From: Luca Olivetti <luca@ventoso.org>
To: linux-wireless@vger.kernel.org
Subject: Mediatek MT7601U big endian fixes
Date: Wed, 24 Sep 2014 19:19:07 +0200 [thread overview]
Message-ID: <5422FD0B.3060806@ventoso.org> (raw)
Hello,
apart from the general brokenness of the vendor supplied driver (see
http://www.spinics.net/lists/linux-wireless/msg126291.html and
http://www.arnelborja.com/compiling-rt2870-wifi-driver-in-fedora/), it
doesn't work in big endian mode.
Without this patch:
https://code.google.com/p/mt7601-openwrt/source/browse/patches/007-big-endian-fix.patch
it doesn't even compile, and this one
https://code.google.com/p/mt7601-openwrt/source/browse/patches/008-more-big-endiand-fixes.patch
makes it functional.
Before finding the fix myself I contacted mediatek support with no reply
so far.
Do you know if is there somebody (at ralink/mediatek or elsewhere)
working on integrating this chipset in the in-kernel driver?
Bye
--
Luca
next reply other threads:[~2014-09-24 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 17:19 Luca Olivetti [this message]
2014-09-24 17:51 ` Mediatek MT7601U big endian fixes John W. Linville
2014-09-24 18:49 ` Luca Olivetti
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=5422FD0B.3060806@ventoso.org \
--to=luca@ventoso.org \
--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).