Hi Hartley, On Tue, 9 Feb 2010 11:38:37 -0500, H Hartley Sweeten wrote: > On Tuesday, February 09, 2010 1:17 AM, Jean Delvare wrote: > > No, it works reasonably fine. I was using it myself no later than one > > month ago. Out of curiosity, with which exact evaluation module do you > > plan to use it? > > I'm not actually... > > I am trying to figure out how a serio driver actually gets "hooked" to a > serial port. The i2c-taos-evm driver looked simple enough to play with > in order to figure it out. I was trying to follow the Documentation in > order to use it and ran into the issue below. OK... but please keep in mind that you won't be able to use this driver without supported hardware. The driver will not bind to the serial port if it doesn't detect a supported device. > (...) > Do you know if there is a way to make the connection in kernel? I suppose this is possible from a pure code perspective, but I can't see why one would want to do that. The kernel has no idea what is connected to the serial ports: devices on the serial port can't be reliably nor safely probed. This is why we rely on user-space to declare which device is connected to which port, based on the assumption that the user knows what he or she is doing. > Also, do you know if there is any information on the serio stuff > available anywhere? Other than just reading the kernel source I > have not been able to locate anything. I seem to remember I hit the exact same problem back when I wrote the i2c-taos-evm driver. I ended up reading the source code of other serial device drivers and used them as an example. It was enough to get things to work, but I won't claim I understood all of serio... just enough to do what I needed back then. Maybe Dmitry Torokhov (Cc'd) will be more helpful than me. -- Jean Delvare -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
