From: David Woodhouse <dwmw2@infradead.org>
To: Alexandr Andreev <andreev@niisi.msk.ru>
Cc: linux-mtd@lists.infradead.org
Subject: Re: FTL and Endianity
Date: Fri, 06 Jul 2001 12:35:25 +0100 [thread overview]
Message-ID: <6473.994419325@redhat.com> (raw)
In-Reply-To: <3B4610D7.8040501@niisi.msk.ru>
andreev@niisi.msk.ru said:
> But when the ftl_fromat utility creates an ftl partition, it doesn't
> swap any field of the header. So, it doesn't matter on which endianity
> the FTL driver and ftl_format works, it must be the same only. Am i
> wrong?
You're right - except that it does matter in theory. The FTL spec is
defined as little-endian. So while it would _work_ if you do it all
backwards, it's technically wrong.
I'd be happier to fix ftl_format and ftl_check to do the byteswapping than
to remove same from ftl.c.
--
dwmw2
next prev parent reply other threads:[~2001-07-06 11:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-06 18:25 FTL and Endianity Alexandr Andreev
2001-07-06 10:30 ` David Woodhouse
2001-07-06 19:26 ` Alexandr Andreev
2001-07-06 11:35 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-06 12:52 Siders, Keith
2001-07-09 9:32 ` David Woodhouse
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=6473.994419325@redhat.com \
--to=dwmw2@infradead.org \
--cc=andreev@niisi.msk.ru \
--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