All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: Wolfgang Grandegger <wg@domain.hid>,
	Xenomai core <Xenomai-core@domain.hid>
Subject: Re: [Xenomai-core] Build issue with rtcan and I-pipe for linux 2.6.36 on powerpc.
Date: Wed, 05 Jan 2011 21:39:15 +0100	[thread overview]
Message-ID: <4D24D6F3.8020007@domain.hid> (raw)
In-Reply-To: <4D24D4CE.6030600@domain.hid>

Jan Kiszka wrote:
> Am 05.01.2011 21:25, Gilles Chanteperdrix wrote:
>> Jan Kiszka wrote:
>>> Am 03.01.2011 11:32, Wolfgang Grandegger wrote:
>>>> Hi Gilles,
>>>>
>>>> the attached patch fixes the issue.
>>>>
>>> Nothing critical, but I think we should consistently wrap the other way
>>> around
>>>
>>> #if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,36)
>>> #define platform_device of_device
>>> #endif
>>>
>>> and update the users to the new style.
>> Err... Am I missing the obvious here? If you include
>> <linux/platform_device.h> on powerpc you then get a massive mess prior
>> to 2.6.36.
> 
> Maybe this is an exception, don't know the powerpc details, but
> generally our drivers should be written according to latest (supported)
> kernel APIs and then extended/wrapped/etc. to compile with older
> versions as well.

platform_device has existed for a long time in the 2.6 series: the
matching between platform_device and platform_driver is the hack which
replaces enumeration USB and PCI bus provide on embedded systems busses.

Some platforms introduced of_device to handle another kind of
enumeration: the device tree.

Now, it seems the member which were specific to of_device migrated to
the platform_device structure, so, the of_device structure was cancelled
completely, and replaced by platform_device all over the place.

At least, is it my understanding.

Now, we can typedef device_tree_device to be of_device on old kernels,
and platform_device on new kernels, but using of_device for this does
not seem stupid either.

-- 
					    Gilles.


      reply	other threads:[~2011-01-05 20:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-02 19:53 [Xenomai-core] Build issue with rtcan and I-pipe for linux 2.6.36 on powerpc Gilles Chanteperdrix
2011-01-03 10:32 ` Wolfgang Grandegger
2011-01-03 21:11   ` Gilles Chanteperdrix
2011-01-05 20:22   ` Jan Kiszka
2011-01-05 20:25     ` Gilles Chanteperdrix
2011-01-05 20:30       ` Jan Kiszka
2011-01-05 20:39         ` Gilles Chanteperdrix [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=4D24D6F3.8020007@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=Xenomai-core@domain.hid \
    --cc=jan.kiszka@domain.hid \
    --cc=wg@domain.hid \
    /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.