Btw, I only noticed now, because I normally don't build DVB on my main
machine with "oldconfig" - why the hell does DVB add tuners with
"default m"?
Why would *anybody* with an old config ever want to get those new
drivers as modules?
Get rid of all the stupid
default m if DVB_FE_CUSTOMISE
because there's no reason for them. If somebody wants that module,
they can damn well press the 'm' button. There's absolutely no reason
for it to default to on.
This is true of *all* drivers. No driver (and certainly DVB is not at
all an exception) is so important that it should be "default m" (or
y).
There are a few valid reasons to use "default m/y", but I don't see
that that is the case here:
- if you have an *existing* driver that got split up, and "make
oldconfig" with that old driver enabled would result in it no longer
supporting the same capability, then a
default OLD_DRIVER_WAS_ENABLED
is appropriate - it makes "oldconfig" work the way people expect it to work.
But this is only when that piece of hardware used to be supported
already, it's irrelevant for new hardware.
- if it's *such* a basic piece of hardware that you simply don't want
to bother the user with an insane default. Like supporting an ATKBD
driver on a PC etc.
This simply isn't true for media devices.
So stop doing the silly "enable this driver by default for old
configurations". It's *wrong*.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
