Linux wireless drivers development
 help / color / mirror / Atom feed
From: Hans Ulli Kroll <ulli.kroll@googlemail.com>
To: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Stanislaw Gruszka <sgruszka@redhat.com>,
	linux-wireless@vger.kernel.org, Felix Fietkau <nbd@nbd.name>,
	Hans Ulli Kroll <ulli.kroll@googlemail.com>,
	Jakub Kicinski <kubakici@wp.pl>,
	Michal Schmidt <mschmidt@redhat.com>,
	linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 00/11] Add mt76x0 driver
Date: Sat, 7 Jul 2018 10:38:27 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1807071027140.11361@T420s> (raw)
In-Reply-To: <20180705153216.GE17524@localhost.localdomain>

Hi 

On Thu, 5 Jul 2018, Lorenzo Bianconi wrote:

> On Jul 05, Stanislaw Gruszka wrote:
> > Add mt76x0 driver for MT7610U based USB dongles. Currently driver
> > support only STA mode.
> 
> Hi Stanislaw,
> 
> > 
> > mt76x0 is based on Jakub's mt7601u driver already included
> > in the kernel. I would like the driver be integrated as part
> > of mt76 (instead of separate driver in mediatek dir like mt7601u)
> > to utilize mt76 code for adding support for MT76x0 PCIe devices
> > in further development.
> > 
> > To do not collide with current mt76x2u work from Lorenzo, I did not
> > remove some code duplication. This will be done in the future, when
> > Lorenzo patches will be merged. I plan to do more close integration
> > with mt76x2u into common mt76 layer and add support for MT76x0 PCIe
> > devices (i.e. MT7630E). Any help with this work is obviously welcome.
> > My integration efforts can be traced here:
> > https://github.com/sgruszka/wireless-drivers-next/commits/mt76x0-draft
> > 
> 
> I just had a brief review of the code and I compiled the driver since at
> the moment I had no adapter for that chipset.
> As a remainder for future improvements/integration most of the code in 
> dma.c, usb.c (except probe/disconnect functions) and tx.c can use the related
> routines in the mt76-usb layer (we need to fill function pointer for chipset
> related stuff if there are differences with mt76x2u, not looked yet).
> Moreover mcu code can use utility routines in usb-mcu.c
> I have not looked at mt76x2 common code yet.
> 
> Regards,
> Lorenzo
> 

It is also possible to reuse 
struct mt76x2_txwi
struct mt76x2_rxwi

They have the same memory layout for both mt76x0u and mt76x2u chipsets.

Lorenzo can you move them up to
mt76.h
and rename them to
struct mt76_txwi
struct mt76_rxwi

And we can also do this for
struct mt76x2_vif

Greetings
Hans Ulli

  parent reply	other threads:[~2018-07-07  8:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-05  6:12 [PATCH 00/11] Add mt76x0 driver Stanislaw Gruszka
2018-07-05  6:12 ` [PATCH 01/11] mt76: add more states Stanislaw Gruszka
2018-07-05  6:12 ` [PATCH 02/11] mt76x0: core files Stanislaw Gruszka
2018-07-05  6:12 ` [PATCH 03/11] mt76x0: mac files Stanislaw Gruszka
2018-07-05 15:17   ` Lorenzo Bianconi
2018-07-05  6:12 ` [PATCH 04/11] mt76x0: usb files Stanislaw Gruszka
2018-07-05 15:05   ` Lorenzo Bianconi
2018-07-06 10:42     ` Stanislaw Gruszka
2018-07-23  6:38     ` Kalle Valo
2018-07-23  8:57       ` Lorenzo Bianconi
2018-07-23  9:07         ` Kalle Valo
2018-07-23  9:31           ` Lorenzo Bianconi
2018-07-05  6:12 ` [PATCH 05/11] mt76x0: mcu files Stanislaw Gruszka
2018-07-05 15:13   ` Lorenzo Bianconi
2018-07-05  6:12 ` [PATCH 06/11] mt76x0: phy files Stanislaw Gruszka
2018-07-05  6:12 ` [PATCH 07/11] mt76x0: init files Stanislaw Gruszka
2018-07-05  6:12 ` [PATCH 08/11] mt76x0: eeprom files Stanislaw Gruszka
2018-07-05  6:12 ` [PATCH 09/11] mt76x0: trace and debugfs files Stanislaw Gruszka
2018-07-05  6:12 ` [PATCH 10/11] mt76x0: dma and tx files Stanislaw Gruszka
2018-07-05  6:12 ` [PATCH 11/11] mt76: Kconfig and Makefile for mt76x0 driver Stanislaw Gruszka
2018-07-05  8:40   ` kbuild test robot
2018-07-05 14:50   ` Lorenzo Bianconi
2018-07-06 10:32     ` Stanislaw Gruszka
2018-07-05 15:32 ` [PATCH 00/11] Add " Lorenzo Bianconi
2018-07-06 10:36   ` Stanislaw Gruszka
2018-07-06 11:37     ` Lorenzo Bianconi
2018-07-07  8:38   ` Hans Ulli Kroll [this message]
2018-07-20 10:30     ` Stanislaw Gruszka
2018-07-20 10:36       ` Stanislaw Gruszka
2018-07-20 12:18       ` Lorenzo Bianconi

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=alpine.LNX.2.00.1807071027140.11361@T420s \
    --to=ulli.kroll@googlemail.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=sgruszka@redhat.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