linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: michael.weiser@gmx.de (Michael Weiser)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5 v3] Fixes for running a big-endian kernel on Cubieboard2
Date: Tue,  2 Aug 2016 21:31:10 +0200	[thread overview]
Message-ID: <20160802193115.850-1-michael.weiser@gmx.de> (raw)

Hello,

the following patches fix up endianness problems with DMA descriptors in the
sunxi-mmc and stmmac drivers preventing a big-endian kernel from working
correctly on the Cubieboard2.

The third patch adds the ability to enable diagnostic messages in the
sun4i-emac driver which were instrumental in finding the problem fixed by patch
number four: Endianness confusion caused by dual-purpose I/O register usage in
sun4i-emac.

The final patch enables the big-endian kernel configuration option for sunxi
devices in order to be able to compile a big-endian kernel for the Cubieboard2.
All of these have been tested successfull on a Cubieboard2 DualCard.

Changes since v2:
- Fixed typo in stmmac patch causing a build failure
- Added sun4i-emac patches

Changes since v1:
- Fixed checkpatch niggles
- Added respective Cc:s

Regards,
Michael

Signed-off-by: Michael Weiser <michael.weiser@gmx.de>
Cc: Maxime Ripard <maxime.ripard@free-electrons.com>

             reply	other threads:[~2016-08-02 19:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02 19:31 Michael Weiser [this message]
2016-08-02 19:31 ` [PATCH 1/5] mmc: sunxi-mmc: change idma descriptor to __le32 Michael Weiser
2016-08-22 13:38   ` Ulf Hansson
2016-08-02 19:31 ` [PATCH 2/5] net: ethernet: stmmac: change dma descriptors " Michael Weiser
2016-08-02 19:31 ` [PATCH 3/5] net: ethernet: sun4i-emac: Allow to enable netif messages Michael Weiser
2016-08-02 19:31 ` [PATCH 4/5] net: ethernet: sun4i-emac: Read rxhdr in CPU byte-order Michael Weiser
2016-08-02 19:31 ` [PATCH 5/5] ARM: sunxi: enable big-endian Michael Weiser
2016-08-22  7:57   ` Maxime Ripard

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=20160802193115.850-1-michael.weiser@gmx.de \
    --to=michael.weiser@gmx.de \
    --cc=linux-arm-kernel@lists.infradead.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 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).