From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Powerful Notageek <powerfulnotageek@yahoo.in>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
users@rt2x00.serialmonkey.com
Subject: Re: MT7630e availability in kernel by default
Date: Tue, 10 Jun 2014 08:38:24 +0200 [thread overview]
Message-ID: <20140610063824.GD1720@redhat.com> (raw)
In-Reply-To: <53936C6E.8070800@lwfinger.net>
On Sat, Jun 07, 2014 at 02:47:58PM -0500, Larry Finger wrote:
> On 06/07/2014 02:13 PM, Powerful Notageek wrote:
> >dmesg says nothing and there's probably no firmware for the device (although linux-firmware is installed)
> >
> >These are the firmwares available to me:
> >
> >[root@localhost ~]# ll /usr/lib/firmware/rt2*
> >-rw-r--r--. 1 root root 8192 Mar 18 00:08 /usr/lib/firmware/rt2561.bin
> >-rw-r--r--. 1 root root 8192 Mar 18 00:08 /usr/lib/firmware/rt2561s.bin
> >-rw-r--r--. 1 root root 8192 Mar 18 00:08 /usr/lib/firmware/rt2661.bin
> >-rw-r--r--. 1 root root 8192 Mar 18 00:08 /usr/lib/firmware/rt2860.bin
> >-rw-r--r--. 1 root root 8192 Mar 18 00:08 /usr/lib/firmware/rt2870.bin
>
> I looked more closely at the code in
> https://github.com/anthonywong/mt7630. There are a number of places
> where there are branches specific to the MT7630.
This driver is quite nice mix of rt2800pci and Mediatek/Ralink driver,
where MT7xx code was copied into rt2x00 from venodr driver. It can be
good start for adding support for mt7xx devices to rt2x00.
> It also needs a
> firmware file named mt7630.bin. Unfortunately, that file is not
> found in the repo, and a quick Google search failed to find it. The
> linux-firmware git repo has a file named mt7650.bin, but I think
> that is Bluetooth firmware.
Indeed, it is hard to find it.
> Unfortunately, there does not seem to be an easy fix, and only
> someone with the hardware could modify rt2800pci to support this
> device.
Yep, some substantial amount of work is needed to add support to new
MT7xxx chips properly to rt2x00.
Stanislaw
prev parent reply other threads:[~2014-06-10 6:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 16:38 MT7630e availability in kernel by default Powerful Notageek
2014-06-07 17:51 ` Larry Finger
2014-06-07 17:59 ` Powerful Notageek
2014-06-07 18:16 ` Larry Finger
2014-06-07 18:25 ` Powerful Notageek
2014-06-07 18:54 ` Larry Finger
2014-06-07 19:13 ` Powerful Notageek
2014-06-07 19:47 ` Larry Finger
2014-06-08 2:05 ` Powerful Notageek
2014-06-08 3:37 ` Larry Finger
2014-06-08 3:46 ` Powerful Notageek
2014-06-08 5:26 ` Powerful Notageek
2014-06-10 6:38 ` 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=20140610063824.GD1720@redhat.com \
--to=sgruszka@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=powerfulnotageek@yahoo.in \
--cc=users@rt2x00.serialmonkey.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.