* serio chaining in 2.6.x?
@ 2003-11-17 3:06 Zinx Verituse
2003-11-17 7:47 ` Vojtech Pavlik
0 siblings, 1 reply; 4+ messages in thread
From: Zinx Verituse @ 2003-11-17 3:06 UTC (permalink / raw)
To: linux-kernel
I have a device (the device in question is the infamous cuecat) which
connects between the computer and a PS/2 device, and I'm trying to
figure out a good way to chain serio devices, such as:
atkbd <-> cuecat <-> lowlevel driver
The serio driver, however, is very clearly not designed for such
chaining. So, the question is:
What do you folks think the best method for chaining the
serio drivers is?
--
Zinx Verituse
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: serio chaining in 2.6.x?
2003-11-17 3:06 serio chaining in 2.6.x? Zinx Verituse
@ 2003-11-17 7:47 ` Vojtech Pavlik
2003-11-17 16:37 ` Zinx Verituse
0 siblings, 1 reply; 4+ messages in thread
From: Vojtech Pavlik @ 2003-11-17 7:47 UTC (permalink / raw)
To: Zinx Verituse; +Cc: linux-kernel
On Sun, Nov 16, 2003 at 09:06:52PM -0600, Zinx Verituse wrote:
> I have a device (the device in question is the infamous cuecat) which
> connects between the computer and a PS/2 device, and I'm trying to
> figure out a good way to chain serio devices, such as:
> atkbd <-> cuecat <-> lowlevel driver
>
> The serio driver, however, is very clearly not designed for such
> chaining. So, the question is:
>
> What do you folks think the best method for chaining the
> serio drivers is?
You grab the port. Then you create a new one and register it. And you
forward all data that's not destined for you through to the new serio
port.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: serio chaining in 2.6.x?
2003-11-17 7:47 ` Vojtech Pavlik
@ 2003-11-17 16:37 ` Zinx Verituse
2003-11-17 17:50 ` Zinx Verituse
0 siblings, 1 reply; 4+ messages in thread
From: Zinx Verituse @ 2003-11-17 16:37 UTC (permalink / raw)
To: Vojtech Pavlik; +Cc: linux-kernel
On Mon, Nov 17, 2003 at 08:47:48AM +0100, Vojtech Pavlik wrote:
> On Sun, Nov 16, 2003 at 09:06:52PM -0600, Zinx Verituse wrote:
> >
[snip]
> > What do you folks think the best method for chaining the
> > serio drivers is?
>
> You grab the port. Then you create a new one and register it. And you
> forward all data that's not destined for you through to the new serio
> port.
>
> --
> Vojtech Pavlik
Many thanks -- I hadn't considered creating a new port, and I'm sure this
solution will work perfectly :)
--
Zinx Verituse
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: serio chaining in 2.6.x?
2003-11-17 16:37 ` Zinx Verituse
@ 2003-11-17 17:50 ` Zinx Verituse
0 siblings, 0 replies; 4+ messages in thread
From: Zinx Verituse @ 2003-11-17 17:50 UTC (permalink / raw)
To: Vojtech Pavlik; +Cc: linux-kernel
On Mon, Nov 17, 2003 at 10:37:29AM -0600, Zinx Verituse wrote:
> On Mon, Nov 17, 2003 at 08:47:48AM +0100, Vojtech Pavlik wrote:
> > On Sun, Nov 16, 2003 at 09:06:52PM -0600, Zinx Verituse wrote:
> > >
> [snip]
> > > What do you folks think the best method for chaining the
> > > serio drivers is?
> >
> > You grab the port. Then you create a new one and register it. And you
> > forward all data that's not destined for you through to the new serio
> > port.
> >
> > --
> > Vojtech Pavlik
>
> Many thanks -- I hadn't considered creating a new port, and I'm sure this
> solution will work perfectly :)
>
Unfortunately, I hit a snag... I can't see a way to rescan or
disconnect all the ports that need intercepted (or, indeed, any of
them that are already connected)
Suggestions welcome :)
--
Zinx Verituse
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2003-11-17 17:50 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-11-17 3:06 serio chaining in 2.6.x? Zinx Verituse
2003-11-17 7:47 ` Vojtech Pavlik
2003-11-17 16:37 ` Zinx Verituse
2003-11-17 17:50 ` Zinx Verituse
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox