public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Phillip Potter <phil@philpotter.co.uk>
To: Zameer Manji <zmanji@gmail.com>
Cc: Pavel Skripkin <paskripkin@gmail.com>,
	linux-staging@lists.linux.dev,
	"Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	Martin Kaiser <martin@kaiser.cx>,
	Michael Straube <straube.linux@gmail.com>
Subject: Re: r8188eu driver in 5.15 only shows wifi networks on channel 11
Date: Sat, 6 Nov 2021 16:59:39 +0000	[thread overview]
Message-ID: <YYa0e98JTsE0PPDL@equinox> (raw)
In-Reply-To: <CABtXzjQk87ZhYcc2h5mU0mR+6zC7rKrpP-g6uE=DxE56NXQXpA@mail.gmail.com>

On Sat, Nov 06, 2021 at 11:48:08AM -0400, Zameer Manji wrote:
> Hello All,
> 
> I have bisected the regression to
> ```
> commit 221abd4d478ab52fd17de9287fa302ac0e06f7b3
> Author: Fabio M. De Francesco <fmdefrancesco@gmail.com>
> Date:   Thu Aug 12 02:25:19 2021 +0200
> 
>     staging: r8188eu: Remove no more necessary definitions and code
> ```
> 
> Prior to this change the device can see all networks on all channels.
> With this change, the device can only see networks on channel 11.
> I suspect this might be specific to the RTL8188EUS variant
> of the hardware. Unfortunately I don't know enough about
> this driver or the hardware to understand where the issue
> is in the change.
> 
> Full bisection log is here
> ```

Hi Zameer,

Thanks for doing this bisection, super useful. I will have a play after
my daughter has gone to bed and see if I can see anything :-)

Assuming me or someone else finds the cause, would you be happy to test
a patch?

Regards,
Phil

  reply	other threads:[~2021-11-06 16:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05  4:34 r8188eu driver in 5.15 only shows wifi networks on channel 11 Zameer Manji
2021-11-05  9:20 ` Pavel Skripkin
2021-11-05 21:03   ` Zameer Manji
2021-11-06  0:29     ` Phillip Potter
2021-11-06  8:32     ` Pavel Skripkin
2021-11-06  9:48       ` Pavel Skripkin
2021-11-06 13:21         ` Zameer Manji
2021-11-06 15:48           ` Zameer Manji
2021-11-06 16:59             ` Phillip Potter [this message]
2021-11-06 17:16               ` Zameer Manji
2021-11-06 18:09                 ` Larry Finger
2021-11-06 18:30                   ` Phillip Potter
2021-11-06 18:49                     ` Phillip Potter
2021-11-06 19:29                       ` Zameer Manji
2021-11-06 19:46                         ` Larry Finger
2021-11-06 19:56                           ` Zameer Manji
2021-11-06 21:33                             ` Phillip Potter
2021-11-06 17:44             ` Larry Finger
2021-11-06 17:52             ` Larry Finger
2021-11-06 19:26           ` Pavel Skripkin
2021-11-06 22:17             ` Fabio M. De Francesco
2021-11-06 23:05               ` Phillip Potter

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=YYa0e98JTsE0PPDL@equinox \
    --to=phil@philpotter.co.uk \
    --cc=Larry.Finger@lwfinger.net \
    --cc=fmdefrancesco@gmail.com \
    --cc=linux-staging@lists.linux.dev \
    --cc=martin@kaiser.cx \
    --cc=paskripkin@gmail.com \
    --cc=straube.linux@gmail.com \
    --cc=zmanji@gmail.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