Kai Schroeder wrote:
> Hi,
>
> I had a hardcrash and had lost the files. I have now found them on a
> backup and have uploaded them to rapidshare. Can someone please mirror
> them?
Ok, see http://x50v.imploder.org/
Jelle.
>
> These are the latest images with working touchscreen and battery status
> driver and some buttons working (hopefully, I don't have the time to
> setup a testing environment right now).
> http://rapidshare.de/files/28135641/x50images050506.tar.gz.html
>
>
> And this is the kernel I used to compile the images.
> http://rapidshare.de/files/28134804/linux-2.6.x-hh-aximx50v.tar.bz2.html
>
>
> The relevant source files are in:
>
> linux/arch/arm/mach-pxa/aximx30
> and
> linux/include/asm-arm/arch-pxa
>
> I used the then latest handheldskernel from CVS (in april) applied the
> files from fisherss and richard and made some modifications to aximx30.c
> and created a new touchscreen driver based on the h4000 touchscreen
> driver, because the one from fisherss did not work anymore.
>
> I'm quite busy now and can't really help. If someone ones to start
> developing he should probably start with the latest handheldskernel cvs
> and try to apply the files aximx30.c, axim50_ts.c and aximx50_buttons.c
> (and corresponding makefiles und include files of course). I have
> installed most touchscreen and button test tools to the image - e.g.
> in / there is the program evtest - google for some options.
>
> The most important driver that is still missing is powermanagement (so
> that you can turn the axim off and on). I don't know if powermanagement
> is possible without linux being flashed on the rom, so you have to
> search for possible bootmanagers first. flashing linux on the axim won't
> be possible until we can initialize the display without using winCE for
> that. If you want to create a driver, first have a look at the other
> mach-pxa machines, especially h4000 and a716, you can probably use a lot
> of that code.
>
> My main point of demotivation was that we haven't even identified the
> bluetooth chip and other similar pdas only have commercial (not
> opensource) bluetooth drivers. So, if anyone identifies that chip, that
> would help motivating me as I really need bluetooth ;).
>
> Kai
>
>
>
>
>
Received on Fri Aug 04 2006 - 12:26:11 EDT
This archive was generated by hypermail 2.2.0 : Fri Aug 04 2006 - 12:42:43 EDT