mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Jason Wessel <jason.wessel@windriver.com>,
	Yinghai Lu <yinghai@kernel.org>
Subject: usb debug port documentation
Date: Fri, 14 May 2010 12:31:16 +0200	[thread overview]
Message-ID: <1273833076.4950.4.camel@jlt3.sipsolutions.net> (raw)

Hi,

I've been looking at
http://www.kernel.org/doc/Documentation/x86/earlyprintk.txt and spent a
while finding everything correctly in place. One of the big unknowns is
what way debug ports are enumerated, so if you have a few USB ports you
end up trying a lot. At the same time, I at least wasn't sure I was
doing everything correctly to start with. It does seem, for example,
that I needed the serial driver built in the kernel too?

In any case, to help others I was wondering if we should start a wiki
page somewhere or so that just lists what port on various machines
people have gotten it to work on? I have a Toshiba Satellite U505 and
earlyprintk=dbgp,keep uses the port on the right-hand side of the
machine... That information could possibly help somebody who is setting
it up for the first time, since it reduces the search space? :)

If there's an appropriate wiki, I'd like to be pointed to it so I can
start a page and submit a kernel patch pointing to it. Otherwise I'll
just create it internally since we all typically use just a handful of
machine types, but it seems like public could help more people.

johannes


             reply	other threads:[~2010-05-14 10:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-14 10:31 Johannes Berg [this message]
2010-05-15 11:07 ` matthieu castet

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=1273833076.4950.4.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

Powered by JetHome