On Fri, Sep 19, 2008 at 7:58 AM, Christian Lamparter <chunkeey@xxxxxx> wrote: > On Friday 19 September 2008 10:59:38 Johannes Berg wrote: >> On Thu, 2008-09-18 at 22:57 -0700, Luis R. Rodriguez wrote: >> > > After the driver has received some serious cleanup I would like to try >> > > to to get it into wireless-testing tree. But I'll send another email >> > > later on. >> > >> > Cool! I thought n810 basically used a p54 type chipset over SPI? >> >> Yes, but the firmware (lower MAC) is sufficiently different that it >> would be painful to support in p54, afaict. >> > not that much... only the frequency calibration data is a bit different, > while most other data structures are more or less the same. Really! Well to be fair we had similar question with ath5k and we went with ath9k because that's how we best could support the hardware as quickly as possible for users. Eventually we will converge though as it just makes sense in areas that we can share. So if this driver is targeted upstream to get users supported I can see how using a new driver supported by a team can make sense. But eventually convergence should be considered. Is this driver targeted for inclusion upstream? If the driver is targeted upstream and a company is sponsoring its development we would like a license for the firmware. I mentioned this on another thread but it must be one which meets distribution requirements. You can see the WHENCE file on linux-firmware git tree for examples. git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git Otherwise how can I use this driver, test it or enhance it? Luis -- 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
