Dave Jones <[email protected]> writes:
> A lot of these drivers show up on pretty much every arch
> regardless of whether they make sense. This adds a bunch
> of additional dependancies tying down platform specific drivers
> that are unlikely to be used on other archs.
>
> Signed-off-by: Dave Jones <[email protected]>
>
> --- linux-2.6.11/drivers/i2c/busses/Kconfig~ 2005-04-16 01:05:36.000000000 -0400
> +++ linux-2.6.11/drivers/i2c/busses/Kconfig 2005-04-16 01:06:09.000000000 -0400
> @@ -376,7 +376,7 @@ config SCx200_I2C_SDA
>
> config SCx200_ACB
> tristate "NatSemi SCx200 ACCESS.bus"
> - depends on I2C && PCI
> + depends on SCx200_I2C && PCI
> help
> Enable the use of the ACCESS.bus controllers of a SCx200 processor.
This is wrong. The ACCESS.bus driver is an alternative to the
bitbanging driver and it's possible to use this driver even without
any other SCx200 stuff configured into the kernel.
/Christer
--
"Just how much can I get away with and still go to heaven?"
Freelance consultant specializing in device driver programming for Linux
Christer Weinigel <[email protected]> http://www.weinigel.se
-
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]
