From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Stanislaw Gruszka <stf_xl@wp.pl>,
linux-ide@vger.kernel.org, Andrew Victor <linux@maxim.org.za>,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH 2/3] ide: add at91_ide driver
Date: Fri, 06 Feb 2009 20:20:03 +0300 [thread overview]
Message-ID: <498C7143.3090508@ru.mvista.com> (raw)
In-Reply-To: <200902061750.24258.bzolnier@gmail.com>
Bartlomiej Zolnierkiewicz wrote:
>>>> Can you answer the simple question: why we should try to support
>>>>two incompatible chips with a single driver? Because the driver name
>>>>will be shorter? :-)
>>>>Very funny. I think patch adding RM9200 support to this driver will
>>>>have less
>>>>than 50 lines changeset, whereas writing new driver would be about
>>>>500 lines.
>>> This approach is so broken-minded that I'm just out words to argue
>>>any more.
>>> Let's then support say all the PCI IDE chipsets with the single
>>>driver (actully, there was a driver that tried to support 2
>>>incompatible Promise chip families but it got split finally).
> Actually it was the case for Linux during early 2.4.x days. :)
And I've spent considerable time fixing this driver in 2.4.20. :-)
> [ Probably for historical reasons. ]
>> To say the truth, there are stil at least 2 examples of such drivers:
>>hpt366 and aec6210. While the former is justified by the bogus chip
> The former can be probably still improved with hpt3xx_main.c and chipset
> family specific code separated into hpt36x.c etc.
Don't think that there's even enough common code for hpt3xx_main.c.
>>identification poilicy used by the vendor, the latter has no
>>justification at all.
> Patches are always warmly welcomed.
There is just to much I'd like to be done with this driver and too little
time to do that. :-)
> Thanks,
> Bart
MBR, Sergei
next prev parent reply other threads:[~2009-02-06 17:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 10:47 [PATCH 2/3] ide: add at91_ide driver Stanislaw Gruszka
2009-02-04 12:19 ` Sergei Shtylyov
2009-02-04 14:47 ` Stanislaw Gruszka
2009-02-04 16:04 ` Sergei Shtylyov
2009-02-04 16:08 ` Sergei Shtylyov
2009-02-05 15:01 ` Stanislaw Gruszka
2009-02-05 16:09 ` Sergei Shtylyov
2009-02-05 20:00 ` Andrew Victor
2009-02-05 20:03 ` Sergei Shtylyov
2009-02-06 9:35 ` Stanislaw Gruszka
2009-02-06 10:55 ` Sergei Shtylyov
2009-02-06 16:50 ` Bartlomiej Zolnierkiewicz
2009-02-06 17:20 ` Sergei Shtylyov [this message]
2009-02-05 21:23 ` Bartlomiej Zolnierkiewicz
2009-02-05 23:31 ` Sergei Shtylyov
2009-02-06 16:36 ` Bartlomiej Zolnierkiewicz
2009-02-08 0:10 ` Sergei Shtylyov
2009-02-08 11:39 ` Sergei Shtylyov
2009-02-08 22:58 ` Sergei Shtylyov
2009-02-09 19:48 ` Bartlomiej Zolnierkiewicz
2009-02-06 9:30 ` Stanislaw Gruszka
2009-02-06 10:36 ` Sergei Shtylyov
2009-02-06 10:47 ` Stanislaw Gruszka
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=498C7143.3090508@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=bzolnier@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=stf_xl@wp.pl \
/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).