> From someone who has no idea at all (yet) about 802.11: why character > device, and not sysfs or configfs files? Like As Michael already said -- there's no real reason for that. We were just brainstorming. The /dev idea seemed like a good plan at first, but then it isn't fixed. What you suggested below does look useful too. Coming back to the point Michael already raised: the overarching idea is to get rid of the net_dev for the 'master' device, even if the underlying hardware supports only a single virtual device (which might then be created by the driver automatically) I'll move the wiki pages a bit to accomodate different models, please check in a few minutes. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
- References:
- State of the Union: Wireless
- From: Jeff Garzik <[email protected]>
- Re: State of the Union: Wireless
- From: Johannes Berg <[email protected]>
- Re: State of the Union: Wireless
- From: Dominik Brodowski <[email protected]>
- State of the Union: Wireless
- Prev by Date: Re: [PATCH] Remove gfp argument from kstrdup()
- Next by Date: Re: 2.6.15 ax25 system lockup with kissattach
- Previous by thread: Re: State of the Union: Wireless
- Next by thread: Re: State of the Union: Wireless
- Index(es):
 |