On Thu, Sep 25, 2008 at 10:39 PM, Luis R. Rodriguez <mcgrof@xxxxxxxxx> wrote: > On Thu, Sep 25, 2008 at 10:28 PM, Zhu Yi <yi.zhu@xxxxxxxxx> wrote: > >> You brought it up. And I also want to discuss it. We do want to support >> it. But the 3945/4965/5000 hardwares doesn't have the alpha2 information >> in their EEPROMs (btw, 2100/2200 does support that). Instead, they have >> a band/channel table including freq, tx power, etc in the EEPROM. So a >> simple regulatory_hint() API doesn't work. We need a way to export the >> channel details to CRDA. > > Yes, this detail of information was conveyed to me at OLS by Guy. This > is why we decided to add support for letting the driver not pass an > alpha2 but to just build the regulatory domain structure itself and > pass it. I even provided an example of how to do this in the > Documentation/networking/regulatory.txt and tested it myself. > > Essentially this was added with your drivers in mind :) > > Let me know if you run into any issues. Oh and to be clear -- you "can" also pass an alpha2 if you guys do figure out a way to do that. If not its OK, just set the alpha2 to NULL. 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
