public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Testing todays u-boot-fdt
Date: Fri, 20 Apr 2007 13:11:13 -0400	[thread overview]
Message-ID: <4628F431.1020901@smiths-aerospace.com> (raw)
In-Reply-To: <4628EBFB.60802@grandegger.com>

Wolfgang Grandegger wrote:
> Hi Jerry,
> 
> Jerry Van Baren wrote:
> [...]
>> Hi wd,

[snip]

> 
> In U-Boot, it's common practice to use "ugly" ifdef's in the source 
> files mainly to reduce compile time as shown in the attached patch.
> 
> Wolfgang.
> 
> ------------------------------------------------------------------------
> 
> diff --git a/libfdt/fdt.c b/libfdt/fdt.c
> index 212b838..1ee67ad 100644
> --- a/libfdt/fdt.c
> +++ b/libfdt/fdt.c
> @@ -16,6 +16,9 @@
>   * License along with this library; if not, write to the Free Software
>   * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
>   */
> +#include "config.h"
> +#if CONFIG_OF_LIBFDT
> +
>  #include "libfdt_env.h"
>  
>  #include <fdt.h>
> @@ -83,3 +86,5 @@ int fdt_move(const void *fdt, void *buf, int bufsize)
>  	memmove(buf, fdt, fdt_totalsize(fdt));
>  	return 0;
>  }
> +
> +#endif /* CONFIG_OF_LIBFDT */

[snip more of the same]

Hi Wolfgang,

At this point I'm reluctant to do this.  We've basically forked libfdt 
in that I've added and changed the source and David Gibson isn't in a 
position to accept the changes back into the original, but it is all 
generically useful libfdt code.

Adding the above to all of the files makes it that much more u-boot 
specific which will make it that much more difficult to unfork.  On the 
other hand, it is "only" three lines per file.

Anyone care to weigh in on the issue?  wd?

Best regards,
gvb

  reply	other threads:[~2007-04-20 17:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-19  8:58 [U-Boot-Users] Testing todays u-boot-fdt Wolfgang Grandegger
2007-04-19 12:08 ` Jerry Van Baren
2007-04-19 13:10   ` Wolfgang Grandegger
2007-04-19 13:19     ` Jerry Van Baren
2007-04-19 15:24   ` Timur Tabi
2007-04-22 20:38   ` Timur Tabi
2007-04-23  0:05     ` Jerry Van Baren
2007-04-19 13:28 ` Jerry Van Baren
2007-04-19 13:42   ` Wolfgang Grandegger
2007-04-19 15:51   ` Wolfgang Denk
2007-04-19 23:11     ` Jerry Van Baren
2007-04-19 23:19       ` Wolfgang Denk
2007-04-20 16:36       ` Wolfgang Grandegger
2007-04-20 17:11         ` Jerry Van Baren [this message]
2007-04-20 20:40           ` Wolfgang Denk
2007-04-20 22:02             ` Jerry Van Baren
2007-04-20  3:38 ` Jerry Van Baren
2007-04-20 13:32   ` Wolfgang Denk
2007-04-20  3:40 ` Jerry Van Baren
     [not found] <4629358C.5050401@cideas.com>
2007-04-20 23:01 ` 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=4628F431.1020901@smiths-aerospace.com \
    --to=gerald.vanbaren@smiths-aerospace.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