From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: Jeff Garzik <jeff@garzik.org>,
netdev@vger.kernel.org, Russell King <rmk@arm.linux.org.uk>
Subject: Re: [PATCH] cs89x0: add support for i.MX31ADS ARM board
Date: Tue, 16 Sep 2008 14:47:33 +0200 [thread overview]
Message-ID: <48CFAAE5.80805@xenomai.org> (raw)
In-Reply-To: <20080916124422.GC18556@xi.wantstofly.org>
Lennert Buytenhek wrote:
> On Sun, Sep 14, 2008 at 04:13:45PM +0200, Gilles Chanteperdrix wrote:
>
>>> I don't have the original patch in my netdev box anymore, but what
>>> seems to me should be done is to add a platform driver interface to
>>> the cs89x0 driver, like how most other non-PCI non-other-autoconf-
>>> supporting-bus net drivers do it. (There aren't too many -- grep
>>> for platform_driver_register in drivers/net/*)
>>>
>>> Then the knowledge about I/O addresses and IRQ lines can live in the
>>> platform code (where it belongs) instead of having it all in the driver
>>> (where it doesn't belong). And all the IXDP2351 and IXDP2X01 ifdefs
>>> can disappear as well. And the ->readword()/->writeword() hacks that
>>> need to be done for IXDP2351 and IXDP2X01 and PNX can then just be an
>>> (optional) set of platform data methods, with a fallback to the default
>>> one if they aren't passed in.
>>>
>>> The question is whether someone wants to step up and do that work.
>>> cs89x0 has seen a lot of drive-by patching by people looking to satisfy
>>> their needs, but noone has stepped up to give it the proper love and
>>> care that it deserves.
>>>
>>> Gilles, are you willing to do the platform driver conversion? If not,
>>> then I guess we should just merge this patch as-is (after you explain
>>> why you need to stub out reset_chip() on your board, as no other board
>>> seems to need this?).
>> Hi Lennert,
>>
>> When I published this patch, I had access to an i.MX31ADS board, and
>> getting Linux to work on this board was just a necessity to get my job
>> done. I did this by copying the parts I needed working (the serial
>> console and ethernet driver) from the Freescale tree.
>>
>> Now, I am no longer working on this, so I can not test any modification.
>> And I do not even know why people at Freescale did what they did.
>
> I guess then we should just wait until the Freescale people submit it.
I will be able to test the modification soon. I will repost the patch on
linux-arm-kernel after this test.
--
Gilles.
next prev parent reply other threads:[~2008-09-16 12:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-09 17:13 [PATCH] cs89x0: add support for i.MX31ADS ARM board Gilles Chanteperdrix
2008-09-14 0:29 ` Jeff Garzik
2008-09-14 12:03 ` Lennert Buytenhek
2008-09-14 14:13 ` Gilles Chanteperdrix
2008-09-16 12:44 ` Lennert Buytenhek
2008-09-16 12:47 ` Gilles Chanteperdrix [this message]
2008-09-16 12:52 ` Lennert Buytenhek
2008-09-16 12:54 ` Gilles Chanteperdrix
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=48CFAAE5.80805@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=buytenh@wantstofly.org \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).