All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Masters <jonmasters@gmail.com>
To: Matt Porter <mporter@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Piotr Perak <peri@aqua.aspd.pwr.wroc.pl>
Subject: Re: 2.6.x on 405CR
Date: Mon, 27 Sep 2004 15:10:47 +0100	[thread overview]
Message-ID: <35fb2e5904092707106d056d46@mail.gmail.com> (raw)
In-Reply-To: <20040927065758.B25288@home.com>

On Mon, 27 Sep 2004 06:57:58 -0700, Matt Porter
<mporter@kernel.crashing.org> wrote:
> On Mon, Sep 27, 2004 at 12:46:07PM +0200, Piotr Perak wrote:
> > Hi.
> >
> > Anyone seen 2.6.x kernel working on 405CR?
> > I can't make it boot.

> I can't recall anybody around here having a 405CR.  That's probably
> why you didn't get a reponse the first time you posted this.

I might get access to one at some point - I'll be getting my Virtex II
tree up and running on 2.6 (PowerPC 405D) sometime soon hopefully too.

> I wish I could rent you my BDI2000 to speed up your debugging,
> but we're too far away from each other. :)

I hate you guys. I'm using insight on an XP box with that horrid
Xilinx xygwin - it's not aware of any virtual memory and I have no
symbols nicely available so it's all done by hand.

Jon.

  reply	other threads:[~2004-09-27 14:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-27 10:46 2.6.x on 405CR Piotr Perak
2004-09-27 13:57 ` Matt Porter
2004-09-27 14:10   ` Jon Masters [this message]
2004-09-27 15:16     ` Matt Porter
2004-09-27 16:24   ` Piotr Perak
2004-09-28  9:57   ` Piotr Perak
2004-09-28 13:44     ` Matt Porter
2004-09-28 15:47       ` Piotr Perak
2004-09-28 16:43         ` Matt Porter
2004-09-28 17:00           ` Mark Chambers
2004-09-29 11:20           ` Piotr Perak
2004-09-29 11:58             ` Jon Masters
2004-09-29 13:22               ` Mark Chambers
2004-09-29 14:22                 ` Jon Masters
2004-09-27 15:19 ` Matt Porter

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=35fb2e5904092707106d056d46@mail.gmail.com \
    --to=jonmasters@gmail.com \
    --cc=jonathan@jonmasters.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mporter@kernel.crashing.org \
    --cc=peri@aqua.aspd.pwr.wroc.pl \
    /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.