From: Pavel Machek <pavel@ucw.cz>
To: Oliver Neukum <oliver@neukum.org>
Cc: kernel list <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: ttyACM0: 2.6.30-rc7 dies on device disconnect, strange echo (regressions)
Date: Tue, 2 Jun 2009 11:19:13 +0200 [thread overview]
Message-ID: <20090602091912.GD15756@elf.ucw.cz> (raw)
In-Reply-To: <200906011434.57083.oliver@neukum.org>
On Mon 2009-06-01 14:34:56, Oliver Neukum wrote:
> Am Montag, 1. Juni 2009 13:31:51 schrieb Pavel Machek:
> > Steps to reproduce:
> >
> > minicom /dev/ttyACM0
> >
> > Bug #2: try to interactivelly communicate with the other
> > device. Notice that characters are echoed one character too late. You
> > type "hello", but only "hell" appears. You press "!", "o" appears.
> >
> > Bug #1: while minicom is still connected, pull the USB cable. Machine
> > locks hard.
>
> I can replicate neither bug with 2.6.30-rc7. Can you replicate it with
> anything but openMOKO?
So AT commands echo properly on USB modem or something? Bad :-(.
I'm afraid I do not have another ACM device near me. I guess going
through cdc-acm.c 's history would be relevant?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-06-02 9:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 10:14 ttyACM0: when the device dies, 2.6.30-rc7 dies, too (regression?) Pavel Machek
2009-06-01 10:25 ` ttyACM0: when the device dies, 2.6.30-rc7 dies, too, strange echo (regression) Pavel Machek
2009-06-01 10:42 ` Oliver Neukum
2009-06-01 11:31 ` ttyACM0: 2.6.30-rc7 dies on device disconnect, strange echo (regressions) Pavel Machek
2009-06-01 12:34 ` Oliver Neukum
2009-06-02 9:19 ` Pavel Machek [this message]
2009-06-02 13:20 ` Oliver Neukum
2009-06-02 13:21 ` Oliver Neukum
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=20090602091912.GD15756@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=rjw@sisk.pl \
/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
Powered by JetHome