All of lore.kernel.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:37:42 +0200	[thread overview]
Message-ID: <4C10B266.3070601@grandegger.com> (raw)
In-Reply-To: <201006101129.15581.roman.fietze@telemotive.de>

On 06/10/2010 11:29 AM, Roman Fietze wrote:
> Hello Wolfram,
> 
> On Thursday 10 June 2010 10:59:23 Wolfram Sang wrote:
> 
>> The mainline kernel works fine here with Phytec based MPC5xxx-boards.
> 
> Reading your answer made me hope again, and I just pulled the newest
> HEAD from the mainline kernel and tried it once more. Now it compiles.
> Thanks for retriggering me again.
> 
> All the other's sill have problems, except pengutronix, most of them
> with an inconsistency (with the socket CAN files?), which shows up as
> 
>   'struct can_bittime_std' declared inside parameter list
> 
> in net/can/dev.c:69

With all other you mean the linux-2.6-denx tree!? These seem to be some
reminders of the old Socket-CAN support merged into that tree (master
branch). I will clean that up a.s.a.p. Nevertheless, whenever possible,
you should use the mainline kernel.

> So I assume we will switch to the mainline kernel, which we already
> use for Atom based x86 development on the MEN boards.

DENX tries to push patches upstream as fast as possible and new projects
are usually based on the mainline kernel tree.

Wolfgang.


> 
> Thanks once more
> 
> Roman
> 

  reply	other threads:[~2010-06-10  9:37 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 [this message]
2010-06-10  9:25 ` Wolfgang Grandegger

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=4C10B266.3070601@grandegger.com \
    --to=wg@grandegger.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=roman.fietze@telemotive.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.