From: Andreas Hartmann <andihartmann@01019freenet.de>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Felix Fietkau <nbd@openwrt.org>
Subject: Re: Compat-wireless-3.2-rc6-3 is broken for rt2860 device
Date: Tue, 10 Jan 2012 14:01:52 +0100 [thread overview]
Message-ID: <201201101301.q0AD1qSK004871@mail.maya.org> (raw)
In-Reply-To: <CAGXE3d9usjQB+9jkBPgtvL6fT8L84ZzDQQ3UqHyMdb+PRfhrKA@mail.gmail.com>
Helmut Schaa schrieb:
[...]
> So this looks good to me although the broken tx status for BAR frames
> is for sure a rt2800pci problem (or even a hw issue).
Sorry - What do you mean with "hw issue"? Is my hw broken? Or is
it a specific "behavior" of exactly this device:
05:07.0 Network controller: RaLink RT2800 802.11n PCI
Subsystem: Linksys Device 0067
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32 (500ns min, 1000ns max), Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 21
Region 0: Memory at fdae0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: rt2800pci
Kind regards,
Andreas
next prev parent reply other threads:[~2012-01-10 13:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-31 13:49 Compat-wireless-3.2-rc6-3 is broken for rt2860 device Andreas Hartmann
2011-12-31 20:35 ` Andreas Hartmann
2012-01-03 21:51 ` Helmut Schaa
2012-01-04 8:38 ` Andreas Hartmann
2012-01-04 15:04 ` Helmut Schaa
2012-01-05 8:44 ` Andreas Hartmann
2012-01-09 10:23 ` Helmut Schaa
2012-01-09 13:29 ` Andreas Hartmann
2012-01-09 13:45 ` Helmut Schaa
2012-01-10 8:03 ` Andreas Hartmann
2012-01-10 9:50 ` Helmut Schaa
2012-01-10 11:56 ` Andreas Hartmann
2012-01-10 12:23 ` Helmut Schaa
2012-01-10 13:01 ` Andreas Hartmann [this message]
2012-01-10 13:43 ` Helmut Schaa
2012-01-10 14:41 ` Andreas Hartmann
2012-01-17 9:09 ` Andreas Hartmann
2012-01-20 7:29 ` Andreas Hartmann
2012-01-23 13:29 ` Helmut Schaa
2012-01-23 16:03 ` Andreas Hartmann
2012-01-23 16:36 ` Helmut Schaa
2012-01-23 17:44 ` Andreas Hartmann
2012-01-24 8:07 ` Helmut Schaa
2012-01-24 14:39 ` Stanislaw Gruszka
2012-01-24 15:19 ` Helmut Schaa
2012-01-24 7:29 ` Stanislaw Gruszka
2012-01-24 8:01 ` Andreas Hartmann
2012-01-24 8:06 ` Helmut Schaa
2012-01-04 12:29 ` Andreas Hartmann
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=201201101301.q0AD1qSK004871@mail.maya.org \
--to=andihartmann@01019freenet.de \
--cc=helmut.schaa@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.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 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).