Re: [RFC] cfg80211: Android P2P-Device workaround

["Arend van Spriel" <arend@broadcom.com>]

On 04/24/2013 04:29 PM, Marcel Holtmann wrote:
> Hi Arend,
>
>>>>> +config CFG80211_ANDROID_P2P_HACK
>>>>> +	bool "Android P2P netdevice hack"
>>>>> +	depends on CFG80211
>>>>> +	depends on !CFG80211_WEXT
>>>>> +	help
>>>>> +	  Enable this option for Android P2P w/ P2P Device.
>>>>> +
>>>>
>>>> do you really think this is a good idea? Wouldn't it be better if
>>>> Android just gets its userspace fixed. This way, they never will and
>>>> you carry this workaround forever.
>>>
>>> Well, I'm about 50/50 on whether to merge this. On the one hand, it's a
>>> very simple patch to carry out of tree, on the other hand more than one
>>> person will need it.
>>>
>>
>> Here is one who needs it. I consider this patch as a temporary solution, but it would be good to have it upstream. We would be using compat-drivers to backport the upstream brcmfmac to the android kernel, which also takes care of cfg80211.
>
> why do I get the feeling that the root-cause for this stupid p2p0 device is the Broadcom binary only driver  ;)

Hi Marcel,

Just like you I can only guess, but you are probably right except that 
the broadcom driver introducing this p2p0 device was propbably the 
bcmdhd driver which is available in android repositories.

Because of the design of the firmware (which is binary) going for a 
net_device was the most straightforward and also because wpa_supplicant 
is all about net_device interfaces.

> I feel like being back in the world of Wireless Extensions ;)

I hear you and we are still not fully rid of that.

Gr. AvS