linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Oleksiy Kebkal" <lesha@evologics.de>
To: Robin Getz <rgetz@blackfin.uclinux.org>,
	Krzysztof Halasa <khc@pm.waw.pl>,
	Mike Frysinger <vapier.adi@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-serial@vger.kernel.org
Subject: Re: should RTS init in serial core be tied to CRTSCTS
Date: Thu, 8 Mar 2007 15:40:15 +0100	[thread overview]
Message-ID: <57354eff0703080640h65ebf6eay69e5eab048812aab@mail.gmail.com> (raw)
In-Reply-To: <20070308142849.GC30023@flint.arm.linux.org.uk>

2007/3/8, Russell King <rmk+lkml@arm.linux.org.uk>:
> On Thu, Mar 08, 2007 at 03:23:49PM +0100, Oleksiy Kebkal wrote:
> > Ok. I understand now one of the sources of misunderstanding. I don't
> > want to mix console and application serial port.
>
> It's not a misunderstanding if you realise that email is threaded and
> you _follow_ the individual threads.  Robin has a similar concern to
> you but _additionally_ wants something that you don't.
>
> So really to remove the "confusion" from this discussion you should
> avoid trying to correct replies to Robin's emails.

On some stages it was very close... Anyway, sorry...

> > The other problem is how to open serial port with correct settings
> > _after_ booting. In this case /proc could be applicable, isn't it?
>
> Doubt it with todays opinions about /proc contents.  Probably more
> appropriate in sysfs, if someone can be bothered to do the work
> required to properly integrate tty and sysfs.
>
> Don't look at me; I'm not doing very much with serial anymore.

I don't. :) Surely I'm not experienced kernel developer, but I would
like to do it. :)
The only purpose of my remarks and questions was to find the best
origin of force
to solve this problem. And all remarks in this thread are very valuable for me.

-Oleksiy

  reply	other threads:[~2007-03-08 14:40 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
2007-03-08 14:23               ` Oleksiy Kebkal
2007-03-08 14:28                 ` Russell King
2007-03-08 14:40                   ` Oleksiy Kebkal [this message]
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=57354eff0703080640h65ebf6eay69e5eab048812aab@mail.gmail.com \
    --to=lesha@evologics.de \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=rgetz@blackfin.uclinux.org \
    --cc=vapier.adi@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).