From: Jean-Daniel P. <jd...@di...> - 2006-01-05 10:09:50
|
by mistake I reversed the order of files in the previous post, here's the correct patch : -------------------------------------------------------------------------= - --- faketty-0.04/faketty.c 2005-10-01 17:14:16.000000000 +0200 +++ faketty-0.04-jd/faketty.c 2006-01-05 10:08:43.000000000 +0100 @@ -807,9 +805,16 @@ static struct input_handle *ftty_connect MKDEV(INPUT_MAJOR, FTTY_MINOR_BASE + mino= r), dev->dev, "ftty%d", minor); #else - class_device_create(input_class, +#if LINUX_VERSION_CODE >=3D KERNEL_VERSION(2,6,15) + class_device_create(&input_class, + NULL, MKDEV(INPUT_MAJOR, FTTY_MINOR_BASE + mino= r), dev->dev, "ftty%d", minor); +#else + class_device_create(input_class, + MKDEV(INPUT_MAJOR, FTTY_MINOR_BASE + mino= r), + dev->dev, "ftty%d", minor); +#endif #endif =20 =20 @@ -823,9 +828,14 @@ static void ftty_disconnect(struct input #if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,13) class_simple_device_remove(MKDEV(INPUT_MAJOR, FTTY_MINOR_BASE + e= vdev->minor)); #else +#if LINUX_VERSION_CODE >=3D KERNEL_VERSION(2,6,15) + class_device_destroy(&input_class, + MKDEV(INPUT_MAJOR, FTTY_MINOR_BASE + evde= v->minor)); +#else class_device_destroy(input_class, MKDEV(INPUT_MAJOR, FTTY_MINOR_BASE + evde= v->minor)); #endif +#endif devfs_remove("input/ftty%d", evdev->minor); evdev->exist =3D 0; -------------------------------------------------------------------------= - --=20 Jean-Daniel Pauget T=E9l: +33 (0) 676 952 746 2, rue Andr=E9 PELCA 50580 Denneville-Plage France |
From: Hugo V. <hvw...@ya...> - 2006-01-05 14:49:16
|
--- Jean-Daniel Pauget <jd...@di...> wrote: > by mistake I reversed the order of files in the > previous post, > here's the correct patch : <snip> Does the trick Jean-Daniel! Thanks! Hugo __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com |
From: <an...@sc...> - 2006-01-09 14:13:55
|
On Thu, Jan 05, 2006 at 06:49:06AM -0800, Hugo Vanwoerkom wrote: > > > --- Jean-Daniel Pauget <jd...@di...> wrote: > > > by mistake I reversed the order of files in the > > previous post, > > here's the correct patch : > > <snip> > > Does the trick Jean-Daniel! Thanks! so do we have a complete working patch for 2.6.15 now somewhere? where? |
From: Jean-Daniel P. <jd...@di...> - 2006-01-09 15:20:24
|
On Mon, Jan 09, 2006 at 03:13:34PM +0100, Andreas Schuldei wrote: > On Thu, Jan 05, 2006 at 06:49:06AM -0800, Hugo Vanwoerkom wrote: > >=20 > >=20 > > --- Jean-Daniel Pauget <jd...@di...> wrote: > >=20 > > > by mistake I reversed the order of files in the > > > previous post, > > > here's the correct patch : > >=20 > > <snip> > >=20 > > Does the trick Jean-Daniel! Thanks! >=20 > so do we have a complete working patch for 2.6.15 now somewhere? > where? yes, I posted it here just a few days ago. you can now have it here : http://disjunkt.com/dualhead/index.html#ftty I'll also try to bring some clear instructions about faketty soon. --=20 Jean-Daniel Pauget T=E9l: +33 (0) 676 952 746 2, rue Andr=E9 PELCA 50580 Denneville-Plage France |
From: Aivils S. <ai...@un...> - 2006-01-11 08:39:10
|
On Pirmdiena, 9. Janv=E2ris 2006 16:33, Jean-Daniel Pauget wrote: > > so do we have a complete working patch for 2.6.15 now somewhere? > > where? =2D fix 2.6.15 compile issues =2D module and service have separate install commands http://www.ltn.lv/~aivils/files/faketty-0.05.tar.bz2 Unfortunately LED switch patch does not go into Linus tree because of silly objection. May be X guys will request that feature and then Andrew Morton applay it. If you use evdev of X, then you have same trouble of LEDs. Aivils |
From: Zephaniah E. H. <wa...@ae...> - 2006-01-11 09:23:08
|
On Wed, Jan 11, 2006 at 10:43:03AM +0200, Aivils Stoss wrote: > On Pirmdiena, 9. Janv=C4=81ris 2006 16:33, Jean-Daniel Pauget wrote: > > > so do we have a complete working patch for 2.6.15 now somewhere? > > > where? >=20 > - fix 2.6.15 compile issues > - module and service have separate install commands >=20 > http://www.ltn.lv/~aivils/files/faketty-0.05.tar.bz2 >=20 > Unfortunately LED switch patch does not go into Linus tree > because of silly objection. May be X guys will request that > feature and then Andrew Morton applay it. If you use evdev > of X, then you have same trouble of LEDs. I generally only skim this list, could you please provide more details on the problem, and a link to the patch in question? Thank you. Zephaniah E. Hull. --=20 1024D/E65A7801 Zephaniah E. Hull <wa...@ae...> 92ED 94E4 B1E6 3624 226D 5727 4453 008B E65A 7801 CCs of replies from mailing lists are requested. <knghtbrd> <Mercury> You don't have to be crazy to be a member of the=20 <knghtbrd> project, but you will be.. <=3D:] <knghtbrd> ^^^ was that a ref to debian or qf? I forget. <knghtbrd> =3D> <Mercury> knghtbrd: QF <knghtbrd> you sure? * knghtbrd was thinking maybe it was both <Mercury> It applies to both, but I was talking about QF at the time..=20 <G> <knghtbrd> ahh, okie. |
From: Aivils S. <ai...@un...> - 2006-01-11 10:04:51
|
On Tre=F0diena, 11. Janv=E2ris 2006 11:22, Zephaniah E. Hull wrote: > On Wed, Jan 11, 2006 at 10:43:03AM +0200, Aivils Stoss wrote: > > On Pirmdiena, 9. Janv=E2ris 2006 16:33, Jean-Daniel Pauget wrote: > > > > so do we have a complete working patch for 2.6.15 now somewhere? > > > > where? > > > > - fix 2.6.15 compile issues > > - module and service have separate install commands > > > > http://www.ltn.lv/~aivils/files/faketty-0.05.tar.bz2 > > > > Unfortunately LED switch patch does not go into Linus tree > > because of silly objection. May be X guys will request that > > feature and then Andrew Morton applay it. If you use evdev > > of X, then you have same trouble of LEDs. > > I generally only skim this list, could you please provide more details > on the problem, and a link to the patch in question? Patch fix case , when 1st X uses old tty layer and 2nd (3rd...) X uses evdev driver. Without patch 1st X via tty switch LED's of all connected keyboards. http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15/2.6.15-mm= 2/broken-out/input-keyboard_tasklet-dont-touch-leds-of-already-grabed-devic= e.patch Discusion: > Dmitry Torokhov <dmi...@gm...> wrote: > > > > On 1/6/06, Vojtech Pavlik <vo...@su...> wrote: > > > On Thu, Jan 05, 2006 at 10:36:41PM -0800, ak...@os... wrote: > > > > > > Fine with me. > > > > > > > From: Aivils Stoss <ai...@un...> > > > > > > > > Recent kernels allow exclusive usage of input device when input dev= ice=20 is > > > > grabbed. =A0keyboard_tasklet does not check device state and switch= =20 LED's of > > > > all keyboards. =A0However grabbed device may be use another LED ste= ering > > > > code. > > > > > > > > This patch forbid keyboard_tasklet switch LED's of grabbed devices. > > > > > >=20 > > The same objection as before - LED state is not synched back after > > device is released. We probably need "ungrab" hook somewhere... > >=20 >=20 > Ho hum. =A0I'll keep the patch queued and will doubtless resend it in a f= ew > weeks time. =A0One day someone will get sick of this and will fix it for= =20 real ;) We cannot sync back keyboard mapping, rate, LED state after "ungrab". I cannot understand view point of Dmitry Torokhov. Someone realy get sick if ungrabing became "hooked". Aivils |