From: Hans Fugal <hans@fugal.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
netdev@vger.kernel.org, softmac-dev@sipsolutions.net,
David Woodhouse <dwmw2@redhat.com>,
Dan Williams <dcbw@redhat.com>,
bcm43xx-dev@lists.berlios.de
Subject: Re: [RFC PATCH] softmac: (v2) send WEXT assoc/disassoc events to userspace
Date: Thu, 13 Apr 2006 19:05:45 -0600 [thread overview]
Message-ID: <20060414010545.GA10636@falcon.fugal.net> (raw)
In-Reply-To: <1144888334.4187.32.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 527 bytes --]
With the patch, wpa_supplicant is able to work properly for WEP and
plaintext as tested with my bcm4306 (iBook), and the latest git.
However, and this may not be related, I still must issue an
ip link set up eth1
after loading the bcm43xx module but before starting wpa_supplicant or
it will not work.
--
Hans Fugal ; http://hans.fugal.net
There's nothing remarkable about it. All one has to do is hit the
right keys at the right time and the instrument plays itself.
-- Johann Sebastian Bach
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-04-14 1:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1141928917.26954.7.camel@localhost.localdomain>
[not found] ` <1141935893.28038.2.camel@localhost.localdomain>
[not found] ` <1141935893.28038.2.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2006-03-09 20:36 ` [RFC PATCH] softmac: (v2) send WEXT assoc/disassoc events to userspace Larry Finger
[not found] ` <1141936896.28038.6.camel@localhost.localdomain>
2006-04-12 23:56 ` Johannes Berg
[not found] ` <20060413001909.GB23116@falcon.fugal.net>
[not found] ` <1144887916.4187.28.camel@localhost>
[not found] ` <20060413002816.GC23116@falcon.fugal.net>
[not found] ` <1144888334.4187.32.camel@localhost>
2006-04-14 1:05 ` Hans Fugal [this message]
2006-04-15 19:25 ` Johannes Berg
2006-04-16 11:24 ` softmac: semantics of SIOCSIWFREQ Ulrich Kunitz
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=20060414010545.GA10636@falcon.fugal.net \
--to=hans@fugal.net \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=dcbw@redhat.com \
--cc=dwmw2@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=netdev@vger.kernel.org \
--cc=softmac-dev@sipsolutions.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).