Which 2.6 kernel for MPC5200

Jon Smirl jonsmirl at gmail.com
Fri Sep 14 04:48:01 EST 2007


On 9/12/07, Domen Puncer <domen.puncer at telargo.com> wrote:
> On 12/09/07 12:16 -0400, Jon Smirl wrote:
> > On 9/12/07, Grant Likely <grant.likely at secretlab.ca> wrote:
> > > On 9/12/07, Jon Smirl <jonsmirl at gmail.com> wrote:
> > > > On 9/12/07, Robert Schwebel <r.schwebel at pengutronix.de> wrote:
> > > > > We have the OSELAS.BSP patch stack for the PCM030 working ontop of
> > > > > Linus' git. It still uses an older version of the Bestcom patches, so if
> > > > > you do some work in that area, please keep me informed about your
> > > > > progress.
> > > >
> > > > What is the best way to proceed? I need to be on current git since we
> > > > are integrating a wireless driver that is tracking current git and the
> > > > mac80211 work.
> > > >
> > > > I have Phytec (pcm030) and Efika hardware but I don't have a 5200lite.
> > > > Our prototype hardware uses the pcm030 module on a custom baseboard.
> > > >
> > > > The best thing for me would be to get a FEC driver merged. That is the
> > > > largest piece of code  that is floating around. Getting that merged
> > > > would give me a stable base to build future patches on.
> > > >
> > > > I'd also like to get support for the pcm030 (minus real-time) merged.
> > > > That isn't a lot of code once FEC is in the kernel.
> > > >
> > > > Domen has posted this driver "[RFC PATCH v0.1] net driver: mpc52xx
> > > > fec". I can work on breaking that up, but I don't have a 5200lite so I
> > > > will have to port to pcm030. I don't want to start on this if someone
> > > > else is already doing it.
> > >
> > > Sylvain's bestcomm patches need be cleaned up and resubmitted before
> > > the next merge window opens.  AFAIK, the code is pretty much ready,
> > > and all the comments have been addressed.  All that is required is the
> > > final push to tidy the patchset and post to the list one more time.
> > > Sylvain said that he was going to get this done last weekend, but I
> > > haven't heard back from him yet.
> > >
> > > Sylvain, if you need help, please let me know.  I'll happily take on
> > > the last bit of tidy work if that's what is needed to be finished
> > > before the merge window.  (And it needs to be ready *before*, not
> > > during if I'm judging the prevailing winds correctly).
> >
> > Is a version of this patch set that has been rebased to current git
> > available? If I have a starting point I can begin working on the
> > pcm030 support. pcm030 already works, it is just out of tree.
>
> I think these patches are "latest":
> http://www.246tnt.com/mpc52xx/dev_full/
> Applying them to -git should not be a problem, I don't remember anything
> tricky, but if you have problems, I can send you patches agains mainline.
>
> BTW. I posted FEC patch v2, which will hopefully be merged.

I just booted your code successfully on current Linus git with a Phytec pcm030.

There is a timeout issue that is probably related to the specific
Ethernet PHY chip used on the pcm030. I'm looking into it now.

[    1.313708] net eth0: attached phy 0 to driver Generic PHY
[    2.320013] Sending DHCP requests ...... timed out!
[   81.968863] IP-Config: Retrying forever (NFS root)...
[   82.477527] net eth0: attached phy 0 to driver Generic PHY
[   83.487809] Sending DHCP requests .<6>PHY: f0003000:00 - Link is Up
- 100/Full
[   86.323795] ., OK
[   88.579802] IP-Config: Got DHCP answer from 192.168.1.200, my
address is 192.168.1.5
[   88.587923] IP-Config: Complete:

>
>
>         Domen
>
> >
> >
> > >
> > > Cheers,
> > > g.
> > > >
> > > > --
> > > > Jon Smirl
> > > > jonsmirl at gmail.com
> > > >
> > >
> > >
> > > --
> > > Grant Likely, B.Sc., P.Eng.
> > > Secret Lab Technologies Ltd.
> > > grant.likely at secretlab.ca
> > > (403) 399-0195
> > >
> >
> >
> > --
> > Jon Smirl
> > jonsmirl at gmail.com
>


-- 
Jon Smirl
jonsmirl at gmail.com


More information about the Linuxppc-embedded mailing list