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

[Alan Stern]

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@xxxxxxxxxx
> 
> 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

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