Which 2.6 kernel for MPC5200

Which 2.6 kernel for MPC5200

[Babarovic Ivica]

Hi!

What kernel should I get/pull for MPC5200 clone board.
I've been away from coding on mpc5200 for quite some time now.
I've read some archives from ML.
Git repo on Sylvain Munauts url:
http://gitbits.246tNt.com/gitbits/linux-2.6-mpc52xx.gitpage
isn't working. Nothing on http://*git*.secretlab.ca/cgi-bin/*gitweb*.cgi
<http://git.secretlab.ca/cgi-bin/gitweb.cgi> to.

I've pulled the sources from kernel.org git server.
git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
linux-2.6-mpc52xx

How recent are these sources?

Regards,
I.

Re: Which 2.6 kernel for MPC5200

[Grant Likely]

On 9/10/07, Babarovic Ivica <ivica.babarovic@asist.si> wrote:
> Hi!
>
> What kernel should I get/pull for MPC5200 clone board.
> I've been away from coding on mpc5200 for quite some time now.
> I've read some archives from ML.
> Git repo on Sylvain Munauts url:
> http://gitbits.246tNt.com/gitbits/linux-2.6-mpc52xx.gitpage
> isn't working. Nothing on http://*git*.secretlab.ca/cgi-bin/*gitweb*.cgi
> <http://git.secretlab.ca/cgi-bin/gitweb.cgi> to.
>
> I've pulled the sources from kernel.org git server.
> git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> linux-2.6-mpc52xx

My 52xx git tree became way out of date, so I dropped it from the
server.  Best bet is to use mainline which gives your everything
except the drivers that use the bestcomm DMA engine (like Ethernet).

Then you need to apply the bestcomm patches.  You can get them here:

http://www.246tnt.com/mpc52xx/dev_full/

Have fun,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

Re: Which 2.6 kernel for MPC5200

[Jon Smirl]

