Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Hacking OpenAI(hacktron.ai ↗)
    122comments
  2. Jemalloc 5.4.0(github.com/jemalloc ↗)
    18comments
  3. Astra for Law(openai.com ↗)
    488comments
  4. The scourge of x86 emulation(fex-emu.com ↗)
    9comments
  5. Bonsai 2 27B: Near-Lossless Compression in a 9x Smaller Footprint(prismml.com ↗)
    118comments
  6. Bend – A language that blocks AI mistakes via proof, on CPU and GPU(bend-lang.com ↗)
    205comments
  7. Qwen 3.8 Omni Flash(qwen.ai ↗)
    60comments
  8. Pre-Greek: The lost language hidden within Ancient Greek(linguisticdiscovery.com ↗)
    25comments
  9. Hister: A private search engine for the pages you visit and the files you keep(github.com/asciimoo ↗)
    159comments
  10. Wax motor(wikipedia.org ↗)
    63comments
  11. Fujitsu launches made-in-Japan next-generation CPU FUJITSU-MONAKA(global.fujitsu ↗)
    221comments
  12. Shapelearn Qwen 3.8 27B (13.1 GB VRAM)(byteshape.com ↗)
    5comments
  13. When the fractional part of a float fixes your shader(crocidb.com ↗)
    discuss
  14. How to Write with an LLM(sockpuppet.org ↗)
    81comments
  15. Telstra outage: The night a network decided the year was 2006(netnod.se ↗)
    21comments
  16. Flet 1.0 – Build cross-platform apps in Python(flet.dev ↗)
    51comments
  17. Apple detectives solved mystery of ancient tree and rewrote the history of fruit(scientificamerican.com ↗)
    4comments
  18. Ask A Monk – A digital wilderness for thoughts with no immediate answer(askamonk.online ↗)
    20comments
  19. Diplodocus, Long Thought Exclusively American, Turns Up in Spain(sci.news ↗)
    36comments
  20. The most important product decision is what you don't build(liamnugent.me ↗)
    32comments
  21. Fixing an NZXT Signal 4K30 part 2: the green/pink video bug(downtowndougbrown.com ↗)
    8comments
  22. Waymo in Singapore(waymo.com ↗)
    107comments
  23. CrowdSec Source Code Leak(crowdsec.net ↗)
    44comments
  24. How do we prevent mathemathics from devolving into the Medieval Era of secrecy?(mathoverflow.net ↗)
    94comments
  25. Why I didn’t sign the Fields medallists’ letter(gowers.wordpress.com ↗)
    354comments
  26. How Uber Protects Against Retry Storms(uber.com ↗)
    35comments
  27. Show HN: Snapdrop: Instantly share files between devices. No setup, no signup(snapdrop.me ↗)
    34comments
  28. Infinite-Parameter LLMs: Generating and Adapting Weights from Live Data(arxiv.org ↗)
    39comments
  29. Khipu (Quipu) Field Guide(khipufieldguide.com ↗)
    discuss
  30. Code Scans(devin.ai ↗)
    4comments

QEMU 680x0 support [video]

43 pointsby 5y agoyoutube.com
13 comments
5y agoHN ↗

Currently, QEMU fully emulates a Macintosh Quadra 800 and partially a NextCube.

The latest addition to QEMU for M68k presented in this talk - which has not been upstreamed yet - is a new pure virtual machine type based on Google Goldfish, optimized for speed.

The goal of the new virtual machine type is to offer something for developers working on Linux/m68k. It does not run any operating system without the necessary modifications.

So, no, it does not help Amiga emulation directly unless someone adds Amiga hardware emulation support to QEMU based on top of this work.

But it will certainly help the Amiga indirectly by providing a fast development and testing target for the Motorola 68000 CPU.

5y agoHN ↗

So, no, it does not help Amiga emulation directly unless someone adds Amiga hardware emulation support to QEMU based on top of this work.

It may also be possible to add virtualized hardware support to the Amiga OS up to version 3.9 (which runs on 68020 and up), by whoever has legal rights to do so.

It may fail to run games or other software that expects access to the Amiga hardware, but if you want to run well-behaved Amiga programs, it should be possible.

5y agoHN ↗

The QEMU fork that the Android Emulator uses, or at least used.

I had thought Goldfish was no longer used, and something closer to the QEMU repo is used for Android, but I'm not sure about that side of things.

5y agoHN ↗

Generally for systems like that (broadly, "games machines" where a lot of the guest software is bare metal, graphics intensive, likely to make strong assumptions either deliberately or accidentally about exact timings of operations and of interactions between different parts of the system) QEMU is not the place to start. QEMU's core use case is really "run Linux", and more generally running guest code which stays within the documented bounds of system functionality, doesn't require much in the way of device support beyond the CPU itself, and which is happy with "runs as fast as possible" behaviour with no accurate emulation of timing.

For a system like the Amiga you will be much better off looking at one of the specifically-an-Amiga-emulator projects.

5y agoHN ↗

Amiga was the first non-x86 computer that Linux ran on!

5y agoHN ↗

Yes, Linux/m68k mostly lived out-of-tree for a while (with bits and pieces of it landing upstream); from its inception in 1993 until it was (iirc) fully merged in 1996.

Being the first non-x86 port, a lot of things originated there. The virtual console everyone is familiar with originated in Linux/m68k; the i386 Linux used the hardware's built-in text-mode, but the Amiga only had a bitmap display, so in order to get a shell they had to implement a virtual text display that rasterized the text in software.

Maddog had the Alpha sent to Linus in 1994, but Linus didn't begin work until January 1995.

Here's the June 1993 announcement of Linux/m68k 0.05, which I understand to be the first release that was publicly distributed http://www.ibiblio.org/pub/historic-linux/ftp-archives/tsx-1... I haven't actually been able to track down that release tarball, but the 0.05p1 patch release is at http://www.oldlinux.org/Linux.old/ftp-archives/tsx-11.mit.ed... More links at https://www.reddit.com/r/archlinux/comments/ejkp1x/what_is_t...

5y agoHN ↗

Did the Amiga actually have an MMU capable of running Unix? I seem to remember an early version of the m68k port faked fork by copying memory back and forth (so each "forked" process saw the same memory addresses), but I might be confusing Linux with Minix.

5y agoHN ↗

Linux-m68k required a 68020/030+68x51 MMU, or a 68040/060 with built-in MMU.