Last update: Talked to some guys over at the wireless linux stack and they told me that drivers always void the 802.11 headers, these will be undefinable. I will have to work with device settings and general SKB to form functionality for 802.11 and let drivers do the rest.
Now I did notice that position of the 802.3 header in skbs is different depending on devices. Seeing as this goes to user space in the next step I can't help but wonder what happens before it is thrown to userspace in a (most likely) general format with pointers that are properly set. If anybody could help me find what happens to those things, I'd be very thankful. Kind regards, Mathieu Devos On Thursday, 1 August 2013 09:24:36 UTC+2, Mathieu Devos wrote: > > Little update: > > When testing on my own notebook I can clearly see that the skb->data > points to the 802.3 header (formed by the drivers), however the 802.11 > header is needed as well and currently can't be found yet. > > When copying this code over to android (I 9100 - Galaxy S2) this just > instantly crashes the kernel (because the pointer is all wrong, see above > post). > > So to recap: > 802.3 header, found on notebook, not found on android > 802.11 header, nowhere found yet > > As again: any information would be much appreciated. > > Kind regards, > Mathieu Devos > -- -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel --- You received this message because you are subscribed to the Google Groups "Android Linux Kernel Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
