Hi Kalle,
On Sun, Jul 17, 2011 at 11:16, Kahn, Gery <geryk@xxxxxx> wrote:
> On Fri, Jul 15, 2011 at 13:56, Kalle Valo <kvalo@xxxxxxxxxx> wrote:
>> Gery Kahn <geryk@xxxxxx> writes:
>>
>>> Export the chip id to userspace. This helps to change application behavior
>>> according to architecture of the wl12xx chip.
>>
>> We already support exporting this type of information through
>> ethtool's ioctl interface using the wiphy.hw_version, which was
>> specifially added for this purpose. That's much better than yet
>> another sysfs file.
>>
> Right.
> In PLT mode it didn't show any information, but
> that might have been a mistake on our part.
>
> I'll send another patch.
>
After some investigation, found that ethtool's ioctl interface doesn't work
at this case.
1.
It demands data for registers while the purpose of the change was to have
only HW version at sysfs.
BTW, if the registers data exists, the ethtool doesn't display
HW version anyway.
2.
The datapath of ioctl SIOCETHTOOL also has problem that can be solved
by changing the cfg80211_get_regs_len() from net/wireless/ethtool.c
static int cfg80211_get_regs_len(struct net_device *dev)
struct wireless_dev *wdev = dev->ieee80211_ptr;
return sizeof(wdev->wiphy->hw_version);
}
But i need to check more with other drivers may be.
I am back to suggest my patch for the case.
Gery
--
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
