JeDi wrote:
>Thanks for the initrd tutorial :-) I'll try it in the morning at work.
>So now I still need the parameters for the vsfb driver, isn't it? Do
>you have them, or do you know how to find out?
>
>
well, the screen resolution of an x50v is 480x640 and the base memory
address is 0x0c00_0000. these are all set correctly in the
kernel26.tar.bz2 file on my site, which is why I sent you that link.
>So I just get your files (with the modified initrd), and Fisherss'
>haret_uart? Or the haret from the downloads section?. Then, when I
>copy the files (haret, kernel, initrd) to the internal storage of the
>pda and run haret, the kernel will boot? Then off course, I'll have to
>create a SD card to store the rootfs on.
>
>
it's easier to put haret, kernel, and initrd on an sd card, and then if
you create a ext2 image called (I think) rootfs in the root of the sd
card you can mount it from there rather than needing a full partition on
the sd card.
>So, with a bit of luck, when I have the framebuffer working, I can
>alter the boot process so usb networking/bluethooth/WiFi works
>automatically, and use the cradle/bluethooth device/Access point to
>login on the device, right?
>It's just that the scheme for the serial cable seems so difficult...
>Or can I just order one somewhere?
>
>
Actually, the framebuffer is the easy part, and that's just because the
2700g controller is already initialized by wince. we're just directly
accessing the video ram for our framebuffer.
It'll take more than a bootprocess modification to get usb networking,
bluetooth, and wifi working, automatically or otherwise.
USB we seem to be missing some GPIOs for, so I suspect it is accessed
through the Toshiba ASIC (which we know nothing about). bluetooth may
be very easy to make work, but I don't know enough about it to try. as
for wifi, we don't even know how it's interfaced. My guess would be
that it's at one of the external memory locations. (see static memory
addresses in cpu docs)
when the framebuffer is working, you still don't yet have the pxa keys
working; this shouldn't be hard to make work, but I haven't tried it yet
so I could be wrong. Also, the touchscreen doesn't work. we know what
chip it is, and how it's interfaced, but for some reason we are unable
to make a driver work for it; someone with more knowledge about
touchscreens might be able to spot an ovious difference, or it may be
something to do with that toshiba asic chip again.
These are our challenges; this is what we need to figure out to make
this usable.
Richard
Received on Tue Sep 06 2005 - 19:47:05 EDT
This archive was generated by hypermail 2.2.0 : Tue Sep 06 2005 - 19:47:12 EDT