Hi,
On Sat, 25 Jun 2005, Vojtech Pavlik wrote:
> > I skipped 2.6.11 on my laptop, so I'm only noticing this problem now.
> > You didn't really answer the question, why has the _default_ been changed,
> > giving users the possibility to change the defaults is fine, but why is it
> > necessary to break existing setups?
>
> Because we added a driver for the pad. There was none before and the pad
> had to work in compatibility mode. It seems more beneficial to me to
> have the driver enabled by default (saving a lot of #ifdefs) than to
> keep perfect compatibility with a no-driver situation.
Adding a driver for it is nice, but that still doesn't question: why does
it change the default settings? If you can't restore the defaults
settings, then just detect the hardware but don't change it until it's
explicitely requested somehow.
bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
