linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, Larry.Finger@lwfinger.net
Subject: Re: [PATCH v2 0/1] rtl8xxxu (mac80211) driver for rtl8188[cr]u/rtl8192cu/rtl8723au
Date: Tue, 08 Sep 2015 17:24:17 -0400	[thread overview]
Message-ID: <wrfjfv2oa9ku.fsf@redhat.com> (raw)
In-Reply-To: <878u8ifv1o.fsf@kamboji.qca.qualcomm.com> (Kalle Valo's message of "Mon, 07 Sep 2015 12:17:07 +0300")

Kalle Valo <kvalo@codeaurora.org> writes:
> Jes Sorensen <Jes.Sorensen@redhat.com> writes:
>
>> Kalle Valo <kvalo@codeaurora.org> writes:
>>> Jes.Sorensen@redhat.com writes:
>>>
>>>> Per default only devices I have actually tested will be enabled. If
>>>> you are interested in trying it out with other 8188cu/8188ru/819[12]cu
>>>> dongles, you need to enable CONFIG_RTL8XXXU_UNTESTED. Please report
>>>> test results back to me.
>>>>
>>>> Note if you enable this driver, it may clash with CONFIG_RTL8192U,
>>>> CONFIG_R8723AU, and CONFIG_RTL8192CU (rtlwifi). Please pay attention
>>>> to which module you load and/or use modprobe blacklists.
>>>
>>> May clash? So how does this work in practise? Is the clash referring
>>> CONFIG_RTL8XXXU_UNTESTED enabled or disabled?
>>>
>>> I think we should only have one driver automatically supporting certain
>>> hardware, and not have a driver randomly chosen and forcing users to use
>>> a blacklist.
>>
>> We already have the clash, if you enable CONFIG_RTL8192U in staging it
>> clashes with rtlwifi's CONFIG_RTL8192CU. Ripping out the above two
>> drivers at this point isn't going to do users any good.
>
> I'm not saying about we should remove drivers, my worry is only that we
> don't have two drivers competing about same devices in a normal distro
> kernel. We should _by default_ not have two drivers claiming support for
> the same device, developer's can of course enable this via experimental
> options etc.
>
>>> Also how do we make sure that distros don't enable
>>> CONFIG_RTL8XXXU_UNTESTED? They are notarious of enabling kconfig options
>>> without thinking.
>>
>> Some distros enable staging whether you ask them or not.
>
> Sure, that's up to them. I don't care what's in staging so I can't
> really comment about that, this is only in context of
> drivers/net/wireless/.

I'm with you, my point is just that we already have multiple drivers
claming this. It is not a new situation :( Right now the distros enable
the rtl drivers in staging because it is the only way to get support for
a number of realtek devices. At least OpenSuSE and Debian seem to be
enabling CONFIG_RTL8192U right now, while Fedora doesn't.

Cheers,
Jes

      reply	other threads:[~2015-09-08 21:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-30 21:02 [PATCH v2 0/1] rtl8xxxu (mac80211) driver for rtl8188[cr]u/rtl8192cu/rtl8723au Jes.Sorensen
2015-08-30 21:02 ` [PATCH 1/1] New driver: rtl8xxxu (mac80211) Jes.Sorensen
2015-09-06 14:59   ` Kalle Valo
2015-09-06 17:06     ` Larry Finger
2015-09-07  1:41       ` Jes Sorensen
2015-09-07  1:40     ` Jes Sorensen
2015-09-07 13:20       ` Kalle Valo
2015-09-07 21:08         ` Jes Sorensen
2015-09-06 14:43 ` [PATCH v2 0/1] rtl8xxxu (mac80211) driver for rtl8188[cr]u/rtl8192cu/rtl8723au Kalle Valo
2015-09-06 17:03   ` Larry Finger
2015-09-07  9:06     ` Kalle Valo
2015-09-07 15:35       ` Larry Finger
2015-09-08 21:04         ` Jes Sorensen
2015-09-08 21:13       ` Jes Sorensen
2015-09-08 21:01     ` Jes Sorensen
2015-09-09 10:51       ` Bruno Randolf
2015-09-07  1:45   ` Jes Sorensen
2015-09-07  4:24     ` Jes Sorensen
2015-09-07  8:53       ` Kalle Valo
2015-09-07  9:17     ` Kalle Valo
2015-09-08 21:24       ` Jes Sorensen [this message]

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=wrfjfv2oa9ku.fsf@redhat.com \
    --to=jes.sorensen@redhat.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=kvalo@codeaurora.org \
    --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 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).