linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michele.Pallaro@alcatel.it
To: Matt Porter <mporter@kernel.crashing.org>
Cc: eric lescouet <eric.lescouet@Jaluna.COM>,
	linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Linux kernel and u-boot for mpc8540
Date: Thu, 05 Feb 2004 17:36:03 +0100	[thread overview]
Message-ID: <402270F3.AD39E32@alcatel.it> (raw)
In-Reply-To: 20040205091232.A15092@home.com


I try to download from ppc.bkbits.net, but I have a proxy problem.
About the metrowerks I'll try to contact.

Thanks
    Michele

Matt Porter wrote:

> On Thu, Feb 05, 2004 at 10:32:48AM +0100, eric lescouet wrote:
> >
> > Michele,
> >
> > Support for mpc8540 is already in linuxppc-2.4 tree.
> > see ppc.bkbits.net
>
> Actually, the linuxppc-2.4 support is incomplete, there's no TSEC/FEC
> driver or other on-chip peripheral drivers in that tree to make it
> really useful. You could just use a PCI network card to nfsroot a
> filesystem and get started, though.
>
> http://www.metrowerks.com/MW/Develop/Embedded/Linux/BSP.htm has
> an 8560ADS BSP for download...it probably has some drivers for
> on-chip peripherals included.
>
> BTW, you'll need the following patch to linuxppc-2.4 to fix outbound
> PCI mem cycles:
>
> ===== arch/ppc/platforms/mpc85xx_ads_common.c 1.3 vs edited =====
> --- 1.3/arch/ppc/platforms/mpc85xx_ads_common.c Thu Jan 22 12:58:25 2004
> +++ edited/arch/ppc/platforms/mpc85xx_ads_common.c      Thu Feb  5 09:10:34 2004@@ -316,8 +316,8 @@
>         pci->piwar2 = 0;
>         pci->piwar3 = 0;
>
> -       /* Setup 128M outbound mem window @ 0xe0000000 */
> -       pci->potar1 = 0x00000000;
> +       /* Setup 128M Phys:PCI 1:1 outbound mem window @ 0xe0000000 */
> +       pci->potar1 = (MPC85XX_ADS_PCI_LOWER_MEM >> 12) & 0x000fffff;
>         pci->potear1 = 0x00000000;
>         pci->powbar1 = (MPC85XX_ADS_PCI_LOWER_MEM >> 12) & 0x000fffff;
>         pci->powar1 = 0x8004401a;       /* Enable, Mem R/W, 128M */
>
> -Matt


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

  reply	other threads:[~2004-02-05 16:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-05  7:45 Linux kernel and u-boot for mpc8540 Michele.Pallaro
2004-02-05  9:32 ` eric lescouet
2004-02-05 16:12   ` Matt Porter
2004-02-05 16:36     ` Michele.Pallaro [this message]
2004-02-05 20:47     ` Matt Porter
2004-02-06  6:00     ` Kumar Gala
  -- strict thread matches above, loose matches on Subject: below --
2004-02-05  7:55 Klaus Popp
2004-02-05  8:27 ` Wolfgang Denk
2004-02-05  8:35 Klaus Popp

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=402270F3.AD39E32@alcatel.it \
    --to=michele.pallaro@alcatel.it \
    --cc=eric.lescouet@Jaluna.COM \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=mporter@kernel.crashing.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).