From: "Yinghai Lu" <yinghai.lu@amd.com>
To: "Greg KH" <gregkh@suse.de>
Cc: ebiederm@xmission.com, "Peter Stuge" <stuge-linuxbios@cdy.org>,
linux-usb-devel@lists.sourceforge.net,
"Stefan Reinauer" <stepan@coresystems.de>,
linux-kernel@vger.kernel.org, linuxbios@linuxbios.org,
"Andi Kleen" <ak@suse.de>, "David Brownell" <david-b@pacbell.net>
Subject: Re: [LinuxBIOS] [linux-usb-devel] [RFC][PATCH 0/2] x86_64 Early usb debug port support.
Date: Fri, 8 Dec 2006 00:52:26 -0800 [thread overview]
Message-ID: <86802c440612080052x3704d767p8bfeb7fb723c9883@mail.gmail.com> (raw)
In-Reply-To: <20061208071437.GA23173@suse.de>
On 12/7/06, Greg KH <gregkh@suse.de> wrote:
> Ugh, no, never use the usb-serial driver as a console device.
>
> That was a bad hack done as a bet many years ago. For many obvious
> reasons it does not work well.
understood, I found with usb_serial convertor could lose some chatacter.
but the usb-debug cable seem it keep all character.
>
> > host with cat /dev/ttyUSB0
> > But if use minicom in host, it will not show '\r', I guess the usb debug
> > cable eat return char. Greg, Can you add that back in usb_debug by
> > replacing '\n' with '\r', '\n'?
>
> The usb-serial console code should handle this, I thought we fixed it a
> while ago.
Is it in the git tree?
>
> But this kind of interface is not what these devices are good for. They
> are for the debug port information, not as a usb-serial console device.
> Otherwise they are way too expensive of a device...
the problem is some "modern" PC will left out serial port. then the cable
could get cheap.
YH
next prev parent reply other threads:[~2006-12-08 8:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 3:48 Lu, Yinghai
2006-12-08 7:14 ` Greg KH
2006-12-08 8:52 ` Yinghai Lu [this message]
2006-12-08 7:42 ` Eric W. Biederman
2006-12-08 8:53 ` Yinghai Lu
2006-12-08 9:07 ` Eric W. Biederman
2006-12-13 7:00 ` Yinghai Lu
2006-12-13 7:29 ` Eric W. Biederman
2006-12-13 10:09 ` Yinghai Lu
2006-12-13 10:41 ` Yinghai Lu
-- strict thread matches above, loose matches on Subject: below --
2006-12-09 3:16 Lu, Yinghai
2006-12-09 10:54 ` Peter Stuge
2006-12-07 22:06 Lu, Yinghai
2006-12-06 21:08 Lu, Yinghai
2006-12-07 9:51 ` [LinuxBIOS] " Peter Stuge
2006-12-06 0:00 Lu, Yinghai
2006-12-05 23:29 Lu, Yinghai
2006-12-05 23:50 ` Eric W. Biederman
2006-12-06 15:31 ` Segher Boessenkool
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=86802c440612080052x3704d767p8bfeb7fb723c9883@mail.gmail.com \
--to=yinghai.lu@amd.com \
--cc=ak@suse.de \
--cc=david-b@pacbell.net \
--cc=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linuxbios@linuxbios.org \
--cc=stepan@coresystems.de \
--cc=stuge-linuxbios@cdy.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
all inboxes | Powered by JetHome®