From: Andreas Larsson <andreas@gaisler.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
linux-can@vger.kernel.org, software@gaisler.com
Subject: Re: [PATCH] can: can_oc: Add driver for CAN_OC cores from Aeroflex Gaisler
Date: Wed, 26 Sep 2012 14:55:07 +0200 [thread overview]
Message-ID: <5062FB2B.2030700@gaisler.com> (raw)
In-Reply-To: <5062E9EE.2020300@pengutronix.de>
On 09/26/2012 01:41 PM, Marc Kleine-Budde wrote:
> On 09/26/2012 01:40 PM, Andreas Larsson wrote:
>> On 09/26/2012 11:56 AM, Wolfgang Grandegger wrote:
>>> On 09/26/2012 11:38 AM, Marc Kleine-Budde wrote:
>>>> On 09/25/2012 07:52 AM, Andreas Larsson wrote:
>>>>> This driver is for the sja1000 compatible CAN_OC cores from Aeroflex
>>>>> Gaisler available in the GRLIB VHDL IP core library.
>>>>
>>>> Why don't you describe a single sja1000 compatible core with an OF
>>>> device? The devices have indipendent address spaces and IRQs. With a
>>>> proper abstraction/desciption you would not need this driver.
>>>
>>> Right, at least I do not see anything special. The following DTS entry
>>> should do the jobs:
>>> [...]
>>
>> I'll look into this. Note that this is a SPARC device and not a PowerPC
>> device.
>
> The driver doesn't care about your processor :)
The driver doesn't care per se, but how the device tree is generated
differs compared to how it is done in PowerPC, at least for Leon SPARC.
I'll look into it. At the very least the Kconfig entry for
sja1000_of_platform could not solely depend on PPC_OF, but the more
important issue is the device tree differences.
Cheers,
Andreas
next prev parent reply other threads:[~2012-09-26 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 5:52 [PATCH] can: can_oc: Add driver for CAN_OC cores from Aeroflex Gaisler Andreas Larsson
2012-09-26 9:38 ` Marc Kleine-Budde
2012-09-26 9:56 ` Wolfgang Grandegger
2012-09-26 11:40 ` Andreas Larsson
2012-09-26 11:41 ` Marc Kleine-Budde
2012-09-26 12:55 ` Andreas Larsson [this message]
2012-09-26 12:58 ` Marc Kleine-Budde
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=5062FB2B.2030700@gaisler.com \
--to=andreas@gaisler.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=software@gaisler.com \
--cc=wg@grandegger.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox