Messages in this thread | | | Date | Mon, 5 Mar 2007 09:23:13 +0100 | From | "Oleksiy Kebkal" <> | Subject | Re: should RTS init in serial core be tied to CRTSCTS |
| |
On 4 Mar, 21:50, Robin Getz <r...@blackfin.uclinux.org> wrote: > On Sun 4 Mar 2007 14:46, Russell King pondered: > > The console command *only* sets the state for the kernel's use of one > > serial port. It does not affect any other serial port, so tying > > random RTS behaviours into that command line option is absolutely > > silly. > The real issue is that there is some legacy equipment, which gets confused if > it sees glitches on RTS (which happens today, when serial core init asserts > RTS, and then the the main application turns it off)... > > How do I set the set up the UART, so RTS is avaliable, but not enabled?
Yes, it is key issue. I think it is not silly to want to set up the UART before RTS is enabled. It is going not about some random RTS behaviour, but about the question how to ask the kernel just don't touch RTS signal. As I understand the current kernel implementation doesn't give a chance to do it.
I wrote about it also several days ago here: http://groups.google.de/group/linux.kernel/browse_thread/thread/82e61dccd11c9e3f/b03971c074609c95?lnk=gst&q=Kebkal&rnum=1&hl=ru#b03971c074609c95 Maybe it would be more relevant to write it in this topic.
Thanks -Oleksiy - 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/
| |