Messages in this thread | | | Date | Sun, 30 May 2004 17:58:21 +0200 | From | Vojtech Pavlik <> | Subject | Re: SERIO_USERDEV patch for 2.6 |
| |
On Sun, May 30, 2004 at 10:09:18AM -0500, Dmitry Torokhov wrote:
> On Sunday 30 May 2004 08:42 am, Vojtech Pavlik wrote: > > > > Anyway, looking at the patch, it's not bad, and it's quite close to what > > I was considering to write. I'd like to keep it separate from the > > serio.c file, although it's obvious it'll require to be linked to it > > statically, because it needs hooks there - it cannot be a regular serio > > driver. > > > > Do we really have to have this stuff directly in serio? How about being able > to mark some serio ports as working in raw mode (i8042.raw=0,1,1,0) and have > separate (serio_raw?) module bind to such ports
We don't have to. But it'd be rather convenient to have it. It would work for all serio ports, not just i8042, etc, etc.
And if kept in a separate file (serio-dev.c), it wouldn't mess up things too much.
-- Vojtech Pavlik SuSE Labs, SuSE CR - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |