linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: James F Dougherty <jfd@GigabitNetworks.COM>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: MPC824x
Date: Thu, 27 Sep 2001 11:59:07 -0400	[thread overview]
Message-ID: <3BB34CCB.5BD5EB2A@mvista.com> (raw)
In-Reply-To: 200109270627.XAA14161@krakatoa.gigabitnetworks.com


James F Dougherty wrote:

> Does anyone have a working port of ppclinux
> (preferably HHL 2.0) ?

The current linuxppc_2_4_devel tree has working 8245
and Sandpoint X3 support.  There was a subsequent
release of HHL 2.0 that added Sandpoint X3 support
(which already supported 8245) available to subscribers.

> .... The serial port seems
> trivial since it is a memmapped NS16552.

I don't personally have this completed in Linux because
I haven't used any boards that utilize this feature.
It seems everyone took a working 8240 design and just
adapted it to 8245, and rather than rewrite boot roms
it was easier to just drop hardware on the board.

> has the port from 8240 to 8245 been relatively
> easy?

It depends how far you want to push the differences.
>From the Linux perspective today, there isn't any
difference between 8240 and 8245.  Due to the subtle
changes in the 8245, you could make it look quite different.
It just depends on your requirements.

> .... It seems like the right place to start
> would be SandPoint X3 with an 8245PMC module.

That would be my suggestion.


	-- Dan

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

  reply	other threads:[~2001-09-27 15:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-27  6:27 MPC824x James F Dougherty
2001-09-27 15:59 ` Dan Malek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-09-27  6:30 MPC824x James F Dougherty
2001-09-27 16:00 ` MPC824x Dan Malek

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=3BB34CCB.5BD5EB2A@mvista.com \
    --to=dan@mvista.com \
    --cc=jfd@GigabitNetworks.COM \
    --cc=linuxppc-embedded@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).