From: Lennert Buytenhek <buytenh@wantstofly.org>
To: sedat.dilek@gmail.com
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, lautriv <admin@coldplug.net>,
Jim Cromie <jim.cromie@gmail.com>
Subject: Re: [PATCH] mwl8k: Add 0x2a02 PCI device-id (Marvell 88W8361)
Date: Tue, 1 May 2012 14:47:08 +0200 [thread overview]
Message-ID: <20120501124708.GM3157@wantstofly.org> (raw)
In-Reply-To: <CA+icZUWQmCRdjucb4+Nf24_zbJ4fzzp7zjqhKjXE6U01rppDfA@mail.gmail.com>
On Fri, Apr 27, 2012 at 11:53:28PM +0200, Sedat Dilek wrote:
> >> So, Lennert if you want more testing - What? How? etc.
> >
> > For one, the output of 'iw phy', please.
> >
> > Also, does monitor mode work? Do you get plausible channel/rxpower
> > values in tcpdump in monitor mode?
> >
> > Are there any messages in the syslog about failing commands?
>
> On 1st sight, logs look fine:
>
> [21:52:52] <lautriv> [ 6.050967] ieee80211 phy0: 88w8361p v4,
> 00173f3bdde3, STA firmware 2.1.4.25
>
> But WLAN connection is not that fast and stable as lautriv reports
> (several abnormalities were observed).
iwconfig saying "Bit Rate=1 Mb/s" can be safely ignored. If there is
a bitrate indication on transmitted packets in tcpdump, then that's
bogus too, as rate control is done in hardware. (I.e. if you want to
verify the rate at which a packet is transmitted, you'll have to sniff
from another machine.)
prev parent reply other threads:[~2012-05-01 12:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 9:08 Sedat Dilek
2012-04-27 9:14 ` Lennert Buytenhek
2012-04-27 9:22 ` Sedat Dilek
2012-04-27 9:40 ` Lennert Buytenhek
2012-04-27 9:42 ` Sedat Dilek
2012-04-27 9:46 ` Lennert Buytenhek
2012-04-27 9:56 ` Sedat Dilek
2012-04-27 9:58 ` Lennert Buytenhek
2012-04-27 10:12 ` Sedat Dilek
2012-04-27 10:17 ` Lennert Buytenhek
2012-04-27 10:57 ` Sedat Dilek
2012-04-27 13:29 ` Sedat Dilek
2012-04-27 18:58 ` Lennert Buytenhek
2012-04-27 21:53 ` Sedat Dilek
2012-04-28 22:25 ` Sedat Dilek
2012-05-01 12:51 ` Lennert Buytenhek
2012-05-01 13:54 ` Sedat Dilek
2012-05-01 15:49 ` Lennert Buytenhek
2012-05-02 1:12 ` Pat Erley
2012-05-02 2:38 ` Lennert Buytenhek
2012-05-02 8:58 ` Sedat Dilek
2012-05-02 7:59 ` Arend van Spriel
2012-05-02 13:53 ` Ben Hutchings
2012-05-07 16:09 ` Dan Williams
2012-05-07 16:42 ` Dan Williams
2012-05-07 18:26 ` Adrian Chadd
2012-05-11 8:01 ` Helmut Stengele
2012-05-01 12:47 ` Lennert Buytenhek [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=20120501124708.GM3157@wantstofly.org \
--to=buytenh@wantstofly.org \
--cc=admin@coldplug.net \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=sedat.dilek@gmail.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
all inboxes | Powered by JetHome®