From: Krzysztof Halasa <khc@pm.waw.pl>
To: Tosoni <jp.tosoni@acksys.fr>
Cc: linux-serial@vger.kernel.org
Subject: Re: should RTS init in serial core be tied to CRTSCTS
Date: Thu, 15 Mar 2007 00:59:45 +0100 [thread overview]
Message-ID: <m3fy87s7f2.fsf@maximus.localdomain> (raw)
In-Reply-To: <002001c7663f$0bc45ee0$2e01a8c0@acksys.local> (Tosoni's message of "Wed, 14 Mar 2007 14:45:35 +0100")
"Tosoni" <jp.tosoni@acksys.fr> writes:
> The reality is: the need exists, it does not break the driver, other OSs
> support it, Linux does not, I personally wrote support for it in the
> existing 8250 driver, other people wrote similar code in similar Linux
> drivers.
>
> But for some reason maintainers did not want to hear about this work. So I
> must reinsert it over and over again with each new version of the kernel.
> </sigh>
Some link to archives maybe? I don't think I've seen your code.
Perhaps you should post the code again? Cc to the maintainer and
lkml wouldn't hurt.
> What I talk about, is a way to toggle RTS
> around transmit data with acceptable delays. This can only reside in the
> serial driver, not in a line discipline.
Of course.
> I do not want to remove the existing behaviour for RTS, I want to add a
> optional "new" one to handle the original standard, and I do believe that I
> am not alone to need this.
That is quite possible, though the normal way of getting things
included into the kernel is posting a patch, getting comments,
perhaps fixing problems, posting again, until it's accepted.
--
Krzysztof Halasa
next prev parent reply other threads:[~2007-03-14 23:59 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 0:03 should RTS init in serial core be tied to CRTSCTS Mike Frysinger
2007-03-04 16:20 ` Robin Getz
2007-03-04 19:46 ` Russell King
2007-03-04 20:42 ` Robin Getz
2007-03-05 8:39 ` Russell King
2007-03-05 17:09 ` Mike Frysinger
2007-03-05 17:39 ` Tosoni
2007-03-05 17:56 ` Russell King
2007-03-05 18:13 ` Mike Frysinger
2007-03-06 20:40 ` Krzysztof Halasa
2007-03-06 23:24 ` Robin Getz
2007-03-07 12:46 ` Krzysztof Halasa
2007-03-07 13:38 ` Oleksiy Kebkal
2007-03-07 15:19 ` Robin Getz
2007-03-07 21:30 ` Oleksiy Kebkal
2007-03-08 13:44 ` Robin Getz
2007-03-08 13:48 ` Russell King
2007-03-08 14:16 ` Carl-Daniel Hailfinger
2007-03-08 14:20 ` Russell King
2007-03-08 16:51 ` Krzysztof Halasa
2007-03-08 18:43 ` Tosoni
2007-03-09 20:39 ` Krzysztof Halasa
2007-03-12 9:22 ` Tosoni
2007-03-12 12:59 ` Krzysztof Halasa
2007-03-14 11:07 ` Tosoni
2007-03-14 12:44 ` Krzysztof Halasa
2007-03-14 13:45 ` Tosoni
2007-03-14 23:59 ` Krzysztof Halasa [this message]
2007-03-08 14:23 ` Oleksiy Kebkal
2007-03-08 14:28 ` Russell King
2007-03-08 14:40 ` Oleksiy Kebkal
2007-03-08 14:25 ` Oleksiy Kebkal
2007-03-08 20:23 ` Robin Getz
2007-03-08 20:40 ` Russell King
2007-03-08 23:32 ` Robin Getz
2007-03-09 8:57 ` Russell King
2007-03-09 14:18 ` Oleksiy Kebkal
2007-03-07 12:54 ` Oleksiy Kebkal
2007-03-07 13:03 ` Krzysztof Halasa
2007-03-07 20:04 ` Mike Frysinger
2007-03-07 5:13 ` Oleksiy Kebkal
2007-03-07 12:48 ` Krzysztof Halasa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3fy87s7f2.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=jp.tosoni@acksys.fr \
--cc=linux-serial@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox