From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: kevin diggs <diggskevin38@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: BootX
Date: Sat, 22 Jan 2011 12:49:55 +1100 [thread overview]
Message-ID: <1295660995.2148.333.camel@pasglop> (raw)
In-Reply-To: <AANLkTi=CVNC-UjdCyByyey_VnPHGtujuH01tquSQyqRm@mail.gmail.com>
On Fri, 2011-01-21 at 19:48 -0600, kevin diggs wrote:
> Hi,
>
> This would require quik, right? I went to penguinppc.org and tried to
> get the latest BootX and quik but the links are dead. Do you know
> where the latest versions are?
That link still works:
> kevin
>
> On Fri, Jan 21, 2011 at 3:21 PM, Benjamin Herrenschmidt
> <benh@kernel.crashing.org> wrote:
> > On Fri, 2011-01-21 at 13:26 -0600, kevin diggs wrote:
> >> Hi,
> >>
> >> Anyone familiar with BootX? Could my problems with the 8600 be related
> >> to some interaction with BootX?
> >
> > It's possible. Have you tried using OF booting instead ? The 8600 should
> > be cable to boot off SCSI or netboot COFF images.
> >
> > Cheers,
> > Ben.
> >
> >
next prev parent reply other threads:[~2011-01-22 1:50 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 ` Benjamin Herrenschmidt [this message]
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=1295660995.2148.333.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=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).