Hi Heiko, On Sunday 19 April 2009 03:04:25 Heiko Schocher wrote: > Hello Dmitry, > > Dmitry Torokhov wrote: > > > > You need to create 2 serio ports in your driver and have it send data > > into appropriate port, depending on what device it came from. If you > > take a look at i8042 driver it does exactly that. We have 1 serio port > > for keyboard and eithe 1 or 4 AUX serio ports. In i8042_interrupt we > > check the status bit to figure to which serio port incoming byte should > > be routed and act accordingly. > > Ah, thanks for this hint :-) > > OK, so I have to write a serial driver for the uart on my hardware, > and add this in drivers/serio, right? > > Hmm.. spontaneous I think (maybe it is a bad thought), what do you > think to the following approach: > > I didn;t want to write a new serio driver for my uart (mpc5200 internal > PSC Uart), because there is a working tty driver for this, and the multi- > plexing functionality is just a protocoll ... so I think of using > the drivers/serio/serport.c and add this "multiplexing" functionality > to the serport.c driver ... is this worth about to think? > > this should be a more general approach then writting a special serial > driver for "my" UART ... what do you think? > Yes, this is definitely better solution. I did not realize that there was a working driver for your UART. It would be best if your solution extended (and was compatible with) current N_MOUSE line discipline. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
