public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH][RFC] bootm: Added CONFIG_BOOTM_{LINUX, NETBSD, RTEMS}
Date: Tue, 21 Oct 2008 15:46:09 -0400	[thread overview]
Message-ID: <48FE3181.3070402@ge.com> (raw)
In-Reply-To: <20081021194247.9418A835694E@gemini.denx.de>

Wolfgang Denk wrote:
> Dear Kumar Gala,
> 
> In message <4DE53147-6FF6-4145-AB35-68D124CD20F8@kernel.crashing.org> you wrote:
>>>> +#define CONFIG_BOOTM_LINUX 1
>>>> +#define CONFIG_BOOTM_NETBSD 1
>>>> +#define CONFIG_BOOTM_RTEMS 1
>>> The only somewhat reasonable thing I can come up with  is  to  add  a
>>> "#define  CONFIG_BOOTM_LINUX"  to  all  board  config  files,  so all
>>> support Linux by default, and leave it up to the board maintainers to
>>> add additioonal OS support if needed.
>>>
>>> Comment?
>> Hmm, can we hold off on this until we have Kconfig than?  It would be  
>> much easier at that point rather me having to touch ~450 config.h's.
> 
> OK from my POV. Should we check in your patch as is, then?
> 
> Best regards,
> 
> Wolfgang Denk

Ugly but effective work-around would be to put in an appropriate location:
/*
  * Todo: REMOVE when Kconfig becomes real!
  */
#ifndef CONFIG_BOOTM_LINUX
#define CONFIG_BOOTM_LINUX 1
#endif

Best regards,
gvb

  reply	other threads:[~2008-10-21 19:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20 16:39 [U-Boot] [PATCH][RFC] bootm: Added CONFIG_BOOTM_{LINUX, NETBSD, RTEMS} Kumar Gala
2008-10-21 19:35 ` Wolfgang Denk
2008-10-21 19:36   ` Kumar Gala
2008-10-21 19:42     ` Wolfgang Denk
2008-10-21 19:46       ` Jerry Van Baren [this message]
2008-10-21 19:50         ` Jerry Van Baren
2008-10-21 19:47       ` Kumar Gala
2008-10-21 21:01       ` Jean-Christophe PLAGNIOL-VILLARD
2009-09-09 12:55         ` [U-Boot] [PATCH] move default bootm config options to config_cmd_default.h Mike Frysinger
2009-09-09 13:06           ` Wolfgang Denk
2009-09-09 14:07             ` Mike Frysinger
2009-09-09 14:28               ` Wolfgang Denk
2009-09-09 15:34                 ` Mike Frysinger
2009-11-04 21:46                 ` [U-Boot] [PATCH 1/4] config_defaults.h: new header for common u-boot config defaults Mike Frysinger
2009-12-02 21:55                   ` Wolfgang Denk
2009-12-03  2:15                     ` [U-Boot] [PATCH 1/4 v2] " Mike Frysinger
2010-01-17 23:05                       ` Wolfgang Denk
2009-11-04 21:46                 ` [U-Boot] [PATCH 2/4] gzip/zlib: make features optional Mike Frysinger
2010-01-21 21:24                   ` Wolfgang Denk
2010-01-22  0:30                     ` [U-Boot] [PATCH v2] " Mike Frysinger
2010-01-25 23:05                       ` Wolfgang Denk
2009-11-04 21:46                 ` [U-Boot] [PATCH 3/4] sha1: add dedicated config option Mike Frysinger
2010-01-18  2:08                   ` [U-Boot] [PATCH 3/4 v2] " Mike Frysinger
2010-01-21 21:21                     ` Wolfgang Denk
2009-11-04 21:46                 ` [U-Boot] [PATCH 4/4] bootm: allow people to disable this command Mike Frysinger
2010-01-21 21:17                   ` Wolfgang Denk
2010-01-22  0:34                     ` Mike Frysinger
2010-01-22 11:59                       ` Wolfgang Denk
2008-10-21 19:47   ` [U-Boot] [PATCH][RFC] bootm: Added CONFIG_BOOTM_{LINUX, NETBSD, RTEMS} Mike Frysinger

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=48FE3181.3070402@ge.com \
    --to=gerald.vanbaren@ge.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