From: Jon Loeliger <jdl@jdl•com>
To: David Gibson <david@gibson•dropbear.id.au>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: dtc: Use the same endian-conversion functions as libfdt
Date: Mon, 14 Jul 2008 13:50:06 -0500 [thread overview]
Message-ID: <E1KIT7e-0006qR-PC@jdl.com> (raw)
In-Reply-To: <20080625042753.GC8284@yookeroo.seuss>
> Currently both libfdt and dtc define a set of endian conversion macros
> for accessing the device tree blob which is always big-endian. libfdt
> uses names like cpu_to_fdt32() and dtc uses names like cpu_to_be32 (as
> the Linux kernel). This patch switches dtc over to using the libfdt
> macros (including libfdt_env.h to supply them). This has a couple of
> small advantages:
> - Removes some code duplication
> - Will make conversion a bit easier if we ever need to produce
> little-endian device tree blobs.
> - dtc no longer needs to pull in netinet/in.h simply for the
> ntohs() and ntohl() functions
>
> Signed-off-by: David Gibson <david@gibson•dropbear.id.au>
Applied.
jdl
prev parent reply other threads:[~2008-07-14 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 4:27 dtc: Use the same endian-conversion functions as libfdt David Gibson
2008-07-14 18:50 ` Jon Loeliger [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=E1KIT7e-0006qR-PC@jdl.com \
--to=jdl@jdl$(echo .)com \
--cc=david@gibson$(echo .)dropbear.id.au \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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