On Thu, 2013-05-30 at 13:17 -0500, Larry Finger wrote: > I am trying to help an openSUSE user that needs driver alx for his wired device. > I see that backports has the code, but it cannot be configured due to the > following statements in drivers/net/wireless/atheros/Kconfig: I think you mean s/wireless/ethernet/, right? > config ALX > depends on !BACKPORT_KERNEL_2_6_28 > depends on n > tristate "Qualcomm Atheros L1F Gigabit Ethernet support" > depends on m > > The "depends on n" is the culprit. Is this deliberate because the driver code is > not ready, or is this a bug? This is an interesting side-effect of how the system works. The ALX Kconfig is added by a patch (patches/unified-drivers/network/0002-alx-make-kconfig/alx.patch) but the *code* itself needs to be copied from an external tree when building a backport tarball. To do this, the --extra-driver option in gentree.py exists. Are you using one of Luis's releases, or building an own backport tarball? If the former, Luis should probably include ALX since it's his driver. For the latter, see also the copy-list.alx file in the backports tree. Basically, the reason is that ALX isn't part of linux-next (yet), so needs to be included during the backporting process from another source, but the Kconfig is actually done in a patch that ships with backports, which is admittedly a bit confusing. johannes -- To unsubscribe from this list: send the line "unsubscribe backports" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
