All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alessio Ferri <alessio.ferri@mythread.it>
To: "andreas.wendleder" <andreas.wendleder@proton.me>
Cc: "b43-dev@lists.infradead.org" <b43-dev@lists.infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: b43: ac rev1 captured packets with ampdu
Date: Sat, 10 Oct 2026 16:01:22 +0200	[thread overview]
Message-ID: <20261010160122.5e82eaec@fedora> (raw)
In-Reply-To: <j7yDoG5_QzsvHn2hPYg-t1IRCKILne4bSf-E0ix15-48INcyh3HHnBydtcLdyWJCXh61NfsV1HawpRIBKpsGYzVzAfMCJIo3Z4Q-c20M15E=@proton.me>

Il giorno Fri, 09 Oct 2026 23:16:40 +0000
"andreas.wendleder" <andreas.wendleder@proton.me> ha scritto:

> Hi Alessio,
> 
> Thanks for the captures. I’ll look at them when I get to 5 GHz, where
> my RX is still broken.
> 
> Your driver no longer hangs my machine. The hang was my own logging,
> a 30 ms delay on each of about 80000 table calls. Without it, your
> head (ce2127a) runs the whole init in about 5 s. The radio doesn’t
> come up on my chip, though: after the first channel I get radio 2069:
> power-on timeout (0x040b=0x0001), so the RCAL done bit never sets.
> 

Maybe you have still too many delays around power on?

> Your blocks (mode_init, set_reg_on_reset, coeff_bank_init, init_regs)
> let me replace my 290-write PHY replay with a 72-write init. 2.4 GHz
> now runs at about 20 Mbit/s up and 17 down. Do you know where PHY
> words 0x1739, 0x016b, 0x0175, 0x03c4 and 0x0197/0x0198 come from? I
> couldn’t find them in your code.
> 
> Thanks, Andreas

Do you mean that in version 6.30.x, the driver write 0x1739, 0x016b, 0x0175, 
0x03c4 and 0x0197/0x0198? Maybe they are related to bluetooth? Don't
know, will investigate it.

Thank you for your reporting!
Alessio

_______________________________________________
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: Alessio Ferri <alessio.ferri@mythread.it>
To: "andreas.wendleder" <andreas.wendleder@proton.me>
Cc: "b43-dev@lists.infradead.org" <b43-dev@lists.infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: b43: ac rev1 captured packets with ampdu
Date: Sat, 10 Oct 2026 16:01:22 +0200	[thread overview]
Message-ID: <20261010160122.5e82eaec@fedora> (raw)
In-Reply-To: <j7yDoG5_QzsvHn2hPYg-t1IRCKILne4bSf-E0ix15-48INcyh3HHnBydtcLdyWJCXh61NfsV1HawpRIBKpsGYzVzAfMCJIo3Z4Q-c20M15E=@proton.me>

Il giorno Fri, 09 Oct 2026 23:16:40 +0000
"andreas.wendleder" <andreas.wendleder@proton.me> ha scritto:

> Hi Alessio,
> 
> Thanks for the captures. I’ll look at them when I get to 5 GHz, where
> my RX is still broken.
> 
> Your driver no longer hangs my machine. The hang was my own logging,
> a 30 ms delay on each of about 80000 table calls. Without it, your
> head (ce2127a) runs the whole init in about 5 s. The radio doesn’t
> come up on my chip, though: after the first channel I get radio 2069:
> power-on timeout (0x040b=0x0001), so the RCAL done bit never sets.
> 

Maybe you have still too many delays around power on?

> Your blocks (mode_init, set_reg_on_reset, coeff_bank_init, init_regs)
> let me replace my 290-write PHY replay with a 72-write init. 2.4 GHz
> now runs at about 20 Mbit/s up and 17 down. Do you know where PHY
> words 0x1739, 0x016b, 0x0175, 0x03c4 and 0x0197/0x0198 come from? I
> couldn’t find them in your code.
> 
> Thanks, Andreas

Do you mean that in version 6.30.x, the driver write 0x1739, 0x016b, 0x0175, 
0x03c4 and 0x0197/0x0198? Maybe they are related to bluetooth? Don't
know, will investigate it.

Thank you for your reporting!
Alessio

  parent reply	other threads:[~2026-10-10 14:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 15:31 b43: ac rev1 captured packets with ampdu Alessio Ferri
2026-10-09 15:31 ` Alessio Ferri
2026-10-09 23:16 ` AW: " andreas.wendleder
2026-10-09 23:16   ` andreas.wendleder
2026-10-10 12:59   ` andreas.wendleder
2026-10-10 12:59     ` andreas.wendleder
2026-10-10 14:10     ` Alessio Ferri
2026-10-10 14:10       ` Alessio Ferri
2026-10-10 14:15       ` AW: " andreas.wendleder
2026-10-10 14:15         ` andreas.wendleder
2026-10-11 16:42         ` Alessio Ferri
2026-10-11 16:42           ` Alessio Ferri
2026-10-10 14:01   ` Alessio Ferri [this message]
2026-10-10 14:01     ` Alessio Ferri

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=20261010160122.5e82eaec@fedora \
    --to=alessio.ferri@mythread.it \
    --cc=andreas.wendleder@proton.me \
    --cc=b43-dev@lists.infradead.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 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.