On Mon, Oct 07, 2002 at 03:36:44AM -0700, David S. Miller wrote:
> No one else can run these drivers so
> how could I expect someone else to maintain them ?
>
> This is a common misconception.
Double that. There are lots of drivers for embedded ARM stuff that
should probably be in the tree, but because they typically add
architecture specific crap to drivers to modify the IO support
the weird and wonderful way the hardware designer has come up with
to connect the device. Examples of this are cs89x0.c and smc9192.c.
I've tried to coerce people in Alans suggested direction (hiding
the architecture specific stuff behind inb and friends) but That
Doesn't Work because embedded people will not do this.
They'd rather keep their changes external. And thus, they stay
external.
The conventional "you will do it this way or else your patch will
not be merged" approach taken by Alan and others just doesn't bite
in the embedded world I'm afraid. Experience has proven this over
and over again.
And as final proof, the solution taken by two embedded companies is
to develop two completely separate cs89x0 driver from the existing one
(and then pick one/merge them) rather than fixing stuff in the way
suggested by Alan.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Oct 07 2002 - 22:00:58 EST