On Thu, Nov 08, 2007 at 08:18:54AM +0000, Al Viro wrote:
> On Thu, Nov 08, 2007 at 04:31:05PM +0900, Magnus Damm wrote:
> > config AX88796
> > tristate "ASIX AX88796 NE2000 clone support"
> > - depends on ARM || MIPS
> > + depends on ARM || MIPS || SUPERH
>
> You know, that really sucks more and more. How about doing the following:
> a) making it depend on PLAT_HAS_AX88796
> b) adding selects for all subarchitectures that have the corresponding
> platform device
> and setting that as a uniform policy for platform drivers? For things like
> SM501 we would do
> config MFD_SM501
> depends on PCI || PLAT_HAS_SM501
> etc.
>
> Seriously, folks, we are getting shitloads of platform drivers with no
> dependencies whatsoever, needed on a handful of targets and occasionally
> failing to build on unrelated architectures. Moreover, having a list
> of architectures in dependencies for each of those suckers is a PITA
> from the conflict POV. Not to mention platform drivers that fall into
> the mainline kernel with not a single platform device for them, etc.
>
> Comments?
commit def47c5095d53814512bb0c62ec02dfdec769db1
Author: Jeff Garzik <jeff@xxxxxxxxxx>
Date: Tue Jul 10 14:06:48 2007 -0400
[netdrvr] Fix dependencies for ax88796 ne2k clone driver
It needs writesb(), not available on all platforms.
Signed-off-by: Jeff Garzik <jeff@xxxxxxxxxx>
diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig
index a3bef22..a64c2fb 100644
--- a/drivers/net/Kconfig
+++ b/drivers/net/Kconfig
@@ -199,6 +199,7 @@ source "drivers/net/arm/Kconfig"
config AX88796
tristate "ASIX AX88796 NE2000 clone support"
+ depends on ARM || MIPS
select CRC32
select MII
help
If writesb() is not an official API then maybe the answer should have been
to either add that API to other architectures or fix the driver.
I guess this incident means I need to go through all Kconfig* files to
see what bogus architecture dependencies on MIPS or !MIPS exist ...
Ralf
-
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
