From: Ralf Baechle <ralf@linux-mips.org>
To: Sebastien Decourriere <sebtx452@gmail.com>
Cc: linux-mtd@lists.infradead.org, linux-mips@linux-mips.org
Subject: Re: [PATCH] mtd: maps: lantiq-flash: Check if the EBU endianness swap is enabled
Date: Tue, 24 Jan 2017 18:03:05 +0100 [thread overview]
Message-ID: <20170124170305.GA26937@linux-mips.org> (raw)
In-Reply-To: <1484904834-14980-1-git-send-email-sebtx452@gmail.com>
On Fri, Jan 20, 2017 at 10:33:54AM +0100, Sebastien Decourriere wrote:
> The purpose of this patch is to enable the software address endianness
> swapping only when the in SoC EBU endianness swapping is disabled.
> To perform this check, I look at Bit 30 of the EBU_CON_0 register.
> Actually, the driver expects that the in SoC swapping is disabled.
> This is the case with current bootloaders shuch as U-boot.
>
> This applies only to vr9 (xrx200) rev 1.2 and ar10 (xrx300).
>
> I have a router which uses a proprietary bootloader which keeps
> the in SoC swapping enabled. The SoC in this router is a vrx200 v1.2.
> In this SoC version, I can keep the in SoC swapping without any problem.
>
> This patch replaces my previous broken patch.
>
> Signed-off-by: Sebastien Decourriere <sebtx452@gmail.com>
> .../mips/include/asm/mach-lantiq/xway/lantiq_soc.h | 1 +
> drivers/mtd/maps/lantiq-flash.c | 29 +++++++++++++++++++---
Acked-by: Ralf Baechle <ralf@linux-mips.org>
for the trivial MIPS bit.
Ralf
next prev parent reply other threads:[~2017-01-24 17:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 9:33 [PATCH] mtd: maps: lantiq-flash: Check if the EBU endianness swap is enabled Sebastien Decourriere
2017-01-24 17:03 ` Ralf Baechle [this message]
2017-01-24 21:32 ` Hauke Mehrtens
2017-01-25 9:04 ` Seb
2017-01-25 16:58 ` Langer, Thomas
2017-01-26 11:02 ` Seb
2017-01-26 16:01 ` Langer, Thomas
-- strict thread matches above, loose matches on Subject: below --
2017-01-19 10:06 Sebastien Decourriere
2017-01-19 23:50 ` Langer, Thomas
2017-01-18 12:10 Sebastien Decourriere
2017-01-18 12:38 ` John Crispin
2017-01-18 13:48 ` Seb
2017-01-18 13:51 ` John Crispin
2017-01-18 17:12 ` Seb
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=20170124170305.GA26937@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mtd@lists.infradead.org \
--cc=sebtx452@gmail.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).