Hi, thanks for the reply !

On Wednesday 30 May 2007 17:34:37 [EMAIL PROTECTED] wrote:
> To see if tc1000ts is really doing its job, you can change
> id:5:initdefault to id:3:initdefault in your /etc/inittab. This
> enables your system to start without launching X server.
>
> Restart your system, then run tc1000ts and /bin/setserial /dev/ttyS2
> autoconfig from the console.  If setserial returns with valid info,
> start X server by startx.  Otherwise, you may need to add debug
> statement to tc1000ts.c to see what's going on.
>
> Ping

I already tried in runlevel 3 before, exactly the same results as in 5: 
# <login as root straight after booting>
# /bin/setserial /dev/ttyS2
< /dev/ttyS2, UART: unknown, Port 0x03e(, IRQ: 4
# /usr/sbin/tc1000ts
# /bin/setserial /dev/ttyS2
< /dev/ttyS2, UART: unknown, Port 0x03e(, IRQ: 4
# /bin/setserial /dev/ttyS2 autoconfig
< /dev/ttyS2, UART: unknown, Port 0x03e(, IRQ: 4
# /bin/setserial /dev/ttyS2
< /dev/ttyS2, UART: unknown, Port 0x03e(, IRQ: 4
[ . . . ]

I'd love to have a try with the debug output. However since not having a clue 
I don't know what to output how ! Maybe you could give me some help here ?

I'd say this is what I have to re-check: 
1.) are the two addresses declared at the beginning of tc1000ts.c correct for 
a TC1000? How do I tell or check ? 
---
const int cfgindex = 0x4e;
const int cfgdata   = 0x4f;
---
I understand the "wsio" macro defined below and as far as i recall "outb" 
itself is a kernel macro to output a byte to a port, whatever a port means 
here, I'd guess a register address to be written to?

2.) that would mean that the following 9 usages of the "wsio" macro write 
values to the registers, probably to program the underlying i/o chip?
So, how do I tell if these are are right sequences ? Probably hardware 
dependend, so in addition how to I find out the type of hardware ?

Guess I have to wait for a few hints from you...

Thanks, arkascha

>
> On 5/28/07, Christian Reiner <[EMAIL PROTECTED]> wrote:
> > Hi,
> > I spent quite a while trying to find out how to get the tablet stuff
> > working on a Compaq TC1000. Amongst other stuff I came about the
> > linuxwacom site and found the Documentation about Tablet PCs promising.
> >
> > I have the impression that I am stuck at initializing the serial device
> > (connecting the tablet hardware to it). As mentioned in the
> > documentation, chapter 7,  this has to be initialized on some Compaq
> > Tablet PCs. There is a small c application meant to do this, but it is
> > written for a compaq TC1100, a slightly newer model. It is also mentioned
> > that this application has not been tested with the TC1000. I would like
> > to do that, but I have no idea about kernel hacking and hardware stuff.
> > So maybe someone can give me a helping hand?
> >
> > Thanks for any reply, I'll be happy to provide additional info !
> > arkascha
> >
> >
> >
> >
> > This is the setup so far:
> > Distribution: opensuse-10.2
> >
> > I have the tc1000ts.c file compiled with -O2 and call it
> > from /etc/init.d/boot.local:
> >
> > # some comments
> > touch /var/lock/subsys/local
> > /usr/sbin/tc1000ts
> > /bin/setserial /dev/ttyS2 autoconfig
> >
> > boot.local IS processed, I can generate errors or logging from it.
> >
> > Nevertheless a setserial call afterwards still gives:
> > # setserial /dev/ttyS2
> > /dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4
> >
> > Consequently wacdump does not work:
> > # wacdump /dev/ttyS2
> > WacomOpenTablet: Invallid argument
> > I also tried to use setserial by hand (without autofconfig), but could
> > not produce any result.
> >
> > Some lines from my xorg.conf:
> >
> > . . .
> > Section "InputDevice"
> >  Driver       "mouse"
> >  Identifier   "Mouse[1]"
> >  Option       "Buttons" "5"
> >  Option       "Device" "/dev/input/mice"
> >  Option       "Name" "Jing-Mold Enterprise USB K/B+Mouse"
> >  Option       "Protocol" "explorerps/2"
> >  Option       "Vendor" "Sysp"
> >  Option       "ZAxisMapping" "4 5"
> > EndSection
> >
> > Section "InputDevice"
> >  Driver       "wacom"
> >  Identifier   "Mouse[3]"
> >  Option       "Device" "/dev/ttyS2"
> >  Option       "ForceDevice" "ISDV4"
> >  Option       "InputFashion" "Tablet"
> >  Option       "Mode" "Absolute"
> >  Option       "Name" "ISDV4 TABLET PC (SERIAL)"
> >  Option       "SendCoreEvents" "on"
> >  Option       "Type" "stylus"
> >  Option       "Vendor" "WACOM"
> > EndSection
> >
> > Section "InputDevice"
> >  Driver       "wacom"
> >  Identifier   "Mouse[5]"
> >  Option       "Device" "/dev/ttyS2"
> >  Option       "ForceDevice" "ISDV4"
> >  Option       "InputFashion" "Cursor"
> >  Option       "Mode" "Absolute"
> >  Option       "Name" "ISDV4 TABLET PC Stylus (SERIAL)"
> >  Option       "Protocol" "Auto"
> >  Option       "Type" "cursor"
> >  Option       "Vendor" "WACOM"
> > EndSection
> > . . .
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > Linuxwacom-discuss mailing list
> > Linuxwacom-discuss@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Reply via email to