From: Alexandr Andreev <andreev@niisi.msk.ru>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "linux-mtd@lists.infrared.org" <linux-mtd@lists.infradead.org>
Subject: Re: FTL and Endianity
Date: Fri, 06 Jul 2001 15:26:15 -0400 [thread overview]
Message-ID: <3B4610D7.8040501@niisi.msk.ru> (raw)
In-Reply-To: 31888.994415407@redhat.com
David Woodhouse wrote:
>
>I didn't test - I think others did though. FTL is defined to be
>little-endian. Why do you say the macros are unusable?
>
As i can see, cpu_to_le32 and others macros, are usable only when FTL
reading the FTL header. 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?
next prev parent reply other threads:[~2001-07-06 11:23 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 [this message]
2001-07-06 11:35 ` David Woodhouse
-- 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=3B4610D7.8040501@niisi.msk.ru \
--to=andreev@niisi.msk.ru \
--cc=dwmw2@infradead.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