linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
To: linux-galileo@source.mvista.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: [Linux-galileo] Re: EV-64260-BP & GT64260 bi_recs
Date: Sun, 24 Mar 02 20:31:55 PST	[thread overview]
Message-ID: <0203250431.AA26633@ivan.Harhan.ORG> (raw)


Nye Liu <nyet@zumanetworks.com> wrote:

> _devel does not work on our custom board due
> to ethernet bugs,

Not encountered any so far.

> mpsc problems, and no 750cx support.
                     ^^^^^^^^^^^^^^^^

What are talking about? Adirondack, IBM's reference board for 750CXe built for
them by SBS, has been supported (rock solid) in 2_4_devel since last summer. (I
know firsthand as I wrote all firmware and Linux code for the Adirondack and
significantly participated in the hardware design.) Also the EV-64260A I had at
SBS on which I did my first GT-64260 work had a 750CXe CPU module (SBS was
fully committed to 750CXe or 750FX for all designs by then) and ran fine.

> _devel does also
> not work 100% with ppcboot since it does not support bd_info afaik.

I'm very very glad that 2_4_devel doesn't use the bd_info crap and uses bi_recs
instead. If PPCBoot can't handle that, it's PPCBoot's problem. There is more to
the world than PPCBoot. StarMON rules!

> We do have an Abatron.

Ahh, JTAG Heisenberg debuggers. Another thing I can't stand. Real programmers
don't need no stinking JTAG debuggers. StarMON's debug capabilities are better
than any JTAG debugger and don't have the Heisenberg effects of the latter.

--
Michael Sokolov					786 E MISSION AVE APT F
Programletarian Freedom Fighter			ESCONDIDO CA 92025-2154 USA
International Free Computing Task Force		Phone: +1-760-480-4575
						msokolov@ivan.Harhan.ORG (ARPA)
Let the Source be with you
Programletarians of the world, unite!

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2002-03-25  4:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-25  4:31 Michael Sokolov [this message]
2002-03-25  6:30 ` [Linux-galileo] Re: EV-64260-BP & GT64260 bi_recs Murray Jensen
  -- strict thread matches above, loose matches on Subject: below --
2002-03-25  6:47 Michael Sokolov
2002-03-25  7:44 ` Murray Jensen
2002-03-25  4:19 Michael Sokolov
2002-03-25 11:10 ` Nye Liu
2002-03-20 17:04 Michael Sokolov
2002-03-21 20:36 ` Troy Benjegerdes
2002-03-21 19:17   ` Mark A. Greer
2002-03-21 21:36     ` Jim Potter
2002-03-21 22:15       ` [Linux-galileo] " Nye Liu
2002-03-21 20:19         ` Mark A. Greer
2002-03-20  1:02 Michael Sokolov
2002-03-21 20:15 ` [Linux-galileo] " Troy Benjegerdes
2002-03-21 19:10   ` Mark A. Greer
2002-03-21 22:10     ` Nye Liu

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=0203250431.AA26633@ivan.Harhan.ORG \
    --to=msokolov@ivan.harhan.org \
    --cc=linux-galileo@source.mvista.com \
    --cc=linuxppc-dev@lists.linuxppc.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).