Hi, On Mon, Mar 03, 2008 at 02:00:08AM +0000, oliford wrote: > With some poking of ARM assembly code into the kernel to occasionally > splash rubbish on the video ram I figured out the zImage decompressor isn't > working, so I tried running the straight kernel Image. After getting the > MTYPE right for the kernel it ran... > > I have the penguin! Nice moment.
Congratulations! > I then tried the same with busybox but it crashes, unfortunately I can't > see the beginning of the resulting trace as it goes off the screen and I > have no input method atm. I tried loading the trial init program with > dynamically linked libc, that works ok as well, though not on the busybox > image. I am confused about this and have to check it again. > > I thought might be able to use the 9 buttons via a kernel driver called > gpio_keys, but I can't work out where you define which gpios and what you > want them to end up as (keystroke wise). tbh I don't understand linux input > much. Also there is pxa7xx_keyboard, which a dll of the same name is loaded > in winCE, backwards compatible again I imagine so I compiled it in but it > never outputs anything. Is there an easy way I can find out if it's doing > anything? In order to use the pxa27x keyboard driver, you need to map the keys. You can take a look at what I did in htcapache/htcapache.c. (I'm assuming you are using the kernel from hh.org.) > The PXA2xx serial driver detects the 3 UARTs that the chip apparently has, > though I'm told by the press stuff that the IPAQ214 has no serial port > other than through the USB. I tried hacking the PXA25x USB client driver > into working, but that crashes as well and again I can't see the trace. I > suspect some of the hundreds of addresses in pxa-regs.h for the PXA25x are > wrong for the PXA310. Get to that later. > > The serial driver reports that the three things are an FFUART, an STUART > and BTUART iirc, what do those mean? I cant find out anywhere. They're just the names of three internal serial ports. Intel had the docs online for many years - but I think they took them down when they sold off the stuff to Marvell. You can probably find the docs archived somewhere online. > Reading between the lines of the press stuff, it suggests the bluetooth > chip might be connected to the UARTs. Is this likely? Is that what the > BTUART is? (stab in the dark) The bluetooth stuff is generally hooked up to a uart. On my HTC Apache, it is conneced to BTUART. > The bluetooth stack compiles happily so if I could get that working it'd > provide my debug/input link. Would a separate driver be required for the > bluetooth chip or is there some standard way of driving them through the > UART, the kernel config mentions something about this. Take a look at some of the existing machine definitions. Most have a few lines to activate bluetooth. Good luck, -Kevin _______________________________________________ Haret mailing list [email protected] https://handhelds.org/mailman/listinfo/haret
