From: David Vrabel <dvrabel@arcom.com>
To: jbowler@acm.org
Cc: linux-mtd@lists.infradead.org,
'Alessandro Zummo' <azummo-lists@towertech.it>
Subject: Re: ixp4xx stuff
Date: Mon, 14 Nov 2005 17:49:17 +0000 [thread overview]
Message-ID: <4378CE1D.4030605@arcom.com> (raw)
In-Reply-To: <006c01c5e939$ba996570$1001a8c0@kalmiopsis>
John Bowler wrote:
> From: David Vrabel
>
>>>along with the other NSLU2 patches. We found that it is now necessary to
>>>set CONFIG_MTD_LE_BYTE_SWAP - with the NSLU2 patches CONFIG_MTD_BE_BYTE_SWAP
>>>must be set. If this is not done (i.e. if BE is set) the flash probe fails.
>>
>>Neither of these options should be enabled. The flash data is returned
>>in the same order regardless of the endianness of the CPU.
>
>
> What is the difference between CONFIG_MTD_BE_BYTE_SWAP and ..._NO_SWAP on a
> BE machine?
They're both no-ops on BE CPUs.
To conclude: With CONFIG_MTD_NOSWAP set the current patches:
a) Work on BE systems as they have always done (tested by myself and
it's fairly obvious it's right since it doesn't do anything different).
b) Work on LE systems (as you have verified -- CONFIG_MTD_LE_BYTE_SWAP
is a no-op on LE CPUs).
So it looks like everything is good to go, yes?
David Vrabel
--
David Vrabel, Design Engineer
Arcom, Clifton Road Tel: +44 (0)1223 411200 ext. 3233
Cambridge CB1 7EA, UK Web: http://www.arcom.com/
next prev parent reply other threads:[~2005-11-14 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <436F94D0.5070509@arcom.com>
2005-11-14 6:50 ` ixp4xx stuff John Bowler
2005-11-14 10:14 ` David Vrabel
2005-11-14 16:37 ` John Bowler
2005-11-14 17:49 ` David Vrabel [this message]
2005-11-14 18:32 ` John Bowler
2005-11-14 21:20 ` [PATCH] [MTD] MAPS/ixp4xx.c: fix BE system break in 2.6.15-rc1, enable LE operation in 2.6.15 John Bowler
2005-11-16 16:35 ` David Vrabel
2005-11-19 18:17 ` John Bowler
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=4378CE1D.4030605@arcom.com \
--to=dvrabel@arcom.com \
--cc=azummo-lists@towertech.it \
--cc=jbowler@acm.org \
--cc=linux-mtd@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