All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Jes.Sorensen@redhat.com
Cc: linux-wireless@vger.kernel.org, Larry.Finger@lwfinger.net
Subject: Re: [PATCH 1/1] New driver: rtl8723au (mac80211)
Date: Tue, 28 Apr 2015 11:37:59 +0300	[thread overview]
Message-ID: <87383kps0o.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1427142300-28051-2-git-send-email-Jes.Sorensen@redhat.com> (Jes Sorensen's message of "Mon, 23 Mar 2015 16:25:00 -0400")

Jes.Sorensen@redhat.com writes:

> From: Jes Sorensen <Jes.Sorensen@redhat.com>
>
> This is an alternate driver for the Realtek 8723AU (rtl8723au) written
> from scratch utilizing the mac80211 stack.
>
> After spending months cleaning up the vendor provided rtl8723au
> driver, which comes with it's own 802.11 stack included, I decided to
> rewrite this driver from the bottom up.

Where is the vendor driver available, in staging or somewhere else? It
would be good to mention that in the commit log.

> Many thanks to Johannes Berg for 802.11 insights and help and Larry
> Finger for help with the vendor driver.
>
> The full git log for the development of this driver can be found here:
> git git://git.kernel.org/pub/scm/linux/kernel/git/jes/linux.git
>     branch rtl8723au-mac80211
>
> This driver is still experimental, but has proven to be rather stable
> for me. It lacks some features found in the staging driver, such as
> power management, AMPDU, and 40MHz channel support. In addition there
> is no AP and monitor support at this point.

It's nice to document in the commit log what features are verified to be
working.

Also I see incosistencies with driver naming, in some places I see
RTL8723au and elsewhere rtl8xxxu. And commit log title could be
improved, for example something like "rtl8xxxu: new wireless mac80211
driver for rtl8723au chipsets"

And I would like to understand the relationship with rtlwifi, can you
describe that a bit more? Why a separate driver instead of extending
rtlwifi? When I look at the directory drivers/net/wireless/rtlwifi/rtl8723ae 
I'm confused what's the bigger plan here. Larry?

>  MAINTAINERS                          |    8 +
>  drivers/net/wireless/Kconfig         |   19 +
>  drivers/net/wireless/Makefile        |    2 +
>  drivers/net/wireless/rtl8xxxu.c      | 4500 ++++++++++++++++++++++++++++++++++
>  drivers/net/wireless/rtl8xxxu.h      |  497 ++++
>  drivers/net/wireless/rtl8xxxu_regs.h |  941 +++++++

I think someone else already mentioned, but it would be better that has
it's own directory. Or should this actually be under rtlwifi directory?

> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -8297,6 +8297,14 @@ S:	Maintained
>  F:	drivers/net/wireless/rtlwifi/
>  F:	drivers/net/wireless/rtlwifi/rtl8192ce/
>  
> +RTL8XXXU WIRELESS DRIVER (rtl8xxxu)
> +M:	Jes Sorensen <Jes.Sorensen@redhat.com>
> +L:	linux-wireless@vger.kernel.org
> +W:	http://intellinuxwireless.org

The link cannot be right.

> +T:	git git://git.kernel.org/pub/scm/linux/kernel/git/jes/linux.git rtl8723au-mac80211

I doubt that this will be in active enough development that a separate
git tree is needed. wireless-drivers trees should be enough and this
line can be removed.

I'll do more detailed code review later, but my first impression was
that there was a lot of #if 0 code which is frowned upon.

And I pushed this to wireless-drivers-next.git pending branch so that
kbuild will run it's tests with this driver.

-- 
Kalle Valo

  parent reply	other threads:[~2015-04-28  8:38 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23 20:24 [PATCH v3 0/1] New driver: rtl8723au (mac80211) Jes.Sorensen
2015-03-23 20:25 ` [PATCH 1/1] " Jes.Sorensen
2015-03-23 22:51   ` Joe Perches
2015-03-24  1:25     ` Jes Sorensen
2015-04-28  8:37   ` Kalle Valo [this message]
2015-04-28 12:55     ` Kalle Valo
2015-04-28 14:27     ` Jes Sorensen
2015-04-28 15:15       ` Larry Finger
2015-09-06 13:38       ` Kalle Valo
2015-09-06 16:41         ` Larry Finger
2015-09-07 13:37           ` Kalle Valo
2015-09-07 18:43         ` Jes Sorensen
2015-09-07 18:50           ` Larry Finger
2015-09-09 14:16             ` Jes Sorensen
2015-09-29  8:56           ` Kalle Valo
2015-09-29 10:42             ` Jes Sorensen
  -- strict thread matches above, loose matches on Subject: below --
2015-05-05 20:04 Xose Vazquez Perez
2015-05-05 21:40 ` Jes Sorensen
2015-05-07  9:43   ` Xose Vazquez Perez
2015-05-07 15:43     ` Larry Finger
2015-03-09 17:00 [PATCH v2 0/1] " Jes.Sorensen
2015-03-09 17:00 ` [PATCH 1/1] " Jes.Sorensen
2015-03-09 17:46   ` Johannes Berg
2015-03-09 18:35     ` Jes Sorensen
2015-03-09 19:52       ` Johannes Berg
2015-03-09 18:20   ` Joe Perches
2015-03-09 18:43     ` Jes Sorensen
2015-03-09 18:51       ` Joe Perches
2015-03-09 19:02         ` Jes Sorensen
2015-03-09 19:07           ` Joe Perches
2015-03-06 22:15 [PATCH 0/1] " Jes.Sorensen
2015-03-06 22:15 ` [PATCH 1/1] " Jes.Sorensen
2015-03-06 22:59   ` Joe Perches
2015-03-07  5:18     ` Jes Sorensen
2015-03-07  5:23       ` Joe Perches
2015-03-07  5:33         ` Jes Sorensen
2015-03-07 21:30   ` Larry Finger
2015-03-09 17:08     ` Jes Sorensen

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=87383kps0o.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=Jes.Sorensen@redhat.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.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.