Re: New x50v release including modifed kernel source tree, build script and binaries...

Thanks for the pointers, I hadn't planned on publicising such a
primative build script until I got it working so quickly that decided
just to release it all as is and share it. ;)

I too think it can't be that difficult to fix it, I just literally had
about 2 hours of free time this week so I didn't get far.

I hope to spend more time on it next week and have already started to
progress work with usb networking & wifi (got it all built into the
kernel, but testing it out on the handheld is a long process - i dont
have a serial cable - i have to write scripts into the fs images, copy
it over and reboot it)

Cheers!

-- 
Michael Cutler              . o O ( http://blog.lobstertechnology.com/ )
                                                          PGP: 0xC3ABA735
JeDi wrote:
> Thanks! I'll have a look at it as soon as possible. Good idea to
> create a build script, I was too lazy to do that...
> 
> By looking at your build script, I see that you still use the
> "ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-" environment variables
> when you build the kernel. That isn't necesarry anymore (for a long
> time), you just have to make sure your toolchain is in the path,
> arm-linux- is put in front automatically. In that way people don't
> have to install the toolchain in /usr/bin. But adjusting the script is
> not that hard off course :-)
> 
> I also would put the kernel version (2.6.12-hh2) in a variable, so the
> script can very easily be adjusted to a new kernel version.
> 
> Did you adjust the h4000_ts driver to use 640x480 coordinates?
> Actually, we should modify that module so we can specify that as a
> kernel parameter, so we can use the same source for x50 and x50v.
> 
> I was just thinking about the touchscreen last night. It shouldn't be
> that hard to make this work, right? I mean, it is obvious that the
> screen coordinates are just divided by 2. Couldn't we hack the numbers
> in /etc/pointercal file to adjust for that? Probably just multiplying
> them by 2 won't work, but we can try, right?
> 
> Anyway, great work! I hope I have some spare time soon to restart
> experimenting myself.
> 
> Greetz,
> JeDi
>