Argh, oki that means that Im still missing something in the s1d13xxxfb driver.

Oki, I will make a custom mp900c kernel with correct framebuffer ram.

Any news?

Not yet, Im stressed for time as always. You could download the v2.6.24-hpc kernel code and adjust it yourself it you want.

Only one problem is I can't find how to setup crosscompiling environment.

And the jlime wiki is dead:

Use the new wiki www.jlime.com. the articles you would need are :
http://jlime.com/mw4/index.php/Kernel_d ... ling_hp700

Its for hp700 but is same as mp900c (just use the mp900c kernel config).

So i successfully compiled non-modified kernel, and found source of problem with non-booting device after softreset - it's booting, but without backlight, I need to wait for WinCE launch, then suspend/resume device, and it's working

Where I need to modify to adjust screen resolution / framebuffer size?

-----

Well, I just adjusted resolution in s1d13mp900fb.c, and:



Hope it's time for some ramfs?

sweet

Ok, so now I need some Your help - if i use make menuconfig, i cant compile kernel - it shows me lot's of warnings, then put in 'normal' console config

The question is - what I need to make some ramfs (with busybox i think), without touching menuconfig?

To change the config you use "make ARCH=arm menuconfig". Since youve already changed your config I suggest you copy the mp900 config to .config again and then do menuconfig.

You can add all the support you want then.

I've added initramfs support, and new kernel is not booting

you are sure thats the only thing you compiled in? Do a test by removing initramfs and see if it boots. Might be that the ramsettings are incorrect so it tries to use more RAM than it actually got.

I've removed initramfs, and kernel boots.

Where I can adjust ram size? (Maui has 128MB)

-----

Maybe it's connected with initrd file directly? Will initrd-enabled kernel boot without such file?

You only see the 64MB ram that mp900c got right? You can change that inside the machine file (arch/arm/mach-pxa/mp900.c bottom).
Also, I still believe the you have set the ramfs/initrd to use too much of your ram and thats why its not booting. You can go through the kernel config to see, should be among the first couple of main options. Its usually set to X number of ramdisks with 16MB each. Take a look and tell me what you see.

Ok, that was my fault. I had compiled Ramdisk support as module. Now, i've compiled it normally, and it boots (tried with initrd from htc wallaby). Better - I've also enabled driver for Intel PXA MMC host, and it see my card here's photo:



Now I'm partitioning my SD card - i'll try to put mp900c userland on it

[edit]

Well, it's booting from SD only one problem - it looks like keyboard is driven differently than in MP900c - it's not working.

Sad thing is that WinCE is damaging ext partition - don't know why it shows it in My Computer, and after that linux kernel doesn't recognize root partition. Only way i currently found is to insert SD card quickly after kernel start booting.

Video: http://www.youtube.com/watch?v=mPgfDcwy8jQ

[edit]
Well, Xorg is working Touchscreen also. Here's vid:
http://www.youtube.com/watch?v=U89x2-7ltDQ

Only issue is still keyboard - noone of hw buttons is working, and when I press any of them ts driver semms to hang.

My config file: LINK
...

Other thing I found - USB slave is controlled by... isp1161a1 (the same as in MP900, but Maui doesn't have USB host (yet? ))

Great progress!

Well, Im somewhat puzzled why touchscreen works but not keyboard. The mp900c driver is using the same gpio for hmm wait.
You dont got a keyboard. maybe its outputting some other commands for the hw buttons. Would be worth to add some printfs to the code and see what kind of data its getting when you press the hw buttons.
Its likely that its still using same gpio for hw buttons and touchscreen since you say that it affects the touchscreen.
Let me make a minimal patch and get back to you.

We should also try and seperate mp900c and bsquare since they are starting to differ more and more. Let me get back to you in a day or so with a patch to test out. Should give some output when you press the buttons and let us know what kind of data its seeing.