All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] RFA: libfdt: using missing type uintptr_t
Date: Tue, 19 Aug 2008 20:40:27 -0400	[thread overview]
Message-ID: <48AB67FB.8070007@gmail.com> (raw)

Hello all,  I have a Request For Advice.

I've pulled down the dtc/libfdt updates and applied them to my personal 
working git repository.  It turns out that David Gibson added a use of 
the typedef "uintptr_t" found in linux-land in /usr/include/stdint.h.

<http://thread.gmane.org/gmane.linux.ports.ppc64.devel/43379>

The problem is, currently u-boot doesn't have stdint.h.  It looks like 
we have three options:
1) Hack in the typedef for uintptr_t into "libfdt_env.h"
2) Add the linux stdint.h to u-boot
3) Find an alternative for uintptr_t and convince David and Jon that it 
is A Better Thing to use.

As I see it, #3 is extremely unlikely, especially since David is using 
uintptr_t for exactly the purpose for which it was created.  #1 is, 
well, a hack.  #2 (add linux' stdint.h to u-boot) seems like the best 
approach, but my initial try caused redefinitions between stdint.h and 
types.h as well as missing files:
   #include <features.h>
   #include <bits/wchar.h>
   #include <bits/wordsize.h>
Sigh.

At this point, adding stdint.h seems to be the best option.  Anybody 
have a better approach?

Thanks,
gvb

             reply	other threads:[~2008-08-20  0:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20  0:40 Jerry Van Baren [this message]
2008-08-20  1:11 ` [U-Boot] RFA: libfdt: using missing type uintptr_t David Gibson

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=48AB67FB.8070007@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.