[-- Attachment #1: Type: text/plain, Size: 1584 bytes --]

On 9/10/07, Grant Likely <grant.likely@secretlab.ca> wrote:
> On 9/10/07, Babarovic Ivica <ivica.babarovic@asist.si> wrote:
> > Hi!
> >
> > What kernel should I get/pull for MPC5200 clone board.
> > I've been away from coding on mpc5200 for quite some time now.
> > I've read some archives from ML.
> > Git repo on Sylvain Munauts url:
> > http://gitbits.246tNt.com/gitbits/linux-2.6-mpc52xx.gitpage
> > isn't working. Nothing on http://*git*.secretlab.ca/cgi-bin/*gitweb*.cgi
> > <http://git.secretlab.ca/cgi-bin/gitweb.cgi> to.
> >
> > I've pulled the sources from kernel.org git server.
> > git clone
> > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> > linux-2.6-mpc52xx
>
> My 52xx git tree became way out of date, so I dropped it from the
> server.  Best bet is to use mainline which gives your everything
> except the drivers that use the bestcomm DMA engine (like Ethernet).
>
> Then you need to apply the bestcomm patches.  You can get them here:
>
> http://www.246tnt.com/mpc52xx/dev_full/

I just finished rebasing the Efika version of those patches to current mainline.

I'm working on merging support for my Phytec pcm030 into them.
After I get stable the plan is to switch over to Domon's new FEC driver.


>
> Have fun,
> g.
>
> --
> Grant Likely, B.Sc., P.Eng.
> Secret Lab Technologies Ltd.
> grant.likely@secretlab.ca
> (403) 399-0195
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>


-- 
Jon Smirl
jonsmirl@gmail.com

[-- Attachment #2: mpc.tgz --]
[-- Type: application/x-gzip, Size: 45497 bytes --]

Re: Which 2.6 kernel for MPC5200

[Wolfgang Denk]

In message <46E57A9D.2020506@asist.si> you wrote:
> 
> What kernel should I get/pull for MPC5200 clone board.
> I've been away from coding on mpc5200 for quite some time now.
> I've read some archives from ML.
> Git repo on Sylvain Munauts url:
> http://gitbits.246tNt.com/gitbits/linux-2.6-mpc52xx.gitpage
> isn't working. Nothing on http://*git*.secretlab.ca/cgi-bin/*gitweb*.cgi
> <http://git.secretlab.ca/cgi-bin/gitweb.cgi> to.

We have working support for  the  MPC5200  (based  on  Sylvain's  and
Grant's)  code  in  our  linux-2.6-denx  repository, at least for the
lite5200b and TQM5200 boards; I recommend to  stick  with  commit  ID
85ab69c5  = tag DENX-2007-08-30-1748 at the moment, as the 2.6.23-rc5
coe is not completely tested yet. [Well, actually *all* this is  work
in progress...]

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
There are always alternatives.
	-- Spock, "The Galileo Seven", stardate 2822.3

Re: Which 2.6 kernel for MPC5200

[Robert Schwebel]

Jon,

On Mon, Sep 10, 2007 at 07:22:39PM -0400, Jon Smirl wrote:
> > Then you need to apply the bestcomm patches. You can get them here:
> >
> > http://www.246tnt.com/mpc52xx/dev_full/
>
> I just finished rebasing the Efika version of those patches to current mainline.
>
> I'm working on merging support for my Phytec pcm030 into them.

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.

Robert
-- 
Pengutronix - Linux Solutions for Science and Industry
Entwicklungszentrum Nord     http://www.pengutronix.de

Re: Which 2.6 kernel for MPC5200

[Jon Smirl]

On 9/12/07, Robert Schwebel <r.schwebel@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.

-- 
Jon Smirl
jonsmirl@gmail.com

Re: Which 2.6 kernel for MPC5200

[Grant Likely]

On 9/12/07, Jon Smirl <jonsmirl@gmail.com> wrote:
> On 9/12/07, Robert Schwebel <r.schwebel@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).

Cheers,
g.
>
> --
> Jon Smirl
> jonsmirl@gmail.com
>


-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

Re: Which 2.6 kernel for MPC5200

[Jon Smirl]

On 9/12/07, Grant Likely <grant.likely@secretlab.ca> wrote:
> On 9/12/07, Jon Smirl <jonsmirl@gmail.com> wrote:
> > On 9/12/07, Robert Schwebel <r.schwebel@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.


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


-- 
Jon Smirl
jonsmirl@gmail.com

Re: Which 2.6 kernel for MPC5200

[Grant Likely]

On 9/12/07, Jon Smirl <jonsmirl@gmail.com> wrote:
> On 9/12/07, Grant Likely <grant.likely@secretlab.ca> wrote:
> > On 9/12/07, Jon Smirl <jonsmirl@gmail.com> wrote:
> > > On 9/12/07, Robert Schwebel <r.schwebel@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've got it it my tree.  I'll try to push it out today.

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

Re: Which 2.6 kernel for MPC5200

[Domen Puncer]

On 12/09/07 12:16 -0400, Jon Smirl wrote:
> On 9/12/07, Grant Likely <grant.likely@secretlab.ca> wrote:
> > On 9/12/07, Jon Smirl <jonsmirl@gmail.com> wrote:
> > > On 9/12/07, Robert Schwebel <r.schwebel@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.


	Domen

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

Re: Which 2.6 kernel for MPC5200

[Jon Smirl]

On 9/12/07, Grant Likely <grant.likely@secretlab.ca> wrote:
> On 9/12/07, Jon Smirl <jonsmirl@gmail.com> wrote:
> > On 9/12/07, Robert Schwebel <r.schwebel@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.

I just noticed mail from Paul Mackerras
"Patches added to powerpc.git for-2.6.24 branch"

The MPC5200 ones aren't in the list.


> 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).
>
> Cheers,
> g.
> >
> > --
> > Jon Smirl
> > jonsmirl@gmail.com
> >
>
>
> --
> Grant Likely, B.Sc., P.Eng.
> Secret Lab Technologies Ltd.
> grant.likely@secretlab.ca
> (403) 399-0195
>


-- 
Jon Smirl
jonsmirl@gmail.com

Re: Which 2.6 kernel for MPC5200

[Jon Smirl]

On 9/12/07, Domen Puncer <domen.puncer@telargo.com> wrote:
> On 12/09/07 12:16 -0400, Jon Smirl wrote:
> > On 9/12/07, Grant Likely <grant.likely@secretlab.ca> wrote:
> > > On 9/12/07, Jon Smirl <jonsmirl@gmail.com> wrote:
> > > > On 9/12/07, Robert Schwebel <r.schwebel@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@gmail.com
> > > >
> > >
> > >
> > > --
> > > Grant Likely, B.Sc., P.Eng.
> > > Secret Lab Technologies Ltd.
> > > grant.likely@secretlab.ca
> > > (403) 399-0195
> > >
> >
> >
> > --
> > Jon Smirl
> > jonsmirl@gmail.com
>


-- 
Jon Smirl
jonsmirl@gmail.com