All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Daniel Walker <dwalker@fifo99.com>
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
	stern@rowland.harvard.edu, randy.dunlap@oracle.com,
	ebiederm@xmission.com, akpm@linux-foundation.org, gregkh@suse.de,
	tglx@linutronix.de, sarah.a.sharp@intel.com, mingo@elte.hu,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/doc] x86/doc: mini-howto for using earlyprintk=dbgp
Date: Thu, 05 Mar 2009 11:22:58 -0800	[thread overview]
Message-ID: <49B02692.3000500@kernel.org> (raw)
In-Reply-To: <1236267366.5937.56.camel@desktop>

Daniel Walker wrote:
> On Thu, 2009-03-05 at 10:00 +0000, Yinghai Lu wrote:
> 
>> +
>> +Mini-HOWTO for using the earlyprintk=dbgp boot option with a
>> +USB2 Debug port key and a debug cable, on x86 systems.
>> +
>> +You need two computers, the 'USB debug key' special gadget and
>> +and two USB cables, connected like this:
>> +
>> +  [host/target] <-------> [USB debug key] <-------> [client/console]
>> +
>> +1. There are three specific hardware requirements:
>> +
>> + a.) Host/target system needs to have USB debug port capability.
>> +
>> + You can check this capability by looking at a 'Debug port' bit in
>> + the lspci -vvv output:
> 
> ...
> 
>> + c.) Thirdly, you need a second client/console system with a regular USB port.
> 
> You might want to combine a.) and c.) since there is some disconnect
> between the two. c.) doesn't explicitly say a second time that the
> client/console needs the debug port capability ..
> 
> Or say
> 
> a.) You will need two USB ports. One on the client/console system and
> one one the target system.
> 
> b.) The client/console and target USB ports must have the debug port
> capability. You can check for this as follows,
> 
> c.) ...

thanks for checking it.

can you submit patch to Ingo according to tip/master?

YH

  reply	other threads:[~2009-03-05 19:24 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 [this message]
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
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=49B02692.3000500@kernel.org \
    --to=yinghai@kernel.org \
    --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@elte.hu \
    --cc=mingo@redhat.com \
    --cc=randy.dunlap@oracle.com \
    --cc=sarah.a.sharp@intel.com \
    --cc=stern@rowland.harvard.edu \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.