From owner-freebsd-arm@FreeBSD.ORG Fri Jun 14 08:22:40 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5414B2F2; Fri, 14 Jun 2013 08:22:40 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x22f.google.com (mail-qa0-x22f.google.com [IPv6:2607:f8b0:400d:c00::22f]) by mx1.freebsd.org (Postfix) with ESMTP id 08F2E1B9B; Fri, 14 Jun 2013 08:22:39 +0000 (UTC) Received: by mail-qa0-f47.google.com with SMTP id i13so14234qae.20 for ; Fri, 14 Jun 2013 01:22:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=FcCBazioPBivawh9AvXxS/c3D9N/YprgrxLLm/yHc+8=; b=o7abDONspTkntj3/8RehkwuMYg615DRpgjEMQWEx2WHWSg8QIpQUN7PqGity9obapz 1EXG1xQjtk58ANUufqhHq2i6CVKsUux5xba3N8zqn+AMltmCPu9m3pWQlXELtphBp+6X op1rRA+XcjXHUuHyj/epmXi4RKZWY7O98vyEO2pIeuma/XXyqOYZb6W4Tda1YHPBfpYb B15Cf9cI3K1VpiugfJeNMssJ9MAnZzzpezzSH0yvLSrQihLb9ee7miWJEh16aeRIO+D9 cXuCdU0HlSU8eqpll/Dpvnfq9jv6HCDVhCuqe4bSbZel5DDFgWBp0Elq5y0yn5F25Zgx l6ww== MIME-Version: 1.0 X-Received: by 10.229.119.3 with SMTP id x3mr451215qcq.64.1371198159614; Fri, 14 Jun 2013 01:22:39 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.5.65 with HTTP; Fri, 14 Jun 2013 01:22:39 -0700 (PDT) In-Reply-To: <0F0FA54B-4970-41A7-9173-4EF28A61DFE5@iaelu.net> References: <201306130940.r5D9eiFx089862@oldred.freebsd.org> <0F0FA54B-4970-41A7-9173-4EF28A61DFE5@iaelu.net> Date: Fri, 14 Jun 2013 01:22:39 -0700 X-Google-Sender-Auth: 7_R_Rl3SamBMAwqM-BC0XNQXHow Message-ID: Subject: Re: arm/179532: wireless networking on ARM From: Adrian Chadd To: Guillaume Bibaut Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-arm@freebsd.org, freebsd-wireless@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jun 2013 08:22:40 -0000 Yup, it's being handed an unaligned radiotap header address from the run dr= iver. Grr. Adrian On 14 June 2013 01:20, Guillaume Bibaut wrote: > Here is the output : > > set_channel: c=3D0xc289b214, p=3D0xc2892fbb, rc=3D0xc2892fbb > > > picture : > > http://iaelu.net/~yom/efikamx/arm-eabi/photo6.JPG > > > -- > Guillaume > > > Le 14 juin 2013 =E0 07:32, Adrian Chadd a =E9crit : > > So that line does this: > > rc->freq =3D htole16(c->ic_freq); > > Please print out the value of p, c and rc before that is called. > > printf("%s: c=3D%p, p=3D%p, rc=3D%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 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" > >