On Wed, Feb 09, 2005 at 09:03:51PM +0100, Jan-Benedict Glaw wrote: > > > It's even worse. Most keyboards don't separate the real keys from > > > magnetic stripe reader events, and just simulate key presses for MSR > > > data. They expect the software to be in a state where it is waiting for > > > that data, and will process it accordingly. > > > > In that case I'm not sure if the kernel should care at all what the data > > is. > > The problematic part is that this needs to be done at a quite low level, > since POS keyboards may send quite a lot more than make/break codes in > "proper" order...
I'll need some specific examples of protocols the keyboard use to judge how to tackle that. > > > What we've done in our application is to use the timings and sequence of > > > key presses to distinguish between normal key presses and MSR data :P > > > > Yes, embedded and single purpose systems are often full of hacks like > > this. > > ...and especially this problem can be better solved by reprogramming the > MCR readers :-) -- Vojtech Pavlik SuSE Labs, SuSE CR - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
