public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "Kári Davíðsson" <kari.davidsson@marel•com>
To: "paul.gibson2074@gmail•com" <paul.gibson2074@gmail•com>
Cc: "linuxppc-dev@ozlabs•org" <linuxppc-dev@ozlabs•org>
Subject: Re: MPC5121 CAN and USB
Date: Thu, 15 Oct 2009 11:36:07 +0000	[thread overview]
Message-ID: <4AD70927.3030401@marel.com> (raw)
In-Reply-To: <4AD70585.40302@gmail.com>

Thank you Paul,

The kernel from the BSP on Freescale site is crashing on the CAN in my case=
 (might be a hardware bug).
I could not find the source for the kernel in the BSP or on the freescale s=
ite.

I had not looked at http://git.denx.de/?p=3Dlinux-2.6-denx.git;a=3Dshortlog=
;h=3Drefs/heads/ltib-mpc5121ads-20090602

I am now in the progress of cloning the linux-mpc512x git from denx and bui=
lding from it.
Hopefully that will help me.

rg
kd

Paul Gibson wrote:
> In my opinion the best place is the BSP available on the MPC5121e page=20
> on the Freescale site.
>=20
> I actually use the kernel in the git repository here which is similar to=
=20
> the BSP:
> http://git.denx.de/?p=3Dlinux-2.6-denx.git;a=3Dshortlog;h=3Drefs/heads/lt=
ib-mpc5121ads-20090602=20
> or here:
> http://git.denx.de/?p=3Dlinux-mpc512x.git;a=3Dsummary
>=20
> I have found both to be very stable, also with the CAN and USB.
>=20
> Paul
>=20
> K=E1ri Dav=ED=F0sson wrote:
>> Hello,
>>
>> Where is the most current linux work for the Freescale MPC5121 cpu=20
>> stored.
>> What I am specifically interested in at this time is the CAN and USB=20
>> subsystems.
>>
>> rg
>> kd
>>
>>
>> _______________________________________________
>> Linuxppc-dev mailing list
>> Linuxppc-dev@lists•ozlabs.org
>> https://lists.ozlabs.org/listinfo/linuxppc-dev
>>
>=20
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists•ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>=20

  reply	other threads:[~2009-10-15 11:36 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-14 10:54 UBIFS problem on MPC8536DS Felix Radensky
2009-10-14 12:36 ` Adrian Hunter
2009-10-14 13:02   ` Felix Radensky
2009-10-14 13:21   ` Felix Radensky
2009-10-14 16:44     ` Adrian Hunter
2009-10-14 17:48       ` Felix Radensky
2009-10-14 18:13         ` Scott Wood
2009-10-14 20:12           ` Felix Radensky
2009-10-15 20:07           ` Scott Wood
2009-10-16  5:01             ` Felix Radensky
2009-10-16 15:31               ` Scott Wood
2009-10-18  9:38                 ` Felix Radensky
2009-10-19 15:40                   ` Scott Wood
2009-10-19 19:39                     ` Felix Radensky
2009-10-19 19:47                       ` Scott Wood
2009-10-19 20:19                         ` Felix Radensky
2009-10-20 15:30                         ` Felix Radensky
2009-10-22  8:20                 ` Felix Radensky
2009-10-22 16:07                   ` Scott Wood
2009-10-15  9:54 ` Norbert van Bolhuis
2009-10-15 10:45   ` MPC5121 CAN and USB Kári Davíðsson
2009-10-15 11:20     ` Paul Gibson
2009-10-15 11:36       ` Kári Davíðsson [this message]
2009-10-15 18:30         ` Wolfgang Denk
2009-10-15 23:03           ` Paul Gibson
2009-10-15 23:10             ` Wolfgang Denk
2009-10-19  6:46               ` David Jander
2009-10-16 13:53           ` Kári Davíðsson
2009-10-15 12:49   ` UBIFS problem on MPC8536DS Felix Radensky

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=4AD70927.3030401@marel.com \
    --to=kari.davidsson@marel$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=paul.gibson2074@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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