On Sat, Mar 01, 2008 at 09:21:22PM +0000, Oliver Ford wrote: >>> B) Since the kernel apparently has support for the chip, is it fairly >>> likely to 'just work', if I compile with the appropriate config? >>> >> >> No. You need to have kernel code specific to the device (eg, >> IPAQ214). >> >> > I ought to be clear what I mean by 'work'. At the moment all I want to see > how far the kernel will get, I'm not really expecting to be able to use any > of the features/hardware of the device yet, just to know that the compiled > kernel is actually executing on the chip. The best-case at the moment would > be to have a simple program executing under init=blah, post-kernel.
I assume you want the output to go to the framebuffer. You'll need to at least tell the kernel that much. You should be able to clone one of the directories: arch/arm/mach-pxa/<xyz>/ (grab one using a pxafb) and then delete all the stuff you're not interested in. >> The 'pxafb' may work. If your device uses it (instead of, for >> example, an ati chip) and Marvell didn't make any drastic changes then >> it will probably work. Unfortunately, there are no docs, so I don't >> know if Marvell made any changes. >> > Ok, I'd never thought of them using a different chip, I assumed using the > built-in graphics would be usual. > Is there much hope of getting a serial interface working? Does your device have a serial port? If so, I'd definitely try getting that to work. I've also debugged kernels on devices that had a uart hooked up to irda. It's a bit tricky, but can be useful. -Kevin _______________________________________________ Haret mailing list [email protected] https://handhelds.org/mailman/listinfo/haret
