linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
To: Sean Wang <sean.wang@mediatek.com>
Cc: Stanislaw Gruszka <sgruszka@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: Wed, 11 Jul 2018 10:07:25 +0200	[thread overview]
Message-ID: <20180711080721.GA3871@localhost.localdomain> (raw)
In-Reply-To: <1531230864.26214.20.camel@mtkswgap22>

> On Tue, 2018-07-10 at 11:52 +0200, Stanislaw Gruszka wrote:
> > On Tue, Jul 10, 2018 at 02:50:30PM +0800, Sean Wang wrote:
> > > > For full support mt7610.bin firmware blob is need, hopefully with 
> > > > the permission of Mediatek, the blob will be pushed into linux-firmware
> > > > git tree.
> > > > 
> > > 
> > > Hi, Stanislaw
> > > 
> > > You can feel free to add mt7610.bin firmware blob to linux-firmware with
> > > the license LICENCE.mediatek I added in [1].
> > > 
> > > 
> > > [1]
> > > http://lists.infradead.org/pipermail/linux-mediatek/2018-June/013759.html
> > 
> > Thank you Sean!
> > 
> > I guess there is no problem with similar submission for
> > mt7662u.bin and mt7662u_rom_patch.bin needed for mt76x2u:
> > https://marc.info/?l=linux-wireless&m=153045438821562&w=2
> > 
> 

Thanks Sean,

I will submit mt7662u.bin and mt7662u_rom_patch.bin with LICENCE.mediatek
soon

> 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?

Regards,
Lorenzo

> > Regards
> > Stanislaw
> > 
> > _______________________________________________
> > Linux-mediatek mailing list
> > Linux-mediatek@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-mediatek
> 
> 

  parent reply	other threads:[~2018-07-11  8:10 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       ` Lorenzo Bianconi [this message]
2018-07-12 11:41         ` [PATCH v2 00/12] Add mt76x0 driver 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

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=20180711080721.GA3871@localhost.localdomain \
    --to=lorenzo.bianconi@redhat.com \
    --cc=kubakici@wp.pl \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mschmidt@redhat.com \
    --cc=nbd@nbd.name \
    --cc=sean.wang@mediatek.com \
    --cc=sgruszka@redhat.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).