JeDi wrote:
On 4/28/06, Fisherss <[EMAIL PROTECTED]> wrote:
I dont know if I got it totally and correctly, this happened in the last days:

1. JeDi has got USB network working

Well, it just works in the new kernel, I can't take credit for it :-)
The only "problem" that we have now is that we have to boot with an
usb cable connected, and pull it out and back in to get it to work.
The driver does complain about a wrong setting, and for that udc isn't
working or something. I guess it's a matter of setting the right GPIO
values?


2. the NFS is also working now

Yep, but cause of the little problem with g_ether, we can only do it
through an initrd that we load, and that pauses a while after setting
up g_ether (so you can pull out and in the usb cable), after that it
can mount the rootfs through nfs without problems. The IP-address and
and nfs path is hardcoded in the initrd for now though, if the
problems are solved we can specify that as kernel boot parameter.


3. Sounds like you guys dont know the root password in the familiar
releases  <- it should be:      rootme

I had problems with that, yes. What I did was putting a telnet daeomon
in so I could start a single-user session through that and set the
root password :-) In fact, the rootfs image I put online is the
original latest opie familiar release with the root password changed
to "x50v-linux". Now we know that, we can just use the original
rootfs.


4. there are sitll some problems for the touchscreen driver.

so JeDi, can you tell me what the touchscreen problem exactly is? I
havent tried your releases but I am willing to, and hope that I can do
something for you.

Well, the problem is that I have no experience in writing linux
drivers, and getting to know kernel programming is not a trivial task.
I tried to port your touchscreen driver to the new kernel, but didn't
succeed. The way how touchscreen drivers seems to have changed a lot.
I tried to change the new h4000 ts driver, and that compiled but it
didn't create a new input device when loaded. Probably I missed
something.

But the good news that there is a new SPI framework, for which an
ads7846 and a pxa2xx-spi module exist, which is normally just what we
need. To use those modules, some board-specific structs have to be
registered with the framework in the machine init code. And there the
problems begin :-) I put a framework for the "driver" online, where I
just copied some relevant things from the documentation, but I didn't
get it to work yet. You probably now more about this. Here is the
driver, but I think it has to be compiled in the kernel (in aximx30.c)
in stead of in a module:
http://lumumba.uhasselt.be/~jedi/x50v-linux/aximx30_ts.c

I used your aximx50-gpio.h and the patch for pxa2xx-spi is here (it
isn't incorporated in the kernel tree yet):
http://lumumba.uhasselt.be/~jedi/x50v-linux/pxa2xx-spi.patch

I bundled the other code changes to the kernel in this diff:
http://lumumba.uhasselt.be/~jedi/x50v-linux/diff-source

Actually, all files that I used to build the kernel are here:
http://lumumba.uhasselt.be/~jedi/x50v-linux/
I tried to put an x50 version online too, but couldn't test it. It's
the same, except for the lcd settings:
http://lumumba.uhasselt.be/~jedi/x50-linux/

I have to leave now, but I'll probably be back online in a couple of hours.

Thanks already!

Greetz,
JeDi
Hi,
I've been trying for the last couple of days to get the touchscreen driver to work, but I've had no luck. I incorporated the new spi patch and tried the aximx30_ts.c code above, and still nothing. The problem I get is the following. The corresponding modules are created properly, but when I try to load them I get the error : -1 Unknown symbol in module, more specifically (aximx30_ts: Unknown symbol spi_register_board_info). Meaning that the spi symbols aren't exported. I've tried looking for the symbols in /proc/kallsyms, but all spi symbols don't appear.

I've noticed that when the gpio_keys and evdev modules are loaded a device is created /dev/input/event0. I've tried the tslib tools, but I can't get them to detect any touchscreen inputs.

Anyone know how to get the spi symbols exported properly?


Thanks,

Xm3t3r
--
_______________________________________________
Aximx50-port mailing list
[email protected]
https://www.handhelds.org/mailman/listinfo/aximx50-port

Reply via email to