public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: brendan.simon@bigpond.com
Cc: mtd <mtd@infradead.org>
Subject: Re: MTD: linux-2.4.0-test9 on a PowerPC board.
Date: Thu, 25 Jan 2001 08:54:39 +0000	[thread overview]
Message-ID: <8917.980412879@redhat.com> (raw)
In-Reply-To: <3A6E7687.9070200@bigpond.com>


brendan.simon@bigpond.com said:
>  Trying to debug things we have noticed that some of the data returned
>  has the bytes swapped.  It seems the NUM ERASE UNITS is returning
> 0xFA03  where as it should be returning 0x03FA.  It looks like an
> endian  problem.  Is the DOC code endian neutral ??  Will the endian
> problems be  rampant throughout the code or will it be confined to a
> few places ??

We don't actually seem to use NumEraseUnits, although I have absolutely no 
recollection _why_ not. But that would explain why we never bother to 
byteswap it. The code is intended to be endian-aware, although 
I've personally only tested it on LE machines, so I wouldn't swear that 
I've caught all cases. 

> Has anyone used a DOC on a PowerPC processor or other big endian
> architecture ?? 

It's been known, but I can't remember whether the person who asked me about 
it ever admitted to it in public. 

--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

      reply	other threads:[~2001-01-25  8:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-24  6:30 MTD: linux-2.4.0-test9 on a PowerPC board Brendan J Simon
2001-01-25  8:54 ` David Woodhouse [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=8917.980412879@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=brendan.simon@bigpond.com \
    --cc=mtd@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