From: kevin diggs <diggskevin38@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: BootX
Date: Fri, 21 Jan 2011 13:26:29 -0600 [thread overview]
Message-ID: <AANLkTikAVgH9-UQfrjoAJSemet5p_PxhxCdot8cChQu3@mail.gmail.com> (raw)
Hi,
Anyone familiar with BootX? Could my problems with the 8600 be related
to some interaction with BootX?
kevin
next reply other threads:[~2011-01-21 19:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 19:26 kevin diggs [this message]
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 ` BootX kevin diggs
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=AANLkTikAVgH9-UQfrjoAJSemet5p_PxhxCdot8cChQu3@mail.gmail.com \
--to=diggskevin38@gmail.com \
--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).