Hi Patrick, On Tue, Jan 24, 2012 at 18:35, Patrick Bottelberger <[email protected]> wrote: > Geert Uytterhoeven schrieb: >> What did Amiboot detect without the `-p` option (you may want ti try `-d')? >> Does it assume a 68882 FPU? >> > Without supplying the '-p' parameter amiboot didn't output anything at > all, it just froze the amiga directly after entering the command.
Even with '-d'? >> I'd expected this to be the topology issue, but that change doesn't seem >> to be in 3.1.4. I'll see whether I can reproduce this. I can't reproduce it on ARAnyM with 3.1.4. > Call Trace: [<0000ffff>] mm_release+0xa1/0xa4 > [<002b84fa>] topology_sysfs_init+0x0/0x1e > > Seems to prove that, do you think But this indeed looks like the same problem. Are you using a Debianized 3.1.4 source tree? > http://www.spinics.net/lists/linux-m68k/msg04709.html would solve the issue? Yes, that should fix this problem. >> Do you know what clock chip is used on the A603? I had a quick look on the >> net, but couldn't find it (I did see a picture of an A604 with a partially >> covered chip that said M6242). If you can't find it, I can ask Jens. >> >> Currently, Linux assumes an A2000 clock chip, which is an Oki MSM6242. >> If it's a Ricoh RP5C01, you have to modify arch/m68k/amiga/config.c to >> select an A3000 clock chip on A600. >> > The kernel outputs: "Amiga hardware found: (...) A2000_CLK (...)", can i > rely on that message, or should i get the A603 out of the case and check > the chip to be sure? You cannot rely on that message. It just assumes A2000/A500/A600 etc. have an A2000-style clock chip. But on all but A2000 the RTC is optional. BTW, I also asked Jens Schönfeld. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected] In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
