Date: Fri, 14 Jun 2013 10:20:27 +0200 From: Guillaume Bibaut <yom@iaelu.net> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-arm@freebsd.org, freebsd-wireless@freebsd.org Subject: Re: arm/179532: wireless networking on ARM Message-ID: <0F0FA54B-4970-41A7-9173-4EF28A61DFE5@iaelu.net> In-Reply-To: <CAJ-VmomctPwB=0MjV8DNO1UxxcJmzx%2BkyDy6p4=d%2BGPSAsu1yg@mail.gmail.com> References: <201306130940.r5D9eiFx089862@oldred.freebsd.org> <CAJ-VmomxoYJ%2B73ro9hg4Ee%2BqseCV-Gy2SmV1fsOBO1EC1Hu6LA@mail.gmail.com> <CAJ-VmomctPwB=0MjV8DNO1UxxcJmzx%2BkyDy6p4=d%2BGPSAsu1yg@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Here is the output : set_channel: c=0xc289b214, p=0xc2892fbb, rc=0xc2892fbb picture : http://iaelu.net/~yom/efikamx/arm-eabi/photo6.JPG -- Guillaume Le 14 juin 2013 07:32, Adrian Chadd <adrian@freebsd.org> a crit : > So that line does this: > > rc->freq = htole16(c->ic_freq); > > Please print out the value of p, c and rc before that is called. > > printf("%s: c=%p, p=%p, rc=%p\n", __func__, c, p, rc); > > I bet one of them is unaligned. > > And I bet that 'c' is aligned, but 'rc' and 'p' aren't aligned. > I bet they're unaligned because ic->ic_rxchan and/or ic->ic_txchan is unaligned. > > Now, why _those_ are unaligned, I dunno. I bet the pointers passed > into ieee80211_radiotap_attach() (th and rh) are unaligned, and that > leads to this unalignment mess. > > The whole tx and rx tap structure allocation in if_runvar.h is a bit sick. Sigh. > > > > Adrian > > > On 13 June 2013 16:49, Adrian Chadd <adrian@freebsd.org> wrote: >> Ugh, >> >> Hi, >> >> An alignment fault? ugh. It works fine on MIPS; I wonder if it's >> something odd to do with the specific driver in use. >> >> I'll look at the source and get back to everyone. >> >> Thanks! >> >> >> >> adrian > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" [-- Attachment #2 --] 0 *H 010 + 0 *H l0000 *H 010 UIL10U StartCom Ltd.1+0)U"Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0 130305151431Z 140306083242Z0Q10U jFNYizweJ963A6H310U yom@iaelu.net10 *H yom@iaelu.net0"0 *H 0 n." ڥ?pf)}O/<O&_6-\xy E3snAi>R<} 2Hs1F4틟XpUhTOiXG\mshk/ح}6`#Rk^w_ϱ˖,Ͽ4|dyP^ L?7?L9q^ ػ-1`kҚah[:'TZqp 00 U0 0U0U%0++0UX`pr[9r-]h0U#0Sr풜\|~5NԸQ0U0 yom@iaelu.net0LU C0?0;+70*0.+"http://www.startssl.com/policy.pdf0+00' StartCom Certification Authority0This certificate was issued according to the Class 1 Validation requirements of the StartCom CA policy, reliance only for the intended purpose in compliance of the relying party obligations.06U/0-0+)'%http://crl.startssl.com/crtu1-crl.crl0+009+0-http://ocsp.startssl.com/sub/class1/client/ca0B+06http://aia.startssl.com/certs/sub.class1.client.ca.crt0#U0http://www.startssl.com/0 *H 'wTFIyʽRSGI '_+]\l;䩓Yq/ÒF[X<v>&t7Dt|YOdWb!IeMaB3Xx[-]Fo3/>rv9(s9˲:%|FB>Ġs~q?VO-FJ:xqi; GV}3$cb88A?ǝtdK祖vLLxş1kã0400 *H 0}10 UIL10U StartCom Ltd.1+0)U"Secure Digital Certificate Signing1)0'U StartCom Certification Authority0 071024210155Z 171024210155Z010 UIL10U StartCom Ltd.1+0)U"Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0"0 *H 0 -).2AUGo#G B|NDRpM-B=o-we5JQpa>O.#._<V [~**pz~3WG .ᘟMlr[<Ce6fqO"uxfWN#uicgkv$Lb%y`_{`xK'GN 00U00U0USr풜\|~5NԸQ0U#0N@[i04hCA0f+Z0X0'+0http://ocsp.startssl.com/ca0-+0!http://www.startssl.com/sfsca.crt0[UT0R0'%#!http://www.startssl.com/sfsca.crl0'%#!http://crl.startssl.com/sfsca.crl0U y0w0u+70f0.+"http://www.startssl.com/policy.pdf04+(http://www.startssl.com/intermediate.pdf0 *H }x,\c^#wMq}>UK/^yX֏y frMIŲB61ymQҨݬZ0&
