From: Stanislaw Gruszka <sgruszka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Hans Ulli Kroll <ulli.kroll-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Cc: Lorenzo Bianconi
<lorenzo.bianconi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Felix Fietkau <nbd-Vt+b4OUoWG0@public.gmane.org>,
Jakub Kicinski <kubakici-5tc4TXWwyLM@public.gmane.org>,
Michal Schmidt <mschmidt-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 00/11] Add mt76x0 driver
Date: Fri, 20 Jul 2018 12:36:29 +0200 [thread overview]
Message-ID: <20180720103628.GA1817@redhat.com> (raw)
In-Reply-To: <20180720103032.GA1791-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Fri, Jul 20, 2018 at 12:30:32PM +0200, Stanislaw Gruszka wrote:
> On Sat, Jul 07, 2018 at 10:38:27AM +0200, Hans Ulli Kroll wrote:
> > > > 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
>
> For the record. I unified bunch of mac80211 callbacks and mac/wcid functions
> and structures (including structures pointed above) into new mt76xx_lib
> module. I also rebased the changes on top of latest wireless-drivers-next
> master and mt76x2u patches in new branch mt76x0-draft-v2:
> https://github.com/sgruszka/wireless-drivers-next/commits/mt76x0-draft-v2
Forgot to wrote that I tested changes only for mt76x0 (sill waiting for
ordered mt76x2 HW) but common code is basically a copy of mt76x2 code
(if mt76x0 implementation differ, the one form mt76x2 was used). However
there are some changes that affect mt76x2 as well. Hopefully I did not break
anything there, but I can not be sure for now.
Stanislaw
WARNING: multiple messages have this Message-ID (diff)
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Hans Ulli Kroll <ulli.kroll@googlemail.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>,
linux-wireless@vger.kernel.org, Felix Fietkau <nbd@nbd.name>,
Jakub Kicinski <kubakici@wp.pl>,
Michal Schmidt <mschmidt@redhat.com>,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 00/11] Add mt76x0 driver
Date: Fri, 20 Jul 2018 12:36:29 +0200 [thread overview]
Message-ID: <20180720103628.GA1817@redhat.com> (raw)
In-Reply-To: <20180720103032.GA1791@redhat.com>
On Fri, Jul 20, 2018 at 12:30:32PM +0200, Stanislaw Gruszka wrote:
> On Sat, Jul 07, 2018 at 10:38:27AM +0200, Hans Ulli Kroll wrote:
> > > > 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
>
> For the record. I unified bunch of mac80211 callbacks and mac/wcid functions
> and structures (including structures pointed above) into new mt76xx_lib
> module. I also rebased the changes on top of latest wireless-drivers-next
> master and mt76x2u patches in new branch mt76x0-draft-v2:
> https://github.com/sgruszka/wireless-drivers-next/commits/mt76x0-draft-v2
Forgot to wrote that I tested changes only for mt76x0 (sill waiting for
ordered mt76x2 HW) but common code is basically a copy of mt76x2 code
(if mt76x0 implementation differ, the one form mt76x2 was used). However
there are some changes that affect mt76x2 as well. Hopefully I did not break
anything there, but I can not be sure for now.
Stanislaw
next prev parent reply other threads:[~2018-07-20 10:36 UTC|newest]
Thread overview: 60+ 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 ` Stanislaw Gruszka
[not found] ` <1530771142-4118-1-git-send-email-sgruszka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-07-05 6:12 ` [PATCH 01/11] mt76: add more states Stanislaw Gruszka
2018-07-05 6:12 ` Stanislaw Gruszka
2018-07-05 6:12 ` [PATCH 02/11] mt76x0: core files Stanislaw Gruszka
2018-07-05 6:12 ` Stanislaw Gruszka
2018-07-05 6:12 ` [PATCH 03/11] mt76x0: mac files Stanislaw Gruszka
2018-07-05 6:12 ` Stanislaw Gruszka
[not found] ` <1530771142-4118-4-git-send-email-sgruszka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-07-05 15:17 ` Lorenzo Bianconi
2018-07-05 15:17 ` Lorenzo Bianconi
2018-07-05 6:12 ` [PATCH 04/11] mt76x0: usb files Stanislaw Gruszka
2018-07-05 6:12 ` Stanislaw Gruszka
[not found] ` <1530771142-4118-5-git-send-email-sgruszka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-07-05 15:05 ` Lorenzo Bianconi
2018-07-05 15:05 ` Lorenzo Bianconi
[not found] ` <20180705150519.GB17524-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2018-07-06 10:42 ` Stanislaw Gruszka
2018-07-06 10:42 ` Stanislaw Gruszka
2018-07-23 6:38 ` Kalle Valo
2018-07-23 6:38 ` Kalle Valo
[not found] ` <87va96tq1g.fsf-5ukZ45wKbUHoml4zekdYB16hYfS7NtTn@public.gmane.org>
2018-07-23 8:57 ` Lorenzo Bianconi
2018-07-23 8:57 ` Lorenzo Bianconi
[not found] ` <CAJ0CqmV_pPrKnRvcCrn-pUNGgJ9bDoFY+H2u0eokOayX7N08oA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-07-23 9:07 ` Kalle Valo
2018-07-23 9:07 ` Kalle Valo
[not found] ` <87pnzexqul.fsf-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-07-23 9:31 ` Lorenzo Bianconi
2018-07-23 9:31 ` Lorenzo Bianconi
2018-07-05 6:12 ` [PATCH 05/11] mt76x0: mcu files Stanislaw Gruszka
2018-07-05 6:12 ` Stanislaw Gruszka
[not found] ` <1530771142-4118-6-git-send-email-sgruszka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-07-05 15:13 ` Lorenzo Bianconi
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 ` Stanislaw Gruszka
2018-07-05 6:12 ` [PATCH 07/11] mt76x0: init files Stanislaw Gruszka
2018-07-05 6:12 ` Stanislaw Gruszka
2018-07-05 6:12 ` [PATCH 08/11] mt76x0: eeprom files Stanislaw Gruszka
2018-07-05 6:12 ` Stanislaw Gruszka
2018-07-05 6:12 ` [PATCH 09/11] mt76x0: trace and debugfs files Stanislaw Gruszka
2018-07-05 6:12 ` Stanislaw Gruszka
2018-07-05 6:12 ` [PATCH 10/11] mt76x0: dma and tx files Stanislaw Gruszka
2018-07-05 6:12 ` Stanislaw Gruszka
2018-07-05 6:12 ` [PATCH 11/11] mt76: Kconfig and Makefile for mt76x0 driver Stanislaw Gruszka
2018-07-05 6:12 ` Stanislaw Gruszka
[not found] ` <1530771142-4118-12-git-send-email-sgruszka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-07-05 8:40 ` kbuild test robot
2018-07-05 8:40 ` kbuild test robot
2018-07-05 14:50 ` Lorenzo Bianconi
2018-07-05 14:50 ` Lorenzo Bianconi
[not found] ` <20180705145018.GA17524-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2018-07-06 10:32 ` Stanislaw Gruszka
2018-07-06 10:32 ` Stanislaw Gruszka
2018-07-05 15:32 ` [PATCH 00/11] Add " Lorenzo Bianconi
2018-07-05 15:32 ` Lorenzo Bianconi
[not found] ` <20180705153216.GE17524-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2018-07-06 10:36 ` Stanislaw Gruszka
2018-07-06 10:36 ` Stanislaw Gruszka
[not found] ` <20180706103657.GB2033-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-07-06 11:37 ` Lorenzo Bianconi
2018-07-06 11:37 ` Lorenzo Bianconi
2018-07-07 8:38 ` Hans Ulli Kroll
2018-07-07 8:38 ` Hans Ulli Kroll
2018-07-20 10:30 ` Stanislaw Gruszka
2018-07-20 10:30 ` Stanislaw Gruszka
[not found] ` <20180720103032.GA1791-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-07-20 10:36 ` Stanislaw Gruszka [this message]
2018-07-20 10:36 ` Stanislaw Gruszka
2018-07-20 12:18 ` Lorenzo Bianconi
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=20180720103628.GA1817@redhat.com \
--to=sgruszka-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=kubakici-5tc4TXWwyLM@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lorenzo.bianconi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=mschmidt-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=nbd-Vt+b4OUoWG0@public.gmane.org \
--cc=ulli.kroll-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.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 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.