linux-kernel - Re: [tip:x86/doc] x86/doc: mini-howto for using earlyprintk=dbgp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <49B0674B.2000604@oracle.com>
Date:	Thu, 05 Mar 2009 15:59:07 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Daniel Walker <dwalker@...o99.com>
CC:	Alan Stern <stern@...land.harvard.edu>,
	Yinghai Lu <yinghai@...nel.org>, mingo@...hat.com,
	hpa@...or.com, linux-kernel@...r.kernel.org, ebiederm@...ssion.com,
	akpm@...ux-foundation.org, gregkh@...e.de, tglx@...utronix.de,
	sarah.a.sharp@...el.com, mingo@...e.hu,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/doc] x86/doc: mini-howto for using earlyprintk=dbgp

Daniel Walker wrote:
> On Thu, 2009-03-05 at 17:54 -0500, Alan Stern wrote:
>> On Thu, 5 Mar 2009, Daniel Walker wrote:
>>
>>> Fix up some typos, and make the requirements section slightly cleaner.
>>>
>>> Signed-Off-By: Daniel Walker dwalker@...o99.com
>>>
>>> diff --git a/Documentation/x86/earlyprintk.txt b/Documentation/x86/earlyprintk.txt
>>> index 607b1a0..5b51aef 100644
>>> --- a/Documentation/x86/earlyprintk.txt
>>> +++ b/Documentation/x86/earlyprintk.txt
>>> @@ -9,7 +9,9 @@ and two USB cables, connected like this:
>>>  
>>>  1. There are three specific hardware requirements:
>>>  
>>> - 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 one the target system.
>> s/one one/one on/
>>
>> You might also try harder to observe the 80-column rule.
>>
>>> + 
>>> + b.) The client/console and target USB ports must have the debug port capability.
>>>  
>>>   You can check this capability by looking at a 'Debug port' bit in
>>>   the lspci -vvv output:
>>> @@ -35,15 +37,13 @@ and two USB cables, connected like this:
>>>  ( If your system does not list a debug port capability then you probably
>>>    wont be able to use the USB debug key. )
>>>  
>>> - b.) You also need a Netchip USB debug cable/key:
>>> + c.) You also need a Netchip USB debug cable/key:
>>>  
>>>          http://www.plxtech.com/products/NET2000/NET20DC/default.asp
>>>  
>>>       This is a small blue plastic connector with two USB connections,
>>>       it draws power from its USB connections.
>> No.  It draws power from one of its USB connections (the one on the 
>> right side when you're looking at the face with the PLX logo).
>>
>> Alan Stern
> 
> --
> 
> Fix up some typos, and make the requirements section slightly cleaner.
> Updated the power draw comment per Alan Stern.
> 
> Signed-Off-By: Daniel Walker <dwalker@...o99.com>
> 
> diff --git a/Documentation/x86/earlyprintk.txt b/Documentation/x86/earlyprintk.txt
> index 607b1a0..ac913a6 100644
> --- a/Documentation/x86/earlyprintk.txt
> +++ b/Documentation/x86/earlyprintk.txt
> @@ -9,7 +9,11 @@ and two USB cables, connected like this:
>  
>  1. There are three specific hardware requirements:
>  
> - 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?


-- 
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/