All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Büsch" <m@bues.ch>
To: Rahul Rameshbabu <sergeantsagara@protonmail.com>
Cc: Kalle Valo <kvalo@kernel.org>,
	linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH wireless 5/5] wifi: b43: Support advertising lack of QoS capability
Date: Sat, 30 Dec 2023 18:43:35 +0100	[thread overview]
Message-ID: <20231230184335.53e33db2@barney> (raw)
In-Reply-To: <87cyunk45e.fsf@protonmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 692 bytes --]

On Sat, 30 Dec 2023 17:10:26 +0000
Rahul Rameshbabu <sergeantsagara@protonmail.com> wrote:

> > The firmware probably is just too old for this device.  
> 
> I just retested with newer firmware released on 2012-08-15. I still see
> the same issue with QoS. This appears to be the newest firmware I can
> acquire from http://lwfinger.com/b43-firmware/, which I extract from
> broadcom-wl-6.30.163.46.

It's still pretty old.
Nobody has worked on getting a newer version extracted for a long time.

But I'm fine with just disabling QoS on this device.
Upgrading to a newer firmware probably is a bigger change.
That could be done later.

-- 
Michael Büsch
https://bues.ch/

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

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
b43-dev mailing list
b43-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/b43-dev

WARNING: multiple messages have this Message-ID (diff)
From: "Michael Büsch" <m@bues.ch>
To: Rahul Rameshbabu <sergeantsagara@protonmail.com>
Cc: Kalle Valo <kvalo@kernel.org>,
	linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH wireless 5/5] wifi: b43: Support advertising lack of QoS capability
Date: Sat, 30 Dec 2023 18:43:35 +0100	[thread overview]
Message-ID: <20231230184335.53e33db2@barney> (raw)
In-Reply-To: <87cyunk45e.fsf@protonmail.com>

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

On Sat, 30 Dec 2023 17:10:26 +0000
Rahul Rameshbabu <sergeantsagara@protonmail.com> wrote:

> > The firmware probably is just too old for this device.  
> 
> I just retested with newer firmware released on 2012-08-15. I still see
> the same issue with QoS. This appears to be the newest firmware I can
> acquire from http://lwfinger.com/b43-firmware/, which I extract from
> broadcom-wl-6.30.163.46.

It's still pretty old.
Nobody has worked on getting a newer version extracted for a long time.

But I'm fine with just disabling QoS on this device.
Upgrading to a newer firmware probably is a bigger change.
That could be done later.

-- 
Michael Büsch
https://bues.ch/

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

  reply	other threads:[~2023-12-30 17:44 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-30  4:51 [PATCH wireless 0/5] wifi: b43: Various QoS-related fixes Rahul Rameshbabu
2023-12-30  4:51 ` Rahul Rameshbabu
2023-12-30  4:51 ` [PATCH wireless 1/5] wifi: b43: Correct OpenFW QoS capability warning conditional Rahul Rameshbabu
2023-12-30  4:51   ` Rahul Rameshbabu
2023-12-30 13:34   ` Michael Büsch
2023-12-30 13:34     ` Michael Büsch
2023-12-30 17:17     ` Rahul Rameshbabu
2023-12-30 17:17       ` Rahul Rameshbabu
2023-12-30  4:51 ` [PATCH wireless 2/5] wifi: b43: Stop/wake correct queue in DMA Tx path when QoS is disabled Rahul Rameshbabu
2023-12-30  4:51   ` Rahul Rameshbabu
2023-12-30  7:48   ` Julian Calaby
2023-12-30  7:48     ` Julian Calaby
2023-12-30 13:40     ` Michael Büsch
2023-12-30 13:40       ` Michael Büsch
2023-12-30 17:15       ` Rahul Rameshbabu
2023-12-30 17:15         ` Rahul Rameshbabu
2023-12-30 17:41         ` Michael Büsch
2023-12-30 17:41           ` Michael Büsch
2023-12-30 19:37           ` Rahul Rameshbabu
2023-12-30 19:37             ` Rahul Rameshbabu
2023-12-30  4:51 ` [PATCH wireless 3/5] wifi: b43: Stop/wake correct queue in PIO " Rahul Rameshbabu
2023-12-30  4:51   ` Rahul Rameshbabu
2023-12-30 18:04   ` Larry Finger
2023-12-30 18:04     ` Larry Finger
2023-12-30 19:43     ` Rahul Rameshbabu
2023-12-30 19:43       ` Rahul Rameshbabu
2023-12-30 22:23       ` Larry Finger
2023-12-30 22:23         ` Larry Finger
2023-12-31  0:02         ` Rahul Rameshbabu
2023-12-31  0:02           ` Rahul Rameshbabu
2023-12-31  9:33           ` Michael Büsch
2023-12-31  9:33             ` Michael Büsch
2023-12-31 17:29             ` Rahul Rameshbabu
2023-12-31 17:29               ` Rahul Rameshbabu
2023-12-30  4:51 ` [PATCH wireless 4/5] wifi: b43: Stop correct queue in DMA worker " Rahul Rameshbabu
2023-12-30  4:51   ` Rahul Rameshbabu
2023-12-30  4:51 ` [PATCH wireless 5/5] wifi: b43: Support advertising lack of QoS capability Rahul Rameshbabu
2023-12-30  4:51   ` Rahul Rameshbabu
2023-12-30 13:45   ` Michael Büsch
2023-12-30 13:45     ` Michael Büsch
2023-12-30 17:10     ` Rahul Rameshbabu
2023-12-30 17:10       ` Rahul Rameshbabu
2023-12-30 17:43       ` Michael Büsch [this message]
2023-12-30 17:43         ` Michael Büsch

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=20231230184335.53e33db2@barney \
    --to=m@bues.ch \
    --cc=b43-dev@lists.infradead.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sergeantsagara@protonmail.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 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.