From: "Jouni Malinen" <jkm@devicescape.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: jt@hpl.hp.com, Michael Buesch <mb@bu3sch.de>,
linux-wireless@vger.kernel.org, netdev <netdev@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>, Dan Williams <dcbw@redhat.com>
Subject: Re: wireless extensions vs. 64-bit architectures
Date: Thu, 8 Mar 2007 11:34:12 -0800 [thread overview]
Message-ID: <20070308193412.GG23040@devicescape.com> (raw)
In-Reply-To: <1173382042.3248.63.camel@johannes.berg>
On Thu, Mar 08, 2007 at 08:27:22PM +0100, Johannes Berg wrote:
> On Thu, 2007-03-08 at 10:49 -0800, Jean Tourrilhes wrote:
> > A proper fix would involve forcing the alignement in the
> > kernel. Unfortunately, that would break 64bit->64bit configs. I think
> > I can build a workaround for this in iwlib.
>
> Actually, other tools like network manager, wpa supplicant and possibly
> more don't use iwlib afaik and are affected too, so the only real fix
> seems to be possible in the kernel.
Yes, workaround in just iwlib is not enough. If the only possible
solution is user space workaround, it better be documented (and
communicated to maintainers of user space apps) well so that
all user space programs not using iwlib can be modified, too.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2007-03-08 19:34 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 1:27 wireless extensions vs. 64-bit architectures Johannes Berg
2007-03-06 14:31 ` Johannes Berg
2007-03-06 17:13 ` Jean Tourrilhes
2007-03-06 18:43 ` Michael Buesch
2007-03-06 18:43 ` Michael Buesch
2007-03-07 1:42 ` Jean Tourrilhes
2007-03-07 1:42 ` Jean Tourrilhes
2007-03-07 2:03 ` Jean Tourrilhes
2007-03-08 14:39 ` Johannes Berg
2007-03-08 14:39 ` Johannes Berg
2007-03-08 16:51 ` Johannes Berg
2007-03-08 16:51 ` Johannes Berg
2007-03-08 17:37 ` Johannes Berg
2007-03-08 17:37 ` Johannes Berg
2007-03-08 18:49 ` Jean Tourrilhes
2007-03-08 19:08 ` Johannes Berg
2007-03-08 19:13 ` Jean Tourrilhes
2007-03-08 19:13 ` Jean Tourrilhes
2007-03-08 19:23 ` Johannes Berg
2007-03-08 19:27 ` Johannes Berg
2007-03-08 19:27 ` Johannes Berg
2007-03-08 19:34 ` Jouni Malinen [this message]
2007-03-08 19:40 ` Johannes Berg
2007-03-08 19:40 ` Johannes Berg
2007-03-08 22:11 ` Jean Tourrilhes
2007-03-08 22:11 ` Jean Tourrilhes
2007-03-08 22:17 ` Randy Dunlap
2007-03-08 22:17 ` Randy Dunlap
2007-03-08 22:30 ` Jean Tourrilhes
2007-03-08 22:30 ` Jean Tourrilhes
2007-03-08 22:36 ` Johannes Berg
2007-03-08 22:36 ` Johannes Berg
2007-03-08 22:34 ` David Miller
2007-03-08 22:34 ` David Miller
2007-03-08 22:49 ` Pavel Roskin
2007-03-08 22:22 ` Johannes Berg
2007-03-08 22:22 ` Johannes Berg
2007-03-08 22:36 ` Jean Tourrilhes
2007-03-08 22:36 ` Jean Tourrilhes
2007-03-08 22:35 ` Johannes Berg
2007-03-08 22:35 ` Johannes Berg
2007-03-09 21:35 ` Jean Tourrilhes
2007-03-09 23:19 ` Jouni Malinen
2007-03-09 23:19 ` Jouni Malinen
2007-03-10 1:01 ` Jean Tourrilhes
2007-03-10 1:01 ` Jean Tourrilhes
2007-03-11 17:40 ` Johannes Berg
2007-03-11 17:40 ` Johannes Berg
2007-03-11 20:11 ` Ulrich Kunitz
2007-03-11 20:11 ` Ulrich Kunitz
2007-03-11 20:30 ` Michael Buesch
2007-03-11 20:30 ` Michael Buesch
2007-03-12 17:56 ` Jean Tourrilhes
2007-03-12 17:56 ` Jean Tourrilhes
2007-03-12 18:21 ` Jouni Malinen
2007-03-12 20:34 ` Jean Tourrilhes
2007-03-12 20:34 ` Jean Tourrilhes
2007-03-13 19:42 ` Johannes Berg
2007-03-13 19:42 ` Johannes Berg
2007-03-13 21:30 ` Jean Tourrilhes
2007-03-13 21:30 ` Jean Tourrilhes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070308193412.GG23040@devicescape.com \
--to=jkm@devicescape.com \
--cc=dcbw@redhat.com \
--cc=jgarzik@pobox.com \
--cc=johannes@sipsolutions.net \
--cc=jt@hpl.hp.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.