linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleksij Rempel <linux@rempel-privat.de>
To: Felix Fietkau <nbd@openwrt.org>,
	Arend van Spriel <arend@broadcom.com>,
	"John W. Linville" <linville@tuxdriver.com>
Cc: Etna <etna@openmailbox.org>, linux-wireless@vger.kernel.org
Subject: Re: MediaTek WiFi hardware support in upstream kernel
Date: Tue, 11 Nov 2014 12:55:35 +0100	[thread overview]
Message-ID: <5461F937.9060004@rempel-privat.de> (raw)
In-Reply-To: <5450BEB2.60208@openwrt.org>

[-- Attachment #1: Type: text/plain, Size: 726 bytes --]

Am 29.10.2014 um 11:17 schrieb Felix Fietkau:
> Hi Hackers,
> 
> Just a quick heads up:
> I'm working on a new driver for MT7662E/MT7612E, written from scratch.
> It is already able to bring up the firmware, init the MAC and do basic
> TX/RX DMA communication with the firmware.
> I've decided to not integrate it with rt2x00, because I want to avoid
> dealing with the the unnecessarily convoluted abstractions and legacy
> code in there. I believe the result will be simpler and easier to
> maintain as a new driver.
> As soon as the basic structure is in place, I will put it on a public
> git tree and post a link here.
> 
> - Felix

Which chip would you suggest for starting?

-- 
Regards,
Oleksij


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

  reply	other threads:[~2014-11-11 11:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27  3:02 MediaTek WiFi hardware support in upstream kernel Etna
2014-10-27 15:20 ` John W. Linville
2014-10-27 18:19   ` Oleksij Rempel
2014-10-28 13:46     ` John W. Linville
2014-10-28 14:06       ` Arend van Spriel
2014-10-28 14:20         ` Oleksij Rempel
2014-10-29 10:17           ` Felix Fietkau
2014-11-11 11:55             ` Oleksij Rempel [this message]
2014-11-12 21:04               ` Felix Fietkau
2014-11-12 21:35                 ` Larry Finger
2015-02-06 17:29                   ` Jakub Kiciński
2015-02-25  0:49                     ` Sergei Antonov
2015-02-25  9:33                       ` mt7601u dies during channel switch (was: MediaTek WiFi hardware support in upstream kernel) Jakub Kiciński
2015-02-25 23:58                         ` Sergei Antonov
2015-02-26 16:05                           ` Jakub Kiciński
2015-02-26 18:50                             ` Sergei Antonov
2015-02-26 19:01                               ` Jakub Kiciński
2015-03-02 10:30                             ` Sergei Antonov
2015-02-26 13:56                     ` MediaTek WiFi hardware support in upstream kernel poma
2015-02-26 14:40                       ` Jakub Kiciński
     [not found]                         ` <5520FB36.8050301@openmailbox.org>
2015-04-05  9:12                           ` Etna
2015-05-18  0:03                         ` poma
2015-05-19  1:03                           ` poma
2015-05-20 17:06                           ` poma
2015-05-20 17:14                             ` Jakub Kiciński
2015-05-21 13:37                               ` poma
2015-06-27 20:45                                 ` poma
2015-12-23 15:05                                   ` poma

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=5461F937.9060004@rempel-privat.de \
    --to=linux@rempel-privat.de \
    --cc=arend@broadcom.com \
    --cc=etna@openmailbox.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=nbd@openwrt.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 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).