linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Hartmann <andihartmann@01019freenet.de>
To: Mohit <mt1037ag11@pdm.ac.in>,
	Gertjan van Wingerde <gwingerde@gmail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: Ralink RT3290 proprietary drivers causing kernel panic
Date: Thu, 23 May 2013 18:18:32 +0200	[thread overview]
Message-ID: <519E4158.2060600@01019freenet.de> (raw)
In-Reply-To: <519E09BE.6060802@pdm.ac.in>

Mohit wrote:
[...]
> The drivers work in kernel 3.2 but stop working from either kernel ver.
> 3.3, 3.4 or 3.5.

>From my experience, it seems more to be a compiler / binutils problem:

See
http://news.gmane.org/find-root.php?group=gmane.linux.drivers.rt2x00.user&article=1765

> The drivers included in the kernel work, but they are a buggy, have low
> range, connection drops etc.

Exactly my experience here, especially the USB ones (but seems to be
heavily hardware dependent). And they produce enormous cpu load as soon
as throughput rises.

That's why I'm only using the vendor driver (for STA), too (besides the
point that rt2800usb doesn't support a Linksys AE3000 at all e.g.
(http://wikidevi.com/wiki/Linksys_AE3000), which is a really fine device!)

> I switched from Linux mint 13 kernel 3.2, installed the proprietary
> driver and it is way better than rt2800pci drivers interms of signal
> strength, latency, speed etc. I think the proprietary drivers use
> rt2860pci driver instead of a dedicated rt3290sta driver.
> 
> Can the drivers included in the kernel be tweaked to match the
> proprietary driver?

It would be cool on the one hand, if Mediatek would integrate their own
drivers themselves to mac80211, but on the other hand, I fear, this is
mostly impossible because mac80211 (which was heavily built for and from
Atheros and Intel and therefore "optimized" for there own needs) doesn't
match the requirements of the Ralink hardware.

That's why I'm happy they don't integrate their drivers in the existing
mac80211 because I fear a likewise bad quality.


I think the maintainer of rt2800 do all they can given the opportunities
they have so far. Unfortunately, they have very little opportunities
from my point of view.



Kind regards,
Andreas

  reply	other threads:[~2013-05-23 16:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22 18:24 Ralink RT3290 proprietary drivers causing kernel panic Mohit
2013-05-22 19:55 ` Gertjan van Wingerde
2013-05-23 12:21   ` Mohit
2013-05-23 16:18     ` Andreas Hartmann [this message]
2013-05-22 20:22 ` Jakub Kiciński

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=519E4158.2060600@01019freenet.de \
    --to=andihartmann@01019freenet.de \
    --cc=gwingerde@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mt1037ag11@pdm.ac.in \
    /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).