From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] FDT include file problems
Date: Mon, 20 Oct 2008 12:51:31 +0200 [thread overview]
Message-ID: <20081020105131.E583E835697A@gemini.denx.de> (raw)
In-Reply-To: <48FC5AB3.10302@gmail.com>
Dear Jerry Van Baren,
In message <48FC5AB3.10302@gmail.com> you wrote:
>
> ...and if I were not rushing so much, I would have found that myself
> instead of looking stupid. :-(
>
> Google hasn't been very helpful for answering the question of how to
> handle endian issues in userland (non-kernel) code. Hmmm. Grrr. Maybe
> I'm not asking it the right question.
Well, I have to admit that you did not perform better, because I've
been searching before, and I didn't find a good solution myself
either. Normally, I use the network macros for such stuff, but these
don't have any 64 bit conversions...
> Maybe we need to make our own copy of linux/byteorder/swab.h in u-boot?
> That doesn't seem right.
No, that would not be right.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Real programmers can write assembly code in any language. :-)
- Larry Wall in <8571@jpl-devvax.JPL.NASA.GOV>
next prev parent reply other threads:[~2008-10-20 10:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 22:01 [U-Boot] FDT include file problems Wolfgang Denk
2008-10-20 3:10 ` Jerry Van Baren
2008-10-20 7:23 ` Wolfgang Denk
2008-10-20 10:17 ` Jerry Van Baren
2008-10-20 10:51 ` Wolfgang Denk [this message]
2008-10-20 11:08 ` Wolfgang Denk
2008-10-20 23:43 ` Jerry Van Baren
2008-10-21 9:24 ` Wolfgang Denk
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=20081020105131.E583E835697A@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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