Re: xf86-input-tc1kpen v0.0.2 available

Hello aka.bugle,

aka.bugle wrote:
> I've updated my Xorg-server to the masked testing version you are
> running (1.4.0-r2) and all its masked dependencies and recompiled my
> xf86-input-keyboard, 'input-mouse and 'input-tc1kpen. I also installed
> the perl Serial driver.. and your calibration utility now performs
> VERY nicely!!!! thanks! take a look at my xorg.log now and see if
> you like! I do!!!

Good news. If the calib. utility works, the driver should, too;
does it work, then?

Note that you forgot to attach the log...

> Now I'm trying to debug my serial port... take a look at my dmesg
> output to see if there are any weirdnesses that I may have introduced
> to the kernel or whatever...
>
> http://forums.gentoo.org/viewtopic-p-4710296.html#4710296

Your 8250 serial driver message looks just like mine:

Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
pnp: Device 00:06 activated.
00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

although mine comes a bit earlier (I've compiled 8250 into kernel
directly; I suppose you load it as a module). I doubt that would
make any difference, though. It's really strange that udev doesn't
create the device for you; I've grepped ttyS throughout my whole /etc
and didn't find any sign of any special treatment of ttyS0.

> The only way I can get the device (/dev/ttyS0) to show up in /dev is
> to put a custom rule in UDEV rules...
> /etc/udev/rules.d/10-local.rules...
> #No Legacy Serial ports
> ACTION=="add", DEVPATH=="/devices/platform/serial8250/*", OPTIONS="ignore$
> ACTION=="remove", DEVPATH=="/devices/platform/serial8250/*", OPTIONS="ignore$
>
> this gives me a working /dev/ttyS0 node however it wrecks havoc
> with HALD. Without this rule all that UDEV sets up on my machine is
> /dev/ttyS1 /dev/ttyS2 and /dev/ttyS3. And as you know I need ttyS0
> for the pen. Any ideas?

Not really. I can only tell you this:

When I look to my /sys/devices/platform/serial8250/,
I can only see sub-dirs for ttyS1, ttyS2 and ttyS3.

But, the ttyS0 sub-dir can be found in /sys/devices/pnp0/00:06/
(check out your /sys/class/tty/).

Do you have this sysfs entry, too?

In my kernel, I've enabled PNP, PNPACPI and namely SERIAL_8250_PNP.
Maybe that's worth a check.

Try to make a diff of yours and mine kernel config:
http://www.razdva.cz/vencik/TC1000_And_Linux/boot/config-linux-2.6.20-gentoo-r4

I suppose udev should create the device if it has an entry in sysfs.
Have you any /dev/.udev/names/ttyS0 and /dev/.udev/db/*ttyS0 files?
Mine look like this:

ls -la /dev/.udev/names/ttyS0/ /dev/.udev/db/\x2f*ttyS0

lrwxrwxrwx 1 root root 5 Jan 11 09:46
/dev/.udev/db/\x2fdevices\x2fpnp0\x2f00:06\x2fttyS0 -> ttyS0

/dev/.udev/names/ttyS0/:
total 0
drwxr-xr-x 2 root root 60 Jan 11 09:46 ./
drwxr-xr-x 186 root root 3720 Jan 11 12:02 ../
-rw-r--r-- 1 root root 0 Jan 11 09:46
\x2fdevices\x2fpnp0\x2f00:06\x2fttyS0

Regards,

vencik

This e-mail and any attachment is for authorised use by the intended recipient(s) only. This email contains confidential information. It should not be copied, disclosed to, retained or used by, any party other than the intended recipient. Any unauthorised distribution, dissemination or copying of this E-mail or its attachments, and/or any use of any information contained in them, is strictly prohibited and may be illegal. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender directly via email. Any emails that you send to us may be monitored by systems or persons other than the named communicant for the purposes of ascertaining whether the communication complies with the law and company policies.
Received on Fri Jan 11 2008 - 06:16:52 EST