From: Johannes Berg <johannes@sipsolutions.net>
To: Sedat Dilek <sedat.dilek@googlemail.com>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: Linux-2.6.32-rc1/2] wext refactor needs wpasupplicant 0.7.0+?
Date: Thu, 01 Oct 2009 21:47:01 +0200 [thread overview]
Message-ID: <1254426421.3959.29.camel@johannes.local> (raw)
In-Reply-To: <2d0a357f0910010247jfda1199h5a9b873233b186ca@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 937 bytes --]
On Thu, 2009-10-01 at 11:47 +0200, Sedat Dilek wrote:
> a few hours ago I compiled a new kernel from upstream and put
> wireless-testing master-2009-09-30 on top of it.
>
> Last commit a1bec0ecfc76281d5e1ebd33435c67da7dd0fe71
> wext: refactor
>
> linux-2.6/master:
> 84d88d5: Merge branch 'sched-fixes-for-linus' of
> git://git./linux/kernel/git/tip/linux-2.6-tip
>
> After installation of the above described kernel, I could not connect
> to my AP using wext driver and wpasupplicant (0.6.9-3) from Debian/sid
> [1].
> With ath5k I could not establish a network connection neither via DHCP
> nor via static-IP to my AP (iwl3945 on a second machine works with
> self-debianized wpasupplicant 0.7.0+ and static-IP, same kernel).
>
> Just for clarification:
> Does wext refactor need a wpasupplicant >= 0.7.0 from hostap GIT repository [2]?
Should be ok. Can we see wpa_supplicant -ddt log please?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-10-01 19:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 9:47 Linux-2.6.32-rc1/2] wext refactor needs wpasupplicant 0.7.0+? Sedat Dilek
2009-10-01 10:15 ` Sedat Dilek
2009-10-01 19:47 ` Johannes Berg [this message]
2009-10-01 20:44 ` Sedat Dilek
2009-10-01 20:56 ` Johannes Berg
2009-10-02 7:10 ` Holger Schurig
2009-10-02 11:48 ` Sedat Dilek
2009-10-01 21:55 ` Sedat Dilek
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=1254426421.3959.29.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=sedat.dilek@googlemail.com \
/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