From: Stanislaw Gruszka <sgruszka@redhat.com> To: Kalle Valo <kvalo@codeaurora.org>, Sean Wang <sean.wang@mediatek.com> Cc: linux-wireless@vger.kernel.org, Lorenzo Bianconi <lorenzo.bianconi@redhat.com>, 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 v3 00/14] Add mt76x0 driver Date: Wed, 1 Aug 2018 10:25:09 +0200 [thread overview] Message-ID: <20180801082508.GA4526@redhat.com> (raw) In-Reply-To: <87y3dqzga9.fsf@purkki.adurom.net> On Wed, Aug 01, 2018 at 10:39:58AM +0300, Kalle Valo wrote: > Stanislaw Gruszka <sgruszka@redhat.com> writes: > > > Add mt76x0 driver for MT7610U based USB dongles. Currently driver > > support only STA mode. > > > > 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. > > So what's the future for mt7601u, are we going to delete it? What's > Jakub's opinion about all this? And what's the delta featurewise between > mt7601u and this driver? Which one will be loaded by default? mt7601u is driver for different chip: MT7601. This driver if for MT7610 chip. There are lot of similarities between the drivers, but there are bunch of differences too. And in the future development of mt76x0, due to integration into mt76 and mt76x2u and adding support for PCIe chips, the differences against mt7601u will be much be bigger. > Also I noticed that mt76 is missing an entry in MAINTAINERS file? Could > someone send a separate patch to add that, please? The question is if Felix would like to be the maintainer? Otherwise who would want to do this job? I think the best option would be to get some commitment from Mediatek if that possible, maybe Sean Wang could aggree to be the maintainer ? :-) Thanks Stanislaw
WARNING: multiple messages have this Message-ID (diff)
From: Stanislaw Gruszka <sgruszka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> To: Kalle Valo <kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>, Sean Wang <sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org> Cc: linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Lorenzo Bianconi <lorenzo.bianconi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>, Felix Fietkau <nbd-Vt+b4OUoWG0@public.gmane.org>, Hans Ulli Kroll <ulli.kroll-gM/Ye1E23mwN+BqQ9rBEUg@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 v3 00/14] Add mt76x0 driver Date: Wed, 1 Aug 2018 10:25:09 +0200 [thread overview] Message-ID: <20180801082508.GA4526@redhat.com> (raw) In-Reply-To: <87y3dqzga9.fsf-5ukZ45wKbUHoml4zekdYB16hYfS7NtTn@public.gmane.org> On Wed, Aug 01, 2018 at 10:39:58AM +0300, Kalle Valo wrote: > Stanislaw Gruszka <sgruszka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> writes: > > > Add mt76x0 driver for MT7610U based USB dongles. Currently driver > > support only STA mode. > > > > 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. > > So what's the future for mt7601u, are we going to delete it? What's > Jakub's opinion about all this? And what's the delta featurewise between > mt7601u and this driver? Which one will be loaded by default? mt7601u is driver for different chip: MT7601. This driver if for MT7610 chip. There are lot of similarities between the drivers, but there are bunch of differences too. And in the future development of mt76x0, due to integration into mt76 and mt76x2u and adding support for PCIe chips, the differences against mt7601u will be much be bigger. > Also I noticed that mt76 is missing an entry in MAINTAINERS file? Could > someone send a separate patch to add that, please? The question is if Felix would like to be the maintainer? Otherwise who would want to do this job? I think the best option would be to get some commitment from Mediatek if that possible, maybe Sean Wang could aggree to be the maintainer ? :-) Thanks Stanislaw
next prev parent reply other threads:[~2018-08-01 10:09 UTC|newest] Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-07-31 12:40 [PATCH v3 00/14] Add mt76x0 driver Stanislaw Gruszka 2018-07-31 12:40 ` Stanislaw Gruszka 2018-07-31 12:40 ` [PATCH v3 01/14] mt76x0: core files Stanislaw Gruszka 2018-07-31 12:40 ` Stanislaw Gruszka 2018-08-02 18:52 ` Kalle Valo 2018-08-02 18:52 ` Kalle Valo [not found] ` <1533040864-9026-2-git-send-email-sgruszka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> 2018-08-02 18:52 ` Kalle Valo 2018-07-31 12:40 ` [PATCH v3 02/14] mt76x0: mac files Stanislaw Gruszka 2018-07-31 12:40 ` Stanislaw Gruszka 2018-07-31 12:40 ` [PATCH v3 03/14] mt76x0: usb files Stanislaw Gruszka 2018-07-31 12:40 ` Stanislaw Gruszka 2018-07-31 12:40 ` [PATCH v3 04/14] mt76x0: mcu files Stanislaw Gruszka 2018-07-31 12:40 ` Stanislaw Gruszka 2018-07-31 12:40 ` [PATCH v3 05/14] mt76x0: phy files Stanislaw Gruszka 2018-07-31 12:40 ` Stanislaw Gruszka 2018-07-31 12:40 ` [PATCH v3 06/14] mt76x0: init files Stanislaw Gruszka 2018-07-31 12:40 ` Stanislaw Gruszka 2018-07-31 12:40 ` [PATCH v3 07/14] mt76x0: eeprom files Stanislaw Gruszka 2018-07-31 12:40 ` Stanislaw Gruszka 2018-07-31 12:40 ` [PATCH v3 08/14] mt76x0: trace and debugfs files Stanislaw Gruszka 2018-07-31 12:40 ` Stanislaw Gruszka 2018-07-31 12:40 ` [PATCH v3 09/14] mt76x0: dma and tx files Stanislaw Gruszka 2018-07-31 12:40 ` Stanislaw Gruszka 2018-07-31 12:41 ` [PATCH v3 10/14] mt76x0: main file Stanislaw Gruszka 2018-07-31 12:41 ` Stanislaw Gruszka 2018-07-31 12:41 ` [PATCH v3 11/14] mt76: add more states Stanislaw Gruszka 2018-07-31 12:41 ` Stanislaw Gruszka 2018-07-31 12:41 ` [PATCH v3 12/14] mt76: Kconfig and Makefile for mt76x0 driver Stanislaw Gruszka 2018-07-31 12:41 ` Stanislaw Gruszka 2018-08-01 7:32 ` Kalle Valo 2018-08-01 7:32 ` Kalle Valo 2018-08-01 8:28 ` Stanislaw Gruszka 2018-08-01 8:28 ` Stanislaw Gruszka 2018-08-01 8:41 ` Kalle Valo 2018-08-01 8:41 ` Kalle Valo 2018-08-01 8:59 ` Stanislaw Gruszka 2018-08-01 8:59 ` Stanislaw Gruszka 2018-08-02 17:11 ` Kalle Valo 2018-08-02 17:11 ` Kalle Valo 2018-07-31 12:41 ` [PATCH v3 13/14] mt76x0: disable HW before probe Stanislaw Gruszka 2018-07-31 12:41 ` Stanislaw Gruszka 2018-07-31 12:41 ` [PATCH v3 14/14] mt76x0: load firmware from mediatek subdir Stanislaw Gruszka 2018-07-31 12:41 ` Stanislaw Gruszka 2018-08-01 7:39 ` [PATCH v3 00/14] Add mt76x0 driver Kalle Valo 2018-08-01 7:39 ` Kalle Valo 2018-08-01 8:13 ` Lorenzo Bianconi 2018-08-01 8:13 ` Lorenzo Bianconi 2018-08-01 8:19 ` Kalle Valo 2018-08-01 8:19 ` Kalle Valo 2018-08-01 8:25 ` Stanislaw Gruszka [this message] 2018-08-01 8:25 ` Stanislaw Gruszka 2018-08-01 8:40 ` Lorenzo Bianconi 2018-08-01 8:40 ` Lorenzo Bianconi 2018-08-02 17:20 ` Kalle Valo 2018-08-02 17:20 ` Kalle Valo
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=20180801082508.GA4526@redhat.com \ --to=sgruszka@redhat.com \ --cc=kubakici@wp.pl \ --cc=kvalo@codeaurora.org \ --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: linkBe 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.