From: Florian Fainelli <f.fainelli@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, opendmb@gmail.com, andrew@lunn.ch,
vivien.didelot@savoirfairelinux.com,
Florian Fainelli <f.fainelli@gmail.com>
Subject: [PATCH net-next 0/4] Endian fixes for SYSTEMPORT/SF2/MDIO
Date: Tue, 29 Aug 2017 11:39:41 -0700 [thread overview]
Message-ID: <1504031985-52808-1-git-send-email-f.fainelli@gmail.com> (raw)
Hi David,
While trying an ARM BE kernel for kinks, the 3 drivers below started not
working and the reasons why became pretty obvious because the register space
remains LE (hardwired), except for Broadcom MIPS where it follows the CPU's
native endian (let's call that a feature).
Thanks!
Florian Fainelli (4):
net: systemport: Use correct I/O accessors
net: dsa: bcm_sf2: Use correct I/O accessors
net: systemport: Set correct RSB endian bits based on host
net: phy: mdio-bcm-unimac: Use correct I/O accessors
drivers/net/dsa/bcm_sf2.h | 12 +++++------
drivers/net/ethernet/broadcom/bcmsysport.c | 21 ++++++++++++--------
drivers/net/phy/mdio-bcm-unimac.c | 32 ++++++++++++++++++++++++------
3 files changed, 45 insertions(+), 20 deletions(-)
--
1.9.1
next reply other threads:[~2017-08-29 18:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 18:39 Florian Fainelli [this message]
2017-08-29 18:39 ` [PATCH net-next 1/4] net: systemport: Use correct I/O accessors Florian Fainelli
2017-08-29 18:39 ` [PATCH net-next 2/4] net: dsa: bcm_sf2: " Florian Fainelli
2017-08-29 18:39 ` [PATCH net-next 3/4] net: systemport: Set correct RSB endian bits based on host Florian Fainelli
2017-08-29 18:39 ` [PATCH net-next 4/4] net: phy: mdio-bcm-unimac: Use correct I/O accessors Florian Fainelli
2017-08-29 20:17 ` [PATCH net-next 0/4] Endian fixes for SYSTEMPORT/SF2/MDIO Florian Fainelli
2017-08-29 21:42 ` David Miller
2017-08-29 21:45 ` Florian Fainelli
2017-08-29 21:52 ` David Miller
2017-08-29 22:08 ` Florian Fainelli
2017-08-29 22:12 ` David Miller
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=1504031985-52808-1-git-send-email-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=opendmb@gmail.com \
--cc=vivien.didelot@savoirfairelinux.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;
as well as URLs for NNTP newsgroup(s).