Michael Buesch wrote: > Yes, please introduce a feature-bitfield at some location in SHM that's unused > by the proprietary firmware. This bitfields would contain a bit for QoS and > a bit for hwcrypto. > Also change your firmware so the driver detects it as open-source firmware. > I think that's done by writing 0xFFFF to the date/time field in SHM. I don't > quite remember, but it's something like that. > Note that this might mean that the firmware watchdog in the driver will trigger, > as that's enabled by the open-source-firmware-flag. We might want to temporarly > disable the watchdog in the driver for the time being. I like the idea of encoding the capabilities in the firmware as it would be a self-documenting method as the firmware evolves. Is using the Broadcom names for the firmware the best course of action? What if the opensource firmware files were named something like "os-ucode5.fw", etc. and b43 were coded to check for those files first? It would then fall back to the standard firmware if the opensource version is not found. Larry -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
