All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiaoshan Zuo <xzuo@vinesystech.com>
To: Huailin Chen <chen_huailin@yahoo.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: any one use 750fx/MV64360
Date: Wed, 21 Jan 2004 21:15:35 -0800	[thread overview]
Message-ID: <20040122051535.GA15242@vinesystech.com> (raw)
In-Reply-To: <20040122034730.55118.qmail@web21409.mail.yahoo.com>


Thanks for the comments. Those are certainly good points. What
OS did you use? Any suggestions on the Linux kernel to use?
BTW, your website is just interesting.

Xiaoshan

**** Huailin Chen wrote ****
> My 2 cents:
>
> I happened to use all your options these years:--(.
>
> 750fx + 64260
> it should be good enough if you don't have
> MP(Multi-CPU) demand for running smp-os on top of it.
> The reason is obivous: 750fx is G3. The MEI protocol
> may not be prefered if your system happens to be a
> high-end applicances.
>
> 750fx + 64360
>
> if you do want to stay 750 and need SMP, you may have
> to use 64360. Check out Marvell FAE people to
> understand their Arbiter part, which have some fixes
> for SMP support. If you have legacy issue, note that
> some tiny porting work needed for 64360 part.
>
> 7447 + 64260
> No one would go for this option
>
> 7447 + 64360
>
> Well, G4+ MES(R)I is born to support SMP system. So,
> if you concern this part, do go for it. One thing you
> need talk to your hardware board group is: Powerp
> Consumption. If you guys are able to live with it, go
> for it:-).
>
> Also, if you have legacy codes under IBM 750-based
> system, please pay high alert on driver part. For
> example, Out of Order issue when under Non-Cachable
> and Guard......One missing will make your driver all
> srew up. For more detail, you are welcome to talk to
> me.
>
> Good luck,
> Huailin Chen
> www.xtrj.org
>
>
>
>
> --- Xiaoshan Zuo <xzuo@vinesystech.com> wrote:
> >
> > Hello,
> >
> > We are planning design a custom board. The preferred
> > cpu is IBM 750FX,
> > the bridge is going to be Marvell 64360. Depending
> > on the software
> > support, we may alter our plan to use either
> > 750FX/64260 or Motorola
> > 7447/64360/64260. It seems that 64360 is not
> > supported in stock kernel,
> > there is galieo tree for that, but I am not sure the
> > code is really
> > stable. Anyone has experience using 750fx/64360?
> > Which version of
> > gcc/kernel/u-boot should I use? If that is not a
> > good option, then how
> > about 750FX/64260 or Motorola 7447/64360/64260? Any
> > suggestions/comments
> > will be appreciated.
> >
> > Thanks,
> >
> > Xiaoshan
> >
> >
>
>
> Yahoo! SiteBuilder - Free web site building tool. Try it!
> http://webhosting.yahoo.com/ps/sb/

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

  reply	other threads:[~2004-01-22  5:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-21 23:59 any one use 750fx/MV64360 Xiaoshan Zuo
2004-01-22  3:47 ` Huailin Chen
2004-01-22  5:15   ` Xiaoshan Zuo [this message]
2004-01-22 18:58 ` FYI: Free Online Book: Inside Linux Kernel and PowerPC Huailin Chen
2004-01-25  1:07   ` Jon Masters
2004-01-27 13:59   ` Kenneth Johansson

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=20040122051535.GA15242@vinesystech.com \
    --to=xzuo@vinesystech.com \
    --cc=chen_huailin@yahoo.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 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.