From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jeff Mock <jeff@mock.com>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: Re: Ocotea board?
Date: Wed, 24 Oct 2007 06:36:11 +1000 [thread overview]
Message-ID: <1193171771.2085.1.camel@pasglop> (raw)
In-Reply-To: <471E39E0.5070106@mock.com>
On Tue, 2007-10-23 at 11:13 -0700, Jeff Mock wrote:
> Is the Ocotea board (the original 440GX eval board) still interesting?
> I'm wrapping up a project using the 440GX, I started out hacking on the
> Ocotea board to get started, but we moved off Ocotea long ago onto our
> own hardware.
>
> I'm cleaning up the lab now that the project is nearly finished and I
> would like to give the board to someone that will put it to good use.
> I've sponged off this mailing list quite a lot, it's about time I give a
> little something back.
Well, the ocotea has an interesting "feature" related to the way the
ethernet PHY an EMAC interact which I haven't dealt with in the new EMAC
driver at this stage.
I -think- the Taishan I have may have the same issue though, in which
case I won't need it, but if not, I could have good use (or Josh in
Rochester) for one of these.
> The board has been hacked a little bit but still works fine. I just
> powered it up and it happily booted Linux via TFTP. The boot ROM now
> has u-boot, the original PIBs (or whatever) is long gone. All I ask is
> that you're self-sufficient and don't bug me too much about it...
>
> Can someone recommend a good home? Otherwise it will wind up in
> storeroom purgatory.
>
> jeff
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
next prev parent reply other threads:[~2007-10-23 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 18:13 Ocotea board? Jeff Mock
2007-10-23 20:36 ` Benjamin Herrenschmidt [this message]
2007-10-23 21:18 ` Josh Boyer
2007-10-24 17:09 ` Jeff Mock
2007-10-24 18:55 ` Charlie Ashton
2007-10-24 23:18 ` Jeff Mock
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=1193171771.2085.1.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=jeff@mock.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@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).