From: patchwork-bot+netdevbpf@kernel.org
To: Magnus Lindholm <linmag7@gmail.com>
Cc: pavan.chebbi@broadcom.com, andrew+netdev@lunn.ch,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3] tg3: normalize inherited BCM5718 register byte order
Date: Sat, 17 Oct 2026 00:50:11 +0000 [thread overview]
Message-ID: <179219821101.1034269.14465914522472303351.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261011194228.981141-1-linmag7@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 11 Oct 2026 21:41:58 +0200 you wrote:
> Firmware can leave BCM5718 vendor registers byte-swapped while standard
> PCI fields retain normal byte order. Detect this from the host-control
> revision marker, byte-swap bit and swapped product ID, without matching
> a platform model or PCI subsystem. Prefer the normal revision marker
> so already-normal controllers do not enter the normalization path.
>
> Hardware swapping can accommodate big-endian register accesses, but tg3
> already initializes misc_host_ctrl with WORD_SWAP set and BYTE_SWAP clear
> on both little- and big-endian builds. Its normal MMIO path uses
> readl()/writel(); on SPARC64 these use little-endian accesses. Restore
> that existing register mode rather than choosing a mode based on host
> endianness. The swab32() on the initial write compensates for the device's
> inherited state; subsequent accesses use the normal driver path.
>
> [...]
Here is the summary with links:
- [net-next,v3] tg3: normalize inherited BCM5718 register byte order
https://git.kernel.org/netdev/net-next/c/4f9fbb30e341
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-17 0:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 19:41 [PATCH net-next v3] tg3: normalize inherited BCM5718 register byte order Magnus Lindholm
2026-10-16 21:38 ` Sebastian Andrzej Siewior
2026-10-17 0:50 ` patchwork-bot+netdevbpf [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=179219821101.1034269.14465914522472303351.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linmag7@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=sparclinux@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.