On Tue, 22 Mar 2005 13:01:14 +0300, Andrey Panin <[EMAIL PROTECTED]> wrote:
> On 081, 03 22, 2005 at 02:13:45AM -0500, Dmitry Torokhov wrote:
> > On Monday 21 March 2005 10:31, Kenan Esau wrote:
> > > Am Montag, den 21.03.2005, 09:52 -0500 schrieb Dmitry Torokhov:
> > > >
> > > > There are couple
On 081, 03 22, 2005 at 02:13:45AM -0500, Dmitry Torokhov wrote:
> On Monday 21 March 2005 10:31, Kenan Esau wrote:
> > Am Montag, den 21.03.2005, 09:52 -0500 schrieb Dmitry Torokhov:
> > >
> > > There are couple of things that I an concerned with:
> > >
> > > 1. I don't like that it overrides
On 081, 03 22, 2005 at 02:13:45AM -0500, Dmitry Torokhov wrote:
On Monday 21 March 2005 10:31, Kenan Esau wrote:
Am Montag, den 21.03.2005, 09:52 -0500 schrieb Dmitry Torokhov:
There are couple of things that I an concerned with:
1. I don't like that it overrides meaning of
On Tue, 22 Mar 2005 13:01:14 +0300, Andrey Panin [EMAIL PROTECTED] wrote:
On 081, 03 22, 2005 at 02:13:45AM -0500, Dmitry Torokhov wrote:
On Monday 21 March 2005 10:31, Kenan Esau wrote:
Am Montag, den 21.03.2005, 09:52 -0500 schrieb Dmitry Torokhov:
There are couple of things that I
On Monday 21 March 2005 10:31, Kenan Esau wrote:
> Am Montag, den 21.03.2005, 09:52 -0500 schrieb Dmitry Torokhov:
> >
> > There are couple of things that I an concerned with:
> >
> > 1. I don't like that it overrides meaning of max_proto parameter to be
> > exactly the protocol specified.
>
>
On Mon, 21 Mar 2005 16:31:08 +0100, Kenan Esau <[EMAIL PROTECTED]> wrote:
> Am Montag, den 21.03.2005, 09:52 -0500 schrieb Dmitry Torokhov:
> > On Mon, 21 Mar 2005 13:44:07 +0100, Vojtech Pavlik <[EMAIL PROTECTED]>
> > wrote:
> > > On Tue, Mar 15, 2005 at 02:25:42PM +0100, Kenan Esau wrote:
> > >
Am Montag, den 21.03.2005, 09:52 -0500 schrieb Dmitry Torokhov:
> On Mon, 21 Mar 2005 13:44:07 +0100, Vojtech Pavlik <[EMAIL PROTECTED]> wrote:
> > On Tue, Mar 15, 2005 at 02:25:42PM +0100, Kenan Esau wrote:
> > > Here is a new version of the patch:
> > > - minimal changes
> > > -
On Mon, 21 Mar 2005 13:44:07 +0100, Vojtech Pavlik <[EMAIL PROTECTED]> wrote:
> On Tue, Mar 15, 2005 at 02:25:42PM +0100, Kenan Esau wrote:
> > Here is a new version of the patch:
> > - minimal changes
> > - reintroduced DMI-probing
> >
> > I had a look at the synaptic-sources to see
On Tue, Mar 15, 2005 at 02:25:42PM +0100, Kenan Esau wrote:
> Here is a new version of the patch:
> - minimal changes
> - reintroduced DMI-probing
>
> I had a look at the synaptic-sources to see how the pass-through-mode is
> implemented. We'll see if something similar to this also
On Tue, Mar 15, 2005 at 02:25:42PM +0100, Kenan Esau wrote:
Here is a new version of the patch:
- minimal changes
- reintroduced DMI-probing
I had a look at the synaptic-sources to see how the pass-through-mode is
implemented. We'll see if something similar to this also works
On Mon, 21 Mar 2005 13:44:07 +0100, Vojtech Pavlik [EMAIL PROTECTED] wrote:
On Tue, Mar 15, 2005 at 02:25:42PM +0100, Kenan Esau wrote:
Here is a new version of the patch:
- minimal changes
- reintroduced DMI-probing
I had a look at the synaptic-sources to see how the
Am Montag, den 21.03.2005, 09:52 -0500 schrieb Dmitry Torokhov:
On Mon, 21 Mar 2005 13:44:07 +0100, Vojtech Pavlik [EMAIL PROTECTED] wrote:
On Tue, Mar 15, 2005 at 02:25:42PM +0100, Kenan Esau wrote:
Here is a new version of the patch:
- minimal changes
- reintroduced
On Mon, 21 Mar 2005 16:31:08 +0100, Kenan Esau [EMAIL PROTECTED] wrote:
Am Montag, den 21.03.2005, 09:52 -0500 schrieb Dmitry Torokhov:
On Mon, 21 Mar 2005 13:44:07 +0100, Vojtech Pavlik [EMAIL PROTECTED]
wrote:
On Tue, Mar 15, 2005 at 02:25:42PM +0100, Kenan Esau wrote:
Here is a new
On Monday 21 March 2005 10:31, Kenan Esau wrote:
Am Montag, den 21.03.2005, 09:52 -0500 schrieb Dmitry Torokhov:
There are couple of things that I an concerned with:
1. I don't like that it overrides meaning of max_proto parameter to be
exactly the protocol specified.
Yeah -- I
Here is a new version of the patch:
- minimal changes
- reintroduced DMI-probing
I had a look at the synaptic-sources to see how the pass-through-mode is
implemented. We'll see if something similar to this also works with the
lifebook.
I received a request from a user who has a
Here is a new version of the patch:
- minimal changes
- reintroduced DMI-probing
I had a look at the synaptic-sources to see how the pass-through-mode is
implemented. We'll see if something similar to this also works with the
lifebook.
I received a request from a user who has a
On Mon, Mar 07, 2005 at 08:27:16AM +0100, Kenan Esau wrote:
> > > > > At the end of this mail you'll find some traces I did.
> > > > >
> > > > > I also wonder if it is possible at all to probe this device. I think
> > > > > not. IMHO we should go for a module-parameter which enforces the
> > >
Sorry for the late response.
Am Dienstag, den 01.03.2005, 13:08 +0100 schrieb Vojtech Pavlik:
> On Tue, Mar 01, 2005 at 09:11:49AM +0100, Kenan Esau wrote:
>
> > > This looks like it either expects some other data (like a second
> > > parameter to the command?) or just wants the 0x07 again
Sorry for the late response.
Am Dienstag, den 01.03.2005, 13:08 +0100 schrieb Vojtech Pavlik:
On Tue, Mar 01, 2005 at 09:11:49AM +0100, Kenan Esau wrote:
This looks like it either expects some other data (like a second
parameter to the command?) or just wants the 0x07 again (and not
On Mon, Mar 07, 2005 at 08:27:16AM +0100, Kenan Esau wrote:
At the end of this mail you'll find some traces I did.
I also wonder if it is possible at all to probe this device. I think
not. IMHO we should go for a module-parameter which enforces the
lifebook-protokoll.
On Tue, Mar 01, 2005 at 09:11:49AM +0100, Kenan Esau wrote:
> > This looks like it either expects some other data (like a second
> > parameter to the command?) or just wants the 0x07 again (and not the
> > whole command) to make sure you really mean it.
> >
> > Could you try sending 0xe8 0x07
Am Donnerstag, den 24.02.2005, 10:03 +0100 schrieb Vojtech Pavlik:
> On Mon, Feb 21, 2005 at 09:06:55AM +0100, Kenan Esau wrote:
>
> > > > I also checked my original standalone-driver: Because of this behaviour
> > > > I always retried the last command 3 times if the responce from the
> > > >
Am Donnerstag, den 24.02.2005, 10:03 +0100 schrieb Vojtech Pavlik:
On Mon, Feb 21, 2005 at 09:06:55AM +0100, Kenan Esau wrote:
I also checked my original standalone-driver: Because of this behaviour
I always retried the last command 3 times if the responce from the
device was 0xfe
On Tue, Mar 01, 2005 at 09:11:49AM +0100, Kenan Esau wrote:
This looks like it either expects some other data (like a second
parameter to the command?) or just wants the 0x07 again (and not the
whole command) to make sure you really mean it.
Could you try sending 0xe8 0x07 0x07?
On Mon, Feb 21, 2005 at 09:06:55AM +0100, Kenan Esau wrote:
> > > I also checked my original standalone-driver: Because of this behaviour
> > > I always retried the last command 3 times if the responce from the
> > > device was 0xfe or 0xfc.
> >
> > And did it actually help? Did the touchscreen
On Mon, Feb 21, 2005 at 09:06:55AM +0100, Kenan Esau wrote:
I also checked my original standalone-driver: Because of this behaviour
I always retried the last command 3 times if the responce from the
device was 0xfe or 0xfc.
And did it actually help? Did the touchscreen ever respond
Am Samstag, den 19.02.2005, 14:16 +0100 schrieb Vojtech Pavlik:
[...]
>
> > I also checked my original standalone-driver: Because of this behaviour
> > I always retried the last command 3 times if the responce from the
> > device was 0xfe or 0xfc.
>
> And did it actually help? Did the
On Sat, Feb 19, 2005 at 01:54:41PM +0100, Kenan Esau wrote:
> > > But this return code is _very_ unusual. 0xfc means 'basic assurance test
> > > failure' and should be reported only as a response to the 0xff command.
> >
> > Kenan, can you check whether the 0xfc response is there even if you
> >
Am Donnerstag, den 17.02.2005, 20:42 +0100 schrieb Vojtech Pavlik:
> On Thu, Feb 17, 2005 at 04:04:55PM +0100, Vojtech Pavlik wrote:
>
> > > drivers/input/serio/i8042.c: d4 -> i8042 (command) [78489009]
> > > drivers/input/serio/i8042.c: 07 -> i8042 (parameter) [78489009]
> > >
Am Donnerstag, den 17.02.2005, 20:42 +0100 schrieb Vojtech Pavlik:
On Thu, Feb 17, 2005 at 04:04:55PM +0100, Vojtech Pavlik wrote:
drivers/input/serio/i8042.c: d4 - i8042 (command) [78489009]
drivers/input/serio/i8042.c: 07 - i8042 (parameter) [78489009]
drivers/input/serio/i8042.c: fe
On Sat, Feb 19, 2005 at 01:54:41PM +0100, Kenan Esau wrote:
But this return code is _very_ unusual. 0xfc means 'basic assurance test
failure' and should be reported only as a response to the 0xff command.
Kenan, can you check whether the 0xfc response is there even if you
don't do
On Thu, Feb 17, 2005 at 04:04:55PM +0100, Vojtech Pavlik wrote:
> > drivers/input/serio/i8042.c: d4 -> i8042 (command) [78489009]
> > drivers/input/serio/i8042.c: 07 -> i8042 (parameter) [78489009]
> > drivers/input/serio/i8042.c: fe <- i8042 (interrupt, aux, 12) [78489014]
>
> Ok, this is a
On Thu, Feb 17, 2005 at 03:19:53PM +0100, Kenan Esau wrote:
> > Would you be so kind to post the 'dmesg' log?
>
> Shure -- here you are...
>
> ...
> input: LBPS/2 Fujitsu Lifebook TouchScreen on isa0060/serio1
> drivers/input/serio/i8042.c: d4 -> i8042 (command) [78488524]
>
Am Mittwoch, den 16.02.2005, 22:35 +0100 schrieb Vojtech Pavlik:
> On Wed, Feb 16, 2005 at 07:34:52PM +0100, Kenan Esau wrote:
>
> > > > +
> > > > +/*
> > > > + Enable absolute output -- ps2_command fails always but if
> > > > + you leave this call out the touchsreen
Am Mittwoch, den 16.02.2005, 22:35 +0100 schrieb Vojtech Pavlik:
On Wed, Feb 16, 2005 at 07:34:52PM +0100, Kenan Esau wrote:
+
+/*
+ Enable absolute output -- ps2_command fails always but if
+ you leave this call out the touchsreen will never send
On Thu, Feb 17, 2005 at 03:19:53PM +0100, Kenan Esau wrote:
Would you be so kind to post the 'dmesg' log?
Shure -- here you are...
...
input: LBPS/2 Fujitsu Lifebook TouchScreen on isa0060/serio1
drivers/input/serio/i8042.c: d4 - i8042 (command) [78488524]
drivers/input/serio/i8042.c:
On Thu, Feb 17, 2005 at 04:04:55PM +0100, Vojtech Pavlik wrote:
drivers/input/serio/i8042.c: d4 - i8042 (command) [78489009]
drivers/input/serio/i8042.c: 07 - i8042 (parameter) [78489009]
drivers/input/serio/i8042.c: fe - i8042 (interrupt, aux, 12) [78489014]
Ok, this is a regular 'I
On Wed, Feb 16, 2005 at 07:34:52PM +0100, Kenan Esau wrote:
> > > +
> > > +/*
> > > + Enable absolute output -- ps2_command fails always but if
> > > + you leave this call out the touchsreen will never send
> > > + absolute coordinates
> > > +*/
> >
Am Dienstag, den 15.02.2005, 14:43 +0100 schrieb Vojtech Pavlik:
> On Tue, Feb 15, 2005 at 09:57:59AM +0100, Kenan Esau wrote:
> > Am Freitag, den 11.02.2005, 21:10 +0100 schrieb Vojtech Pavlik:
[...]
> > +
> > +/*
> > + Enable absolute output -- ps2_command fails always but
Am Dienstag, den 15.02.2005, 14:43 +0100 schrieb Vojtech Pavlik:
On Tue, Feb 15, 2005 at 09:57:59AM +0100, Kenan Esau wrote:
Am Freitag, den 11.02.2005, 21:10 +0100 schrieb Vojtech Pavlik:
[...]
+
+/*
+ Enable absolute output -- ps2_command fails always but if
+
On Wed, Feb 16, 2005 at 07:34:52PM +0100, Kenan Esau wrote:
+
+/*
+ Enable absolute output -- ps2_command fails always but if
+ you leave this call out the touchsreen will never send
+ absolute coordinates
+*/
+param =
On Tue, 15 Feb 2005 18:03:28 +0100, Kenan Esau <[EMAIL PROTECTED]> wrote:
> Am Dienstag, den 15.02.2005, 09:43 -0500 schrieb Dmitry Torokhov:
> > On Tue, 15 Feb 2005 14:43:08 +0100, Vojtech Pavlik <[EMAIL PROTECTED]>
> > wrote:
> > > On Tue, Feb 15, 2005 at 09:57:59AM +0100, Kenan Esau wrote:
> >
Am Dienstag, den 15.02.2005, 14:43 +0100 schrieb Vojtech Pavlik:
> On Tue, Feb 15, 2005 at 09:57:59AM +0100, Kenan Esau wrote:
> > Am Freitag, den 11.02.2005, 21:10 +0100 schrieb Vojtech Pavlik:
>
> > Here are my changes. I have tested everything on my lifebook B2175 and
> > it works fine for me.
On Tue, Feb 15, 2005 at 06:03:28PM +0100, Kenan Esau wrote:
> All B-Series Lifebooks have the same touchscreen-hardware. But Dmitri's
> concern is correct -- at the moment I would enforce the LBTOUCH-protocol
> on external mice...
>
> I have to fix this. I will additionally to the DMI stuff use
Am Dienstag, den 15.02.2005, 09:43 -0500 schrieb Dmitry Torokhov:
> On Tue, 15 Feb 2005 14:43:08 +0100, Vojtech Pavlik <[EMAIL PROTECTED]> wrote:
> > On Tue, Feb 15, 2005 at 09:57:59AM +0100, Kenan Esau wrote:
> > > +static struct dmi_system_id lifebook_dmi_table[] = {
> > > + {
> > > +
On Tue, 15 Feb 2005 14:43:08 +0100, Vojtech Pavlik <[EMAIL PROTECTED]> wrote:
> On Tue, Feb 15, 2005 at 09:57:59AM +0100, Kenan Esau wrote:
> > +static struct dmi_system_id lifebook_dmi_table[] = {
> > + {
> > + .ident = "Fujitsu Siemens Lifebook B-Sereis",
> > +
On Tue, Feb 15, 2005 at 09:57:59AM +0100, Kenan Esau wrote:
> Am Freitag, den 11.02.2005, 21:10 +0100 schrieb Vojtech Pavlik:
> Here are my changes. I have tested everything on my lifebook B2175 and
> it works fine for me. I have used DMI for probing. Does anyone have an
> Idea what devices we
Am Freitag, den 11.02.2005, 21:10 +0100 schrieb Vojtech Pavlik:
> Hi!
>
> I've reimplemented the Lifebook touchscreen driver using libps2 and
> input, to make it short and fitting into the kernel drivers.
>
> Please comment on code and test for functionality!
>
> PS.: The driver should register
Am Freitag, den 11.02.2005, 21:10 +0100 schrieb Vojtech Pavlik:
Hi!
I've reimplemented the Lifebook touchscreen driver using libps2 and
input, to make it short and fitting into the kernel drivers.
Please comment on code and test for functionality!
PS.: The driver should register two
On Tue, Feb 15, 2005 at 09:57:59AM +0100, Kenan Esau wrote:
Am Freitag, den 11.02.2005, 21:10 +0100 schrieb Vojtech Pavlik:
Here are my changes. I have tested everything on my lifebook B2175 and
it works fine for me. I have used DMI for probing. Does anyone have an
Idea what devices we have
On Tue, 15 Feb 2005 14:43:08 +0100, Vojtech Pavlik [EMAIL PROTECTED] wrote:
On Tue, Feb 15, 2005 at 09:57:59AM +0100, Kenan Esau wrote:
+static struct dmi_system_id lifebook_dmi_table[] = {
+ {
+ .ident = Fujitsu Siemens Lifebook B-Sereis,
+ .matches = {
+
Am Dienstag, den 15.02.2005, 09:43 -0500 schrieb Dmitry Torokhov:
On Tue, 15 Feb 2005 14:43:08 +0100, Vojtech Pavlik [EMAIL PROTECTED] wrote:
On Tue, Feb 15, 2005 at 09:57:59AM +0100, Kenan Esau wrote:
+static struct dmi_system_id lifebook_dmi_table[] = {
+ {
+ .ident =
On Tue, Feb 15, 2005 at 06:03:28PM +0100, Kenan Esau wrote:
All B-Series Lifebooks have the same touchscreen-hardware. But Dmitri's
concern is correct -- at the moment I would enforce the LBTOUCH-protocol
on external mice...
I have to fix this. I will additionally to the DMI stuff use
Am Dienstag, den 15.02.2005, 14:43 +0100 schrieb Vojtech Pavlik:
On Tue, Feb 15, 2005 at 09:57:59AM +0100, Kenan Esau wrote:
Am Freitag, den 11.02.2005, 21:10 +0100 schrieb Vojtech Pavlik:
Here are my changes. I have tested everything on my lifebook B2175 and
it works fine for me. I have
On Tue, 15 Feb 2005 18:03:28 +0100, Kenan Esau [EMAIL PROTECTED] wrote:
Am Dienstag, den 15.02.2005, 09:43 -0500 schrieb Dmitry Torokhov:
On Tue, 15 Feb 2005 14:43:08 +0100, Vojtech Pavlik [EMAIL PROTECTED]
wrote:
On Tue, Feb 15, 2005 at 09:57:59AM +0100, Kenan Esau wrote:
+static
Vojtech Pavlik wrote:
Hi!
I've reimplemented the Lifebook touchscreen driver using libps2 and
input, to make it short and fitting into the kernel drivers.
Please comment on code and test for functionality!
PS.: The driver should register two input devices. It doesn't yet,
since that isn't very
Vojtech Pavlik wrote:
Hi!
I've reimplemented the Lifebook touchscreen driver using libps2 and
input, to make it short and fitting into the kernel drivers.
Please comment on code and test for functionality!
PS.: The driver should register two input devices. It doesn't yet,
since that isn't very
On Sun, Feb 13, 2005 at 07:14:44PM +0100, Kenan Esau wrote:
> Am Sonntag, den 13.02.2005, 13:01 +0100 schrieb Vojtech Pavlik:
> > On Sun, Feb 13, 2005 at 11:05:00AM +0100, Kenan Esau wrote:
> >
> > > > > This
> > > > > sequence does not always work and there is not something like a "magic
> > >
Am Sonntag, den 13.02.2005, 13:01 +0100 schrieb Vojtech Pavlik:
> On Sun, Feb 13, 2005 at 11:05:00AM +0100, Kenan Esau wrote:
>
> > > > This
> > > > sequence does not always work and there is not something like a "magic
> > > > knock sequence".
> > >
> > > You mean that the only needed bit is
On Sun, Feb 13, 2005 at 11:05:00AM +0100, Kenan Esau wrote:
> > > This
> > > sequence does not always work and there is not something like a "magic
> > > knock sequence".
> >
> > You mean that the only needed bit is setting the resolution to '7'?
>
> The lifebook touchscreen has some
On Sun, Feb 13, 2005 at 10:39:46AM +0100, Kenan Esau wrote:
> Am Samstag, den 12.02.2005, 12:46 -0500 schrieb Arjan van de Ven:
> > On Sat, 2005-02-12 at 18:01 +0100, Kenan Esau wrote:
> >
> > > Second thing is that I am not shure that it is a good idea to integrate
> > > the lbtouch-support into
Am Samstag, den 12.02.2005, 12:46 -0500 schrieb Arjan van de Ven:
> On Sat, 2005-02-12 at 18:01 +0100, Kenan Esau wrote:
>
> > Second thing is that I am not shure that it is a good idea to integrate
> > the lbtouch-support into the psmouse-driver since there is no real way
> > of deciding if the
Am Samstag, den 12.02.2005, 19:34 +0100 schrieb Vojtech Pavlik:
> On Sat, Feb 12, 2005 at 06:01:19PM +0100, Kenan Esau wrote:
> > Am Freitag, den 11.02.2005, 21:10 +0100 schrieb Vojtech Pavlik:
> > > Hi!
[...]
> > As far as I can see the
> > init-sequence is the one from Haralds xfree
On Sun, Feb 13, 2005 at 01:49:10AM -0500, Dmitry Torokhov wrote:
> On Friday 11 February 2005 15:10, Vojtech Pavlik wrote:
> > + if (set_properties) {
> > + psmouse->vendor = "Fujitsu Lifebook";
> > + psmouse->name = "TouchScreen";
> > + }
> > +
> > +
On Sun, Feb 13, 2005 at 01:49:10AM -0500, Dmitry Torokhov wrote:
On Friday 11 February 2005 15:10, Vojtech Pavlik wrote:
+ if (set_properties) {
+ psmouse-vendor = Fujitsu Lifebook;
+ psmouse-name = TouchScreen;
+ }
+
+
Am Samstag, den 12.02.2005, 19:34 +0100 schrieb Vojtech Pavlik:
On Sat, Feb 12, 2005 at 06:01:19PM +0100, Kenan Esau wrote:
Am Freitag, den 11.02.2005, 21:10 +0100 schrieb Vojtech Pavlik:
Hi!
[...]
As far as I can see the
init-sequence is the one from Haralds xfree 3.3.6-driver. There
Am Samstag, den 12.02.2005, 12:46 -0500 schrieb Arjan van de Ven:
On Sat, 2005-02-12 at 18:01 +0100, Kenan Esau wrote:
Second thing is that I am not shure that it is a good idea to integrate
the lbtouch-support into the psmouse-driver since there is no real way
of deciding if the device
On Sun, Feb 13, 2005 at 10:39:46AM +0100, Kenan Esau wrote:
Am Samstag, den 12.02.2005, 12:46 -0500 schrieb Arjan van de Ven:
On Sat, 2005-02-12 at 18:01 +0100, Kenan Esau wrote:
Second thing is that I am not shure that it is a good idea to integrate
the lbtouch-support into the
On Sun, Feb 13, 2005 at 11:05:00AM +0100, Kenan Esau wrote:
This
sequence does not always work and there is not something like a magic
knock sequence.
You mean that the only needed bit is setting the resolution to '7'?
The lifebook touchscreen has some extensions to the standard
Am Sonntag, den 13.02.2005, 13:01 +0100 schrieb Vojtech Pavlik:
On Sun, Feb 13, 2005 at 11:05:00AM +0100, Kenan Esau wrote:
This
sequence does not always work and there is not something like a magic
knock sequence.
You mean that the only needed bit is setting the resolution
On Sun, Feb 13, 2005 at 07:14:44PM +0100, Kenan Esau wrote:
Am Sonntag, den 13.02.2005, 13:01 +0100 schrieb Vojtech Pavlik:
On Sun, Feb 13, 2005 at 11:05:00AM +0100, Kenan Esau wrote:
This
sequence does not always work and there is not something like a magic
knock sequence.
On Sat, Feb 12, 2005 at 06:01:19PM +0100, Kenan Esau wrote:
> Am Freitag, den 11.02.2005, 21:10 +0100 schrieb Vojtech Pavlik:
> > Hi!
> >
> > I've reimplemented the Lifebook touchscreen driver using libps2 and
> > input, to make it short and fitting into the kernel drivers.
> >
> > Please
On Saturday 12 February 2005 12:01, Kenan Esau wrote:
> Second thing is that I am not shure that it is a good idea to integrate
> the lbtouch-support into the psmouse-driver since there is no real way
> of deciding if the device you are talking to is REALLY a
> lifebook-touchsreen or not.
>
I
On Sat, 2005-02-12 at 18:01 +0100, Kenan Esau wrote:
> Second thing is that I am not shure that it is a good idea to integrate
> the lbtouch-support into the psmouse-driver since there is no real way
> of deciding if the device you are talking to is REALLY a
> lifebook-touchsreen or not.
...
>
Am Freitag, den 11.02.2005, 21:10 +0100 schrieb Vojtech Pavlik:
> Hi!
>
> I've reimplemented the Lifebook touchscreen driver using libps2 and
> input, to make it short and fitting into the kernel drivers.
>
> Please comment on code and test for functionality!
>
> PS.: The driver should
Am Freitag, den 11.02.2005, 21:10 +0100 schrieb Vojtech Pavlik:
Hi!
I've reimplemented the Lifebook touchscreen driver using libps2 and
input, to make it short and fitting into the kernel drivers.
Please comment on code and test for functionality!
PS.: The driver should register two
On Sat, 2005-02-12 at 18:01 +0100, Kenan Esau wrote:
Second thing is that I am not shure that it is a good idea to integrate
the lbtouch-support into the psmouse-driver since there is no real way
of deciding if the device you are talking to is REALLY a
lifebook-touchsreen or not.
...
IMHO
On Saturday 12 February 2005 12:01, Kenan Esau wrote:
Second thing is that I am not shure that it is a good idea to integrate
the lbtouch-support into the psmouse-driver since there is no real way
of deciding if the device you are talking to is REALLY a
lifebook-touchsreen or not.
I think
On Sat, Feb 12, 2005 at 06:01:19PM +0100, Kenan Esau wrote:
Am Freitag, den 11.02.2005, 21:10 +0100 schrieb Vojtech Pavlik:
Hi!
I've reimplemented the Lifebook touchscreen driver using libps2 and
input, to make it short and fitting into the kernel drivers.
Please comment on code
Hi!
I've reimplemented the Lifebook touchscreen driver using libps2 and
input, to make it short and fitting into the kernel drivers.
Please comment on code and test for functionality!
PS.: The driver should register two input devices. It doesn't yet,
since that isn't very straightforward in the
Hi!
I've reimplemented the Lifebook touchscreen driver using libps2 and
input, to make it short and fitting into the kernel drivers.
Please comment on code and test for functionality!
PS.: The driver should register two input devices. It doesn't yet,
since that isn't very straightforward in the
81 matches
Mail list logo
