From: Randy Dunlap <randy.dunlap@oracle.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Sarah Sharp <sarah.a.sharp@intel.com>, Greg KH <gregkh@suse.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Ingo Molnar <mingo@elte.hu>,
linux-usb@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: EHCI debug documentation
Date: Tue, 03 Mar 2009 17:36:11 -0800 [thread overview]
Message-ID: <49ADDB0B.1050002@oracle.com> (raw)
In-Reply-To: <86802c440903031731x36c1180dk72a3631bb4397319@mail.gmail.com>
Yinghai Lu wrote:
> On Tue, Mar 3, 2009 at 3:53 PM, Sarah Sharp <sarah.a.sharp@intel.com> wrote:
>> Greetings,
>>
>> You wrote the EHCI debug port patch for early printk back in July 2008
>> (commit 5c05917e7fe313a187ad6ebb94c1c6cf42862a0b). Can you add some
>> documentation to the Documentation directory about how a Linux user
>> would set up a system (cables, files to open to get the printks, etc.)?
>
> please check
>
> ==========================================================================================
> USB Debug port using Howto
>
> 1. HW:
>
> a. target system need to have debug port
>
> 00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2
> EHCI Controller #1 (rev 03) (prog-if 20 [EHCI])
> Subsystem: Lenovo ThinkPad T61
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR+ FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>> TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0
> Interrupt: pin D routed to IRQ 19
> Region 0: Memory at fe227000 (32-bit, non-prefetchable) [size=1K]
> Capabilities: [50] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA
> PME(D0+,D1-,D2-,D3hot+,D3cold+)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME+
> Capabilities: [58] Debug port: BAR=1 offset=00a0
> Kernel driver in use: ehci_hcd
> Kernel modules: ehci-hcd
> 00: 86 80 36 28 06 01 90 02 03 20 03 0c 00 00 00 00
> 10: 00 70 22 fe 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 aa 17 ab 20
> 30: 00 00 00 00 50 00 00 00 00 00 00 00 0b 04 00 00
> 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 50: 01 58 c2 c9 00 80 00 00 0a 00 a0 20 00 00 00 00
> 60: 20 20 9f 01 00 00 00 00 01 00 00 01 00 00 08 80
> 70: c0 00 17 3f 00 00 00 00 00 00 00 00 00 00 00 00
> 80: 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00
> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 00 00 00 00 00 aa ff 00 00 00 00 00 00 00 00 00
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> f0: 00 00 00 00 88 85 40 00 86 0f 05 00 06 17 02 20
>
> b. netchip USB debug cable
http://www.plxtech.com/products/NET2000/NET20DC/default.asp
> c. console system: have USB port
>
> 2. SW setting
> a. console system: need to have kernel config
> CONFIG_USB_SERIAL_DEBUG
> you should get /dev/ttyUSBx
>
> # cat /dev/ttyUSBx could get output
>
> b. target system: need to have kernel config
> CONFIG_EARLY_PRINTK_DBGP
>
> boot command line: earlyprintk=dbgp
>
> c. for Nvidia Southbridge based system: kernel will try to probe and
> find out which port has debug device connected.
--
~Randy
next prev parent reply other threads:[~2009-03-04 1:36 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 [this message]
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
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=49ADDB0B.1050002@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sarah.a.sharp@intel.com \
--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 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.