public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger•com>
To: Roman Fietze <roman.fietze@telemotive•de>
Cc: linuxppc-dev@lists•ozlabs.org
Subject: Re: CAN Subsystem and MPC52xx onboard controller
Date: Thu, 10 Jun 2010 11:25:38 +0200	[thread overview]
Message-ID: <4C10AF92.9060400@grandegger.com> (raw)
In-Reply-To: <201006101041.27926.roman.fietze@telemotive.de>

On 06/10/2010 10:41 AM, Roman Fietze wrote:
> Hello List Members,
> 
> I have tried multiple versions/branches and git repos (torvalds,
> benh/{next,master}, denx, pengutronix, ...) to get a 2.6.34 or HEAD
> version of that repos that compiles w/o errors when the CAN subsystem
> is enabled and the MPC5xxx onboard driver is selected starting with
> the lite5200b_defconfig.
> 
> Until now I'm out of luck. If other's also have compile problems I can
> of course offer to try to dig into the sources.

Hm, kernel.org's "linux-2.6.34.tar.bz2" builds here just fine with
lite5200b_defconfig and Socket-CAN support enabled for the MSCAN. I can
imaging that there are issues with more recent "-rc" versions due to
Grant's OF platform device generalization. Also the DTS entries entries
for MSCAN in lite5200b.dts seem OK.

> Q0:
> 
> I'm somewhat unsure what repos to use in general to develop using the
> 2.6 on a Lite5200B compatible board (for the 2.4 we always used the
> DENX repos).

Please use the mainline kernel for that board.

Wolfgang.

      parent reply	other threads:[~2010-06-10  9:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10  8:41 CAN Subsystem and MPC52xx onboard controller Roman Fietze
2010-06-10  8:59 ` Wolfram Sang
2010-06-10  9:29   ` Roman Fietze
2010-06-10  9:37     ` Wolfgang Grandegger
2010-06-10  9:25 ` Wolfgang Grandegger [this message]

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=4C10AF92.9060400@grandegger.com \
    --to=wg@grandegger$(echo .)com \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=roman.fietze@telemotive$(echo .)de \
    /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