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>,
	"Jakub Kiciński" <moorray3@wp.pl>,
	"Hans Ulli Kroll" <ulli.kroll@googlemail.com>,
	"Michal Schmidt" <mschmidt@redhat.com>,
	linux-mediatek@lists.infradead.org
Subject: Re: [ANN] mt76x0 usb driver
Date: Mon, 9 Apr 2018 20:52:05 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1804092045270.8369@T420s> (raw)
In-Reply-To: <20180409145342.GB5680@localhost.localdomain>

Hi

On Mon, 9 Apr 2018, Lorenzo Bianconi wrote:

> On Apr 09, Stanislaw Gruszka wrote:
> > On Mon, Apr 09, 2018 at 04:26:42PM +0200, Lorenzo Bianconi wrote:
> > > > I would like to integrate the driver to kernel via mt76 driver, i.e.
> > > > add USB hooks and mt76x0 mac/phy code to mt76. This will open
> > > > possibility to develop support for mt76x2 USB devices as well as mt76x0
> > > > PCIe devices in mt76.
> > > > 
> > > 
> > > I have already started supporting mt76x2 USB devices in mt76 since register map
> > > is pretty similar to PCIe devices:
> > > https://github.com/LorenzoBianconi/wireless-drivers-next/tree/mt76x2u
> > > I added some usb utility routines so I think we can integrate mt76x0 in mt76 as
> > > well
> > 
> > Great, I'll start to integrate mt76x0 on top of your tree.
> 
> Cool :) actually this branch is in under development but what is really
> changing day by day is mt7612u part not usb one so I guess we can use it as
> common ground for mt76x2u and mt76x0.
> Maybe even the mcu code is in common with mt76x2, isn't it?
> 

from my POV for "general" commands the MCU on mt76x0 and mt76x2 (doesn't 
matter if USB or PCIe) are almost the same i.e. CMD_FUN_SET_OP

The only difference is CMD_CALIBRATION_OP, they are for mt76x0 and mt76x2 
different calibrate id's.

How about the LED on mt76x2 ?

Greetings
Hans

  reply	other threads:[~2018-04-09 18:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-09 14:10 [ANN] mt76x0 usb driver Stanislaw Gruszka
2018-04-09 14:26 ` Lorenzo Bianconi
2018-04-09 14:48   ` Stanislaw Gruszka
2018-04-09 14:53     ` Lorenzo Bianconi
2018-04-09 18:52       ` Hans Ulli Kroll [this message]
2018-04-10 10:12       ` Stanislaw Gruszka
2018-06-25 12:08     ` Stanislaw Gruszka
2018-06-25 12:55       ` Lorenzo Bianconi
2018-06-25 13:54         ` Stanislaw Gruszka
2018-06-28 17:26           ` Lorenzo Bianconi
2018-07-03 15:31             ` Hans Ulli Kroll
2018-07-04 14:00               ` Stanislaw Gruszka
2018-04-09 18:45 ` Hans Ulli Kroll
2018-04-10 10:14   ` Stanislaw Gruszka
2018-04-16 22:30     ` 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.1804092045270.8369@T420s \
    --to=ulli.kroll@googlemail.com \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=moorray3@wp.pl \
    --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