From: Pavel Roskin <proski@gnu.org>
To: Kalle Valo <Kalle.Valo@iki.fi>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 00/12] at76_usb mac80211 port
Date: Sun, 09 Mar 2008 21:00:43 -0400 [thread overview]
Message-ID: <1205110843.2142.37.camel@dv> (raw)
In-Reply-To: <87r6ejyhk2.fsf@litku.valot.fi>
On Sun, 2008-03-09 at 18:43 +0200, Kalle Valo wrote:
> >
> > I've put your patches on http://git.80211libre.org/at76_usb.git so that
> > they can be tested by more users. I gave no promise about continuity of
> > the branch, so I'm ready to replace the patches.
>
> Thanks, but it seems that John already applied the patches to
> wireless-testing. I would prefer working directly with
> wireless-testing, because it's easier for me.
That's easier for me too, as 80211libre.org domain is expiring soon.
> > I haven't looked at the code yet, but here are some testing results.
>
> What hardware and firmware did you use?
The firmware is the latest we support from at76_usb-firmware-0.1.tar.gz
But I don't remember which hardware I was using, as I have several
different devices. I can test again and provide more details.
> > I'm totally at loss why a positive value us printed. When trying to
> > set the key and ESSID again, I get this:
> >
> > wlan3: Initial auth_alg=0
> > wlan3: authenticate with AP 00:0b:6b:56:01:bf
> > wlan3: authenticate with AP 00:0b:6b:56:01:bf
> > wlan3: authenticate with AP 00:0b:6b:56:01:bf
> > wlan3: authentication with AP 00:0b:6b:56:01:bf timed out
> >
> > Pings don't come through. Everything is within one room.
> Attenuation
> > shouldn't be an issue.
>
> Do you mean that all your tries failed? That's bad.
Yes.
> > Another interesting problem - scan results show the channel two
> times
> > (not counting the "frequency" line). Other mac80211 drivers do it
> once.
> > No idea why.
>
> Strange. I'll take a look at it as well.
Thanks.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2008-03-10 1:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 14:59 [PATCH 00/12] at76_usb mac80211 port Kalle Valo
2008-02-10 14:59 ` [PATCH 01/12] Use net/mac80211.h instead of net/ieee80211.h Kalle Valo
2008-02-10 15:00 ` [PATCH 02/12] Add at76_dbg_dump() macro Kalle Valo
2008-02-10 15:00 ` [PATCH 03/12] Convert DBG_TX levels to use at76_dbg_dump() Kalle Valo
2008-02-10 15:00 ` [PATCH 04/12] Add DBG_CMD for debugging firmware commands Kalle Valo
2008-02-10 15:00 ` [PATCH 05/12] at76_usb: add mac80211 support Kalle Valo
2008-02-10 15:00 ` [PATCH 06/12] Add support for monitor mode Kalle Valo
2008-02-10 15:49 ` Michael Buesch
2008-02-10 15:52 ` Michael Buesch
2008-03-09 16:10 ` Kalle Valo
2008-03-09 17:39 ` Michael Buesch
2008-02-10 15:00 ` [PATCH 07/12] Add support for WEP Kalle Valo
2008-02-10 15:00 ` [PATCH 08/12] Remove support the legacy stack Kalle Valo
2008-02-10 15:00 ` [PATCH 09/12] Use wiphy_name everywhere where needed Kalle Valo
2008-02-10 15:01 ` [PATCH 10/12] Allocate struct at76_priv using ieee80211_alloc_hw() Kalle Valo
2008-02-10 15:01 ` [PATCH 11/12] Prepare for struct net_device removal Kalle Valo
2008-02-10 15:01 ` [PATCH 12/12] Remove struct net_device Kalle Valo
2008-02-11 5:05 ` [PATCH 00/12] at76_usb mac80211 port Pavel Roskin
2008-02-11 5:17 ` Pavel Roskin
2008-03-09 16:43 ` Kalle Valo
2008-03-10 1:00 ` Pavel Roskin [this message]
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=1205110843.2142.37.camel@dv \
--to=proski@gnu.org \
--cc=Kalle.Valo@iki.fi \
--cc=linux-wireless@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.