linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Sean Wang <sean.wang@mediatek.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>,
	Jakub Kicinski <kubakici@wp.pl>,
	Hans Ulli Kroll <ulli.kroll@googlemail.com>,
	Michal Schmidt <mschmidt@redhat.com>,
	linux-wireless@vger.kernel.org,
	linux-mediatek@lists.infradead.org, Felix Fietkau <nbd@nbd.name>
Subject: Re: [PATCH v2 00/12] Add mt76x0 driver
Date: Mon, 23 Jul 2018 11:35:10 +0200	[thread overview]
Message-ID: <20180723093510.GB26486@redhat.com> (raw)
In-Reply-To: <1532100994.8953.305.camel@mtkswgap22>

Hello,

On Fri, Jul 20, 2018 at 11:36:34PM +0800, Sean Wang wrote:
> > > Sure, there is no any problem for submitting mt7662u.bin and
> > > mt7662u_rom_patch.bin if they are added with LICENCE.mediatek.
> > > 
> > > Do you or Lorenzo have a plan to add MT7668u support to mt76?
> > > MT7668 is a newer wifi device than MT7610u or MT7662u.
> > > 
> > 
> > Cool, I am interested in adding MT7668u support to mt76 driver.
> > Is the adapter available on the market?
> 
> I'm not sure if it can be got from the market easily.
> 
> I would like to say, mt7668 is based on new MTK wifi architecture. as
> for mt7662/mt7612/mt7610, they all belong to legacy Ralink based design.
> of course, we will never see any new chip based on Ralink based design
> wifi in the future.
> 
> There must be really lots of differences exist between two types of
> devices, such as MCU firmware download, MCU control interface, tx/rx
> path, even hardware register layout all changed and so on.
> 
> I guess the hardware abstraction layer needs to be largely adjusted to
> add the new device mt7668u into mt76 driver. And even I think it would
> be easier for development and maintenance if we make a separate driver
> and then pick up some pure software components from mt76 to reuse.

It could be the case that it's better to develop separate mac80211 driver
for this new chip than to integrate it into mt76. FWIW few years back
there was failed efforts to add MT7630 devices into venerable rt2x00
driver and Felix Fietkau decision to develop new mt76 driver proved that
this is better approach (though MT7620 is still supported via rt2x00
driver, but IMHO would be much better to have it as part of mt76).

As usual the devil is in the detail. We have not yet unstreamed Felix'
mt7603 driver which is part of mt76 in github tree;
https://github.com/openwrt/mt76 
I was not aware of that before, but according to description it also
supports MT7688 ? ( PCIe version ?). However, for what I can tell,
overlap between mt76x2 and mt7603 is very small and make mt7603 a
separate driver it drivers/net/wireless/mediatek/ could be a better
decision.
 
> Maybe it's the time I want to test your tree first with 7612u (?) or
> mt7610u (?) , what is suggested? and see how big the gap between this
> two type of devices and last write some code based on your tree to test
> mt7668u

Both 7610u and 7612u should be supported in my development
mt76x0-draft-v2 branch, which add mt76x0 on top of Lorenzo mt76x2u:
https://github.com/sgruszka/wireless-drivers-next/commits/mt76x0-draft-v2
so you can test that if you want to :-)

Thanks
Stanislaw

      parent reply	other threads:[~2018-07-23 10:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06 11:03 [PATCH v2 00/12] Add mt76x0 driver Stanislaw Gruszka
2018-07-06 11:03 ` [PATCH v2 01/12] mt76: add more states Stanislaw Gruszka
2018-07-06 11:03 ` [PATCH v2 02/12] mt76x0: core files Stanislaw Gruszka
2018-07-06 11:03 ` [PATCH v2 03/12] mt76x0: mac files Stanislaw Gruszka
2018-07-06 11:03 ` [PATCH v2 04/12] mt76x0: usb files Stanislaw Gruszka
2018-07-06 11:03 ` [PATCH v2 05/12] mt76x0: mcu files Stanislaw Gruszka
2018-07-06 11:03 ` [PATCH v2 06/12] mt76x0: phy files Stanislaw Gruszka
2018-07-06 11:03 ` [PATCH v2 07/12] mt76x0: init files Stanislaw Gruszka
2018-07-06 11:03 ` [PATCH v2 08/12] mt76x0: eeprom files Stanislaw Gruszka
2018-07-06 11:03 ` [PATCH v2 09/12] mt76x0: trace and debugfs files Stanislaw Gruszka
2018-07-06 11:03 ` [PATCH v2 10/12] mt76x0: dma and tx files Stanislaw Gruszka
2018-07-06 11:03 ` [PATCH v2 11/12] mt76x0: main file Stanislaw Gruszka
2018-07-06 11:03 ` [PATCH v2 12/12] mt76: Kconfig and Makefile for mt76x0 driver Stanislaw Gruszka
2018-07-06 14:48   ` kbuild test robot
2018-07-06 14:48   ` [RFC PATCH] mt76: mt76x0_burst_read_regs() can be static kbuild test robot
     [not found] ` <1531205430.26214.8.camel@mtkswgap22>
     [not found]   ` <20180710095222.GA18926@redhat.com>
     [not found]     ` <1531230864.26214.20.camel@mtkswgap22>
2018-07-11  8:07       ` [PATCH v2 00/12] Add mt76x0 driver Lorenzo Bianconi
2018-07-12 11:41         ` Stanislaw Gruszka
2018-07-20 15:36         ` Sean Wang
2018-07-23  9:16           ` Lorenzo Bianconi
2018-07-23  9:44             ` Stanislaw Gruszka
2018-07-23  9:35           ` 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=20180723093510.GB26486@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=kubakici@wp.pl \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=mschmidt@redhat.com \
    --cc=nbd@nbd.name \
    --cc=sean.wang@mediatek.com \
    --cc=ulli.kroll@googlemail.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 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).