From: Ingo Molnar <mingo@elte.hu>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Daniel Walker <dwalker@fifo99.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
Yinghai Lu <yinghai@kernel.org>,
mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
ebiederm@xmission.com, akpm@linux-foundation.org, gregkh@suse.de,
tglx@linutronix.de, sarah.a.sharp@intel.com,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/doc] x86/doc: mini-howto for using earlyprintk=dbgp
Date: Fri, 6 Mar 2009 16:55:27 +0100 [thread overview]
Message-ID: <20090306155527.GA24448@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0903060958130.3461-100000@iolanthe.rowland.org>
* Alan Stern <stern@rowland.harvard.edu> wrote:
> On Thu, 5 Mar 2009, Daniel Walker wrote:
>
> > On Thu, 2009-03-05 at 15:59 -0800, Randy Dunlap wrote:
> >
> > > > - a.) Host/target system needs to have USB debug port capability.
> > > > + a.) You will need two USB ports. One on the client/console system and one on
> > > > + the target system.
> > > > +
> > > > + b.) The client/console and target USB ports must have the debug port
> > > > + capability.
> > >
> > > Is that correct on the (ugh, I think that the naming/terminology is
> > > still mucked up, but you didn't do that) host/target system?
> > >
> > > On the client/console (which I would call the host and I would call the
> > > "Host/target" here just the Target system), a USB debug port is needed,
> > > but on the Host/target, it should just look like a USB device.
> > > At least that was the intent AFAIK/IIRC. No?
> > >
> >
> > >From the rest of document I assumed Host/target was referring to both
> > sides of the connection. So you would need USB on both sides for this
> > thing to work. I assumed Client/console was just the host. I guess that
> > is all kind of confusing tho ..
>
> The term "Host" is too confusing to be used here; it has too
> many other meanings. "Target" is good.
I used Host/Target for that reason, consistently so. The combo
gives us the best of both worlds.
> "Client" is probably okay too, but I don't like "Console" so
> much because both machines will have a console. "Debugging
> console" is more accurate but also more cumbersome.
I used client/console term for that reason.
> > The document indicates you need this one capability on your
> > USB port in addition to the USB device (check the complete
> > document for how to find the capability). So both host and
> > target need this one capability, and then you also need the
> > USB device for the whole thing to work.
>
> In fact the original document was rather clear about this; it
> says only that the target machine needs the debug capability.
> The client machine uses its normal USB driver and treats the
> debugging cable as a normal USB serial device.
yes.
btw., i think this document is being over-engineered.
Significantly so.
Ingo
next prev parent reply other threads:[~2009-03-06 15:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090303235354.GA7145@gamba.jf.intel.com>
2009-03-04 1:31 ` EHCI debug documentation Yinghai Lu
2009-03-04 1:36 ` Randy Dunlap
2009-03-04 17:57 ` Ingo Molnar
2009-03-04 21:25 ` Greg KH
2009-03-04 21:39 ` Eric W. Biederman
2009-03-04 21:59 ` Alan Stern
2009-03-04 22:55 ` Sarah Sharp
2009-03-05 0:11 ` [PATCH] x86/doc: doc the using earlyprintk=dbgp Yinghai Lu
2009-03-05 10:00 ` [tip:x86/doc] x86/doc: mini-howto for " Yinghai Lu
2009-03-05 15:36 ` Daniel Walker
2009-03-05 19:22 ` Yinghai Lu
2009-03-05 22:40 ` Daniel Walker
2009-03-05 22:54 ` Alan Stern
2009-03-05 23:02 ` Daniel Walker
2009-03-05 23:05 ` Randy Dunlap
2009-03-05 23:12 ` Daniel Walker
2009-03-05 23:19 ` Randy Dunlap
2009-03-05 23:32 ` Daniel Walker
2009-03-05 23:41 ` Randy Dunlap
2009-03-05 23:44 ` Daniel Walker
2009-03-06 14:57 ` Alan Stern
2009-03-06 15:03 ` Daniel Walker
2009-03-06 15:55 ` Alan Stern
2009-03-05 23:48 ` Daniel Walker
2009-03-05 23:59 ` Randy Dunlap
2009-03-06 0:09 ` Daniel Walker
2009-03-06 15:52 ` Alan Stern
2009-03-06 15:55 ` Ingo Molnar [this message]
2009-03-06 16:16 ` Daniel Walker
2009-03-06 2:23 ` Daniel Walker
2009-03-05 2:06 ` EHCI debug documentation Greg KH
2009-03-04 22:50 ` Sarah Sharp
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=20090306155527.GA24448@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=dwalker@fifo99.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=randy.dunlap@oracle.com \
--cc=sarah.a.sharp@intel.com \
--cc=stern@rowland.harvard.edu \
--cc=tglx@linutronix.de \
--cc=yinghai@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