From: David Brownell <david-b@pacbell.net>
To: Andi Kleen <ak@suse.de>
Cc: yinghai.lu@amd.com, stuge-linuxbios@cdy.org,
stepan@coresystems.de, linuxbios@linuxbios.org,
linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, gregkh@suse.de,
ebiederm@xmission.com
Subject: Re: [linux-usb-devel] [RFC][PATCH 0/2] x86_64 Early usb debug port support.
Date: Wed, 6 Dec 2006 15:47:49 -0800 [thread overview]
Message-ID: <200612061547.51524.david-b@pacbell.net> (raw)
In-Reply-To: <200612062224.33482.ak@suse.de>
On Wednesday 06 December 2006 1:24 pm, Andi Kleen wrote:
> > - Host, to which that console connects (through the debug device);
> > runs usb_debug, much like any other usb-serial device
>
> My understanding was that the client could run in user
> space only on top of libusb.
I suppose it could, if you didn't want to use it like a normal
serial consoe.
> > It's analagous to debugging an embedded box using a serial console
> > with a Linux host ... except the target here is a PC, not an ARM
> > (or PPC, MIPS, etc) custom board.
> >
> >
> > Once the coexistence issues between the debug port and normal EHCI
> > driver get worked, there's no reason not to keep using that debug
> > port as a system console.
>
> One reason is the one I covered in my last mail -- locking of the PCI
> type 1 ports.
That'd be part of coexistence. The debug port is _designed_ to share
two different drivers like that ... EHCI can see, as it comes up,
whether the debug port is in use, and could then ignore it. (At least,
unless/until the debug device gets removed.)
- Dave
next prev parent reply other threads:[~2006-12-07 1:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 20:43 Lu, Yinghai
2006-12-06 20:58 ` Andi Kleen
2006-12-06 21:12 ` Eric W. Biederman
2006-12-06 21:17 ` David Brownell
2006-12-06 21:24 ` Andi Kleen
2006-12-06 21:37 ` Eric W. Biederman
2006-12-06 21:59 ` Andi Kleen
2006-12-06 23:47 ` David Brownell [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-06 21:08 Lu, Yinghai
2006-12-01 18:55 [LinuxBIOS] #57: libusb host program for PLX NET20DC debug device Lu, Yinghai
2006-12-03 15:49 ` Eric W. Biederman
2006-12-04 5:09 ` [RFC][PATCH 0/2] x86_64 Early usb debug port support Eric W. Biederman
[not found] ` <200612042001.09808.david-b@pacbell.net>
2006-12-05 11:01 ` [linux-usb-devel] " Eric W. Biederman
2006-12-06 17:31 ` Andi Kleen
2006-12-05 11:18 ` Eric W. Biederman
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=200612061547.51524.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=ak@suse.de \
--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 \
--cc=yinghai.lu@amd.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
Powered by JetHome