public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] FDT include file problems
Date: Sun, 19 Oct 2008 23:10:23 -0400	[thread overview]
Message-ID: <20081020031023.GA18173@cideas.com> (raw)
In-Reply-To: <20081019220159.CB9F8835697A@gemini.denx.de>

On Mon, Oct 20, 2008 at 12:01:59AM +0200, Wolfgang Denk wrote:
> Hello,
> 
> on some systems (for example Fedora Core 4) U-Boot builds with the
> following wanrings only:
> 
> ...
> In file included from /home/wd/git/u-boot/include/libfdt_env.h:33,
>                  from fdt.c:51:
> /usr/include/asm/byteorder.h:6:2: warning: #warning using private kernel header; include <endian.h> instead!

[snip]

> However, for the FDT code this doesn't help,  as  we  then  will  get
> unresolved    references    for    fdt32_to_cpu(),    cpu_to_fdt32(),
> fdt64_to_cpu() and cpu_to_fdt64().
> 
> The 32 bit accesses couldbe worked  around  by  using  htonl()  resp.
> ntohl(), but I don't know a good way for the 64 bit cases.
> 
> Is there a clean and portable way to do this?
> 
> Best regards,
> 
> Wolfgang Denk

Hi Wolfgang,

Does this work better?

Best regards,
gvb

  reply	other threads:[~2008-10-20  3:10 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 [this message]
2008-10-20  7:23   ` Wolfgang Denk
2008-10-20 10:17     ` Jerry Van Baren
2008-10-20 10:51       ` Wolfgang Denk
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=20081020031023.GA18173@cideas.com \
    --to=gvb.uboot@gmail.com \
    --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