linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Basse <michael@alpha-unix.de>
To: linux-wireless@vger.kernel.org
Cc: "John W. Linville"
	<public-linville-2XuSBdqkA4R54TAoqtyWWQ@lo.gmane.org>,
	public-linux-wireless-u79uwXL29TY76Z2rM5mHXA@lo.gmane.org,
	Ivo van Doorn
	<public-IvDoorn-Re5JQEeQqe8AvxtiuMwx3w@lo.gmane.org>,
	Gertjan van Wingerde
	<public-gwingerde-Re5JQEeQqe8AvxtiuMwx3w@lo.gmane.org>,
	Helmut Schaa
	<public-helmut.schaa-gM/Ye1E23mwN+BqQ9rBEUg@lo.gmane.org>,
	Amir Hedayaty
	<public-hedayaty-Re5JQEeQqe8AvxtiuMwx3w@lo.gmane.org>
Subject: Re: [PATCH] rt2800pci: handle spurious interrupts
Date: Tue, 22 Nov 2011 21:33:34 +0100	[thread overview]
Message-ID: <4ECC071E.5050403@alpha-unix.de> (raw)
In-Reply-To: <20111116100915.GA2191@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Stanislaw,
first of all thank you for your patch.

> I changed rt2800pci only because get bug report for that device,
> not sure if similar changes are not needed for other rt2x00 PCI
> devices

Me (and many other) ubuntu-users are facing issues with different
Version of Kernel 3.x. As it seems all users are using "rt2800pci" for
there wifi.

Model: "RaLink RT2860"
Vendor: pci 0x1814 "RaLink"
Device: pci 0x0781 "RT2860"
SubVendor: pci 0x1814 "RaLink"
SubDevice: pci 0x2790
Driver: "rt2800pci"
Driver Modules: "rt2800pci"

See also

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/869502
http://thread.gmane.org/gmane.linux.kernel/1211290
http://rt2x00.serialmonkey.com/phpBB/viewtopic.php?f=5&t=6192

I have build the newest ubuntu-kernel with your patch

http://alpha-unix.de/~iceroot/ubuntu/

Hopefully your patch is fixing the issues we are facing.
Just wanted to say thank you to your work and i will give you feedback
about your patch.

Greetings from germany

Michael Basse
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOzAcdAAoJEMIajL8dFT4GAXwIAJJJoUghmTUbw/354z09CDuB
eCpIaJw0is+zyp3RLssUJmmabyFtLkC0nFJ4iAGJfL/ozf7ISjtk1nLlQFbt6/iy
knV1uSGv6o9UuFCzJZ7boJ9cdNq35pAVul86PFqQ+fgDQYdlqfdLyNc71JRazvIE
b01jUudgjZDe09rKmrxiBvcr7FVKPhsSvrH5t6mSYpHJufDDm+TmQk+TJBT+KS8/
aDMPKXlCaAXNlXlm8tgLds8Flx5nnxGvvSXA1DDw37Z7kHOWKLOeHz8ILuctneVz
e8Fp5kgl02VVUVFK/K6+M4EbF/jmTo7FIW5Nlv60H9qsfx+peTkhKqx8o48FGAQ=
=D2BU
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2011-11-22 20:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16 10:09 [PATCH] rt2800pci: handle spurious interrupts Stanislaw Gruszka
2011-11-16 10:14 ` Ivo Van Doorn
2011-11-16 11:17   ` Stanislaw Gruszka
2011-11-16 11:45     ` Ivo Van Doorn
2011-11-16 10:46 ` Helmut Schaa
2011-11-16 10:52   ` Ivo Van Doorn
2011-11-16 11:01     ` Helmut Schaa
2011-11-22 20:33 ` Michael Basse [this message]
2011-11-22 22:10   ` Helmut Schaa
2011-11-23  6:25     ` Michael Basse
     [not found]   ` <20111123073500.GA9833@redhat.com>
2011-11-23 15:50     ` Michael Basse
2011-11-22 21:49 ` John W. Linville
2011-11-23  8:05   ` Stanislaw Gruszka
2011-11-23  8:50     ` Ivo Van Doorn
2011-11-23  8:51     ` Helmut Schaa
2011-11-23 10:51       ` Stanislaw Gruszka
     [not found]         ` <CAHJ2optb4E2r6W2w21oswptZh=_Q9kB+RbQ=F0TWg9zHGjXwZA@mail.gmail.com>
2011-11-23 14:40           ` Stanislaw Gruszka
2011-11-23 14:45             ` Luis Correia
     [not found]         ` <CAN6fvj2=EhimZUy-DKtpzAKq1mpvBt03KtX9vCi0dBTCXWVsRg@mail.gmail.com>
2011-11-23 15:14           ` Stanislaw Gruszka
2011-11-23 15:44             ` Stanislaw Gruszka
2011-11-23 17:00             ` Stanislaw Gruszka
2011-11-23 20:47         ` David Miller

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=4ECC071E.5050403@alpha-unix.de \
    --to=michael@alpha-unix.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=public-IvDoorn-Re5JQEeQqe8AvxtiuMwx3w@lo.gmane.org \
    --cc=public-gwingerde-Re5JQEeQqe8AvxtiuMwx3w@lo.gmane.org \
    --cc=public-hedayaty-Re5JQEeQqe8AvxtiuMwx3w@lo.gmane.org \
    --cc=public-helmut.schaa-gM/Ye1E23mwN+BqQ9rBEUg@lo.gmane.org \
    --cc=public-linux-wireless-u79uwXL29TY76Z2rM5mHXA@lo.gmane.org \
    --cc=public-linville-2XuSBdqkA4R54TAoqtyWWQ@lo.gmane.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).