From: Alejandro B. <abo...@li...> - 2005-07-28 15:10:05
|
> Hi, >=20 > This patch will add the ieee80211_hdr_3addr to the=20 > ieee80211_assoc_request_frame structure. >=20 > Patch is against ieee80211 1.0.3. >=20 > IvD >=20 >=20 > diff -U 3 -H -w -E -d -r -N -- ieee80211-1.0.3/net/ieee80211.h=20 > ieee80211-1.0.3-assoc/net/ieee80211.h > --- ieee80211-1.0.3/net/ieee80211.h 2005-07-15=20 > 01:53:35.000000000 +0200 > +++ ieee80211-1.0.3-assoc/net/ieee80211.h 2005-07-28=20 > 16:58:30.000000000=20 > +0200 > @@ -566,6 +566,7 @@ > } __attribute__ ((packed)); > =20 > struct ieee80211_assoc_request_frame { > + struct ieee80211_hdr_3addr header; > u16 capability; > u16 listen_interval; > u8 current_ap[ETH_ALEN]; >=20 Sorry, What is the difference with this patch and the one for ipw2100 to = compile against 1.0.3? http://ipw2100.sourceforge.net/patches/ipw2100-1.1.2-ieee80211-1.0.3.patc= h That patch gives: -#define IPW_HEADER_802_11_SIZE sizeof(struct ieee80211_header_data) +#define IPW_HEADER_802_11_SIZE sizeof(struct ieee80211_hdr_3addr) #define IPW_MAX_80211_PAYLOAD_SIZE 2304U #define IPW_MAX_802_11_PAYLOAD_LENGTH 2312 #define IPW_MAX_ACCEPTABLE_TX_FRAME_LENGTH 1536 So this is doing ieee80211_hdr_3addr for the ipw2100 to compile with = 1.0.3, but isn't ieee80211_hdr_3addr already there? I'm confused... |