linux-kernel - Re: [BUG] staging: r8822be: RTL8822be can't find any wireless AP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <7e95bd6a-97bc-b030-26ce-83da66e5f279@lwfinger.net>
Date:   Wed, 4 Jul 2018 10:13:20 -0500
From:   Larry Finger <Larry.Finger@...inger.net>
To:     Dan Carpenter <dan.carpenter@...cle.com>
Cc:     Jian-Hong Pan <jian-hong@...lessm.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "Frank A. Cancio Bello" <frank@...eralsoftwareinc.com>,
        Stanislaw Gruszka <sgruszka@...hat.com>,
        devel@...verdev.osuosl.org, Kalle Valo <kvalo@...eaurora.org>,
        linux-wireless@...r.kernel.org,
        Linux Kernel <linux-kernel@...r.kernel.org>,
        Linux Upstreaming Team <linux@...lessm.com>,
        Colin Ian King <colin.king@...onical.com>,
        Ping-Ke Shih <pkshih@...ltek.com>,
        Arnd Bergmann <arnd@...db.de>
Subject: Re: [BUG] staging: r8822be: RTL8822be can't find any wireless AP

On 07/04/2018 09:09 AM, Dan Carpenter wrote:
> On Wed, Jul 04, 2018 at 08:55:00AM -0500, Larry Finger wrote:
>> I do not think this is a bug.
> 
> It's obviously a bug.  The driver should just work by default.
> 
> As a last resort, we would do something like add quirk or something.  I
> haven't looked at how quirks would be handled for this driver but grep
> for quirk to see how other drivers do it.

We will have to agree to disagree.

I have no idea what the vendors are doing that cause some motherboards to need a 
different aspm value. What I do know is that we have had to live with the idiocy 
of some vendors saving a few pennies by only including a single antenna, rather 
than two, and then making a problem by miscoding the EFUSE bit that indicates 
which connector is actually in use. As we have no means that I know about to 
detect which boxes have the problem, a module parameter was created, just as in 
this case.

I agree that drivers should work "out of the box", but finite resources and lack 
of vendor cooperation make this a goal that may not be attainable.

Larry