From: Dave Jones <davej@redhat.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: serial ports now asserting DTR and RTS during boot; breaks connected hardware
Date: Tue, 3 Jan 2012 11:13:10 -0500 [thread overview]
Message-ID: <20120103161310.GA8727@redhat.com> (raw)
In-Reply-To: <4F03262D.8090506@suse.cz>
On Tue, Jan 03, 2012 at 05:00:45PM +0100, Jiri Slaby wrote:
> On 01/03/2012 04:37 PM, Dave Jones wrote:
> > Jiri,
> > We got this report from a user who notes a change in behaviour for
> > his serial hardware over the last few kernel versions.
>
> Hi!
>
> I'm busy right now, however just after a quick look, it may be related to:
> https://lkml.org/lkml/2011/12/6/573
>
> I'll take a look later.
thanks. I'll dig a little deeper.
> > https://bugzilla.redhat.com/show_bug.cgi?id=771010
> >
> > This sounds like it might be related to your DTR/RTS changes back in March 2011 maybe ?
>
> What changes do you mean? In serial-core.c? Thaat one is not used by USB
> serials. Hence this wouldn't occur with FTDI.
yeah, 303a7a1199c20f7c9452f024a6e17bf348b6b398 and c7d7abff40c27f82fe78b1091ab3fad69b2546f9
jumped out at me, as they were they only things that changed DTR/RTS handling
(at least mentioned in changelog) in recent times.
The user mentions that it also affects 8250, though your point may mean
that this is caused by something further up in the serial/tty code.
Dave
next prev parent reply other threads:[~2012-01-03 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 15:37 serial ports now asserting DTR and RTS during boot; breaks connected hardware Dave Jones
2012-01-03 16:00 ` Jiri Slaby
2012-01-03 16:13 ` Dave Jones [this message]
2012-01-04 18:43 ` Jiri Slaby
2012-01-03 16:06 ` Alan Cox
2012-01-04 20:54 ` Jiri Slaby
2012-01-04 22:37 ` Chris Elmquist
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=20120103161310.GA8727@redhat.com \
--to=davej@redhat.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).