From: Stanislaw Gruszka <sgruszka@redhat.com>
To: blue-t@web.de
Cc: linux-wireless@vger.kernel.org
Subject: Re: What is the state of mt7610un mainline support?
Date: Tue, 10 Jun 2014 08:41:16 +0200 [thread overview]
Message-ID: <20140610064115.GE1720@redhat.com> (raw)
In-Reply-To: <7708158.pL1FsGGcj0@nebulos>
On Sun, Jun 08, 2014 at 09:22:10AM +0200, blue-t@web.de wrote:
> i recently bought an AVM!Wlan Stick AC 430 (ID 057c:8501 AVM GmbH) which
> currently doesn't work at all with 3.15 kernel.
> A magnifying glass revealed that this device is using an mt7610un chipset.
> I tried to add the device id to the mt7610u driver from
> http://www.mediatek.com/en/downloads/?sort=os but that didn't work out.
[snip]
> Firmware loading wasn't required for the earlier devices from that
> manufacturer if i understand the discussion in
> http://www.spinics.net/lists/linux-wireless/msg123246.html correctly.
> Do we need a similiar fix here?
Adding support for new MT76xx chips to rt2x00 will require quite lot of
work not a single fix.
Stanislaw
prev parent reply other threads:[~2014-06-10 6:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 7:22 What is the state of mt7610un mainline support? blue-t
2014-06-10 6:41 ` Stanislaw Gruszka [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=20140610064115.GE1720@redhat.com \
--to=sgruszka@redhat.com \
--cc=blue-t@web.de \
--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 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).