Re: Merging DRM and fbdev
From: Bill Davidsen
Date: Mon Oct 04 2004 - 14:56:48 EST
Jon Smirl wrote:
On Sun, 3 Oct 2004 11:38:39 -0700 (PDT), Mike Mestnik
<cheako911@xxxxxxxxx> wrote:
What about moving the DRM and FB specific code into there own per card
libs?
radeon - attached to hardware
radeon-drm
drm - library
radeon-fb
fb - library
fbcon - library
Fell free to convert the merged radeon driver in to a driver plus two
libs if you want. I'll accept the patch back. You'll need to wait
until I get the merged driver working.
What I don't want is two independent implementations of the hardware
initialization code like we currently have. The point of merging is to
make sure that a single logical driver programs the hardware is a
consistent way.
We spend so much time talking about splitting the radeon driver into
pieces. But I don't hear anyone saying I can't ship my product because
the radeon driver is 120K and all I can handle is 60K. I'm not going
to spend a week's work breaking things up and testing them just
because of some theoretical need for a non-existant embedded system.
When this hypothetical embedded system shows up the people making the
money off from the system can do the work.
Perhaps there might be some feedback from the embedded folks and/or
those who decide if these changes are what they want to go in the
kernel. If you're going to do something like this, one of the embedded
vendors might want to contribute to development. Clearly smaller
software parts have advantages, if resources were available to do it
split as part of the modification.
That would probably reduce the maintenence effort in the future as well.
--
-bill davidsen (davidsen@xxxxxxx)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/