On 03/30/2010 12:54 PM, Rafał Miłecki wrote: > --- > I've problem with deciding how to keep some data needed by band width setting > code. Generally these band width-related routines are considered "common", to > be used by more than just N-PHY. So probably the most /correct/ way should be > to add some variables like maccontrol, wake_override, clk and other to struct > b43_phy which is shared between all PHYs. However we would not use these vars > in anything except N-PHY, so we would just waste users memory. > > Could you help me decide correct way to handle this? I have not done the RE yet, but the SSLPN PHY is multi-band and will likely need all the band width parameters needed by the N PHY. I would vote for putting them in a "common" struct. 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
