I guess right now when you transmit on the master device frames are only accepted with a cookie and all that info in the CB. It would work just as well to move that info from the CB and into a protocol header. It would also make it easier to expand the info without the size constraint of the CB. Same could apply on receive.
Simon -----Original Message----- From: Johannes Berg [mailto:[EMAIL PROTECTED] Sent: Friday, November 03, 2006 3:07 PM To: Simon Barber Cc: Stephen Hemminger; Christoph Hellwig; James Ketrenos; John W. Linville; Jeff Garzik; Patrick McHardy; David Kimdon; netdev@vger.kernel.org Subject: RE: [patch] d80211: use pfifo_qdisc_ops ratherthand80211-specificqdisc On Fri, 2006-11-03 at 11:23 -0800, Simon Barber wrote: > I would > think the master device is the perfect place to do packet capture, Sort of. Since it'll be an 802.11 protocol thing, you won't be getting any signal strength information etc. You really do need that. > and > raw packet transmission. Same here, you really do want to be able to submit a frame with the bitrate to use etc. All not part of 802.11. All the meta info you want from RX or need for proper TX cannot be transported over that master netdev since it'll have a proper 802.11 protocol, so it's pretty much useless. johannes - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
