linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: kevin diggs <diggskevin38@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: BootX
Date: Fri, 4 Feb 2011 11:21:37 -0600	[thread overview]
Message-ID: <AANLkTikxL1ZrTmKLvQ--JDZyu=80AM8kUUhi4BGNLz0O@mail.gmail.com> (raw)
In-Reply-To: <1296685762.2349.739.camel@pasglop>

Hi,

FYI:

This driver has some pretty good diagnostics/debug capabilities built
in. Once that is enabled it shows that the inquiry works and the sync
negotiation works. The next command (I think) is test unit ready,
which does not work. It is retried multiple times. The result is 20000
which I think is DID_BUS_BUSY. Probably in mesh_start_cmd(), possibly
something off in the loop at line 462?

kevin

P.S.:  I posted some documentation for dump_stack()/show_stack() but
have not heard anything? Is that not something we are interested in
doing?

  reply	other threads:[~2011-02-04 17:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21 19:26 BootX kevin diggs
2011-01-21 21:21 ` BootX Benjamin Herrenschmidt
2011-01-22  1:48   ` BootX kevin diggs
2011-01-22  1:49     ` BootX Benjamin Herrenschmidt
2011-01-22  1:50     ` BootX Benjamin Herrenschmidt
2011-01-22  2:03       ` BootX kevin diggs
2011-01-22  2:31         ` BootX Benjamin Herrenschmidt
2011-01-22 18:24 ` BootX kevin diggs
2011-01-24 17:51   ` BootX kevin diggs
2011-01-25  4:01   ` BootX kevin diggs
2011-02-02 19:36     ` BootX kevin diggs
2011-02-02 21:40       ` BootX Benjamin Herrenschmidt
2011-02-02 21:55         ` BootX kevin diggs
2011-02-02 22:09           ` BootX kevin diggs
2011-02-02 22:29             ` BootX Benjamin Herrenschmidt
2011-02-04 17:21               ` kevin diggs [this message]
2011-02-04 20:47                 ` BootX Benjamin Herrenschmidt
2011-02-11 19:16             ` BootX kevin diggs

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='AANLkTikxL1ZrTmKLvQ--JDZyu=80AM8kUUhi4BGNLz0O@mail.gmail.com' \
    --to=diggskevin38@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).