mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: any value in allowing user selection of barebox prompt?
Date: Mon, 6 Feb 2012 10:57:22 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1202061041330.5018@oneiric> (raw)


  making things a bit simpler than my last few posts, is it worth
making the BOARDINFO prompt string user selectable?  if i was going to
do some customization, it would be nice to have the prompt perhaps
abbreviate what i'd done.

  for instance, if i:

$ make omap3530_beagle_defconfig

i can see how my barebox prompt string is going to be set in
arch/arm/mach-omap/Kconfig:

config BOARDINFO
        default "Texas Instrument's SDP343x" if MACH_OMAP343xSDP
        default "Texas Instrument's Beagle" if MACH_BEAGLE
        default "Texas Instrument's OMAP3EVM" if MACH_OMAP3EVM
        default "Texas Instrument's Panda" if MACH_PANDA
        default "Phytec phyCORE pcm049" if MACH_PCM049
        default "Phytec phyCARD-A-L1" if MACH_PCAAL1

  but if i specifically configure and build for an xM, i'd like the
prompt to perhaps read:

  barebox@Texas Instrument's Beagle xM:/

it's easy enough to do (although it would need to be done on a
per-machine basis):

config BOARDINFO
        string "Board info"
        default "Texas Instrument's SDP343x" if MACH_OMAP343xSDP
        default "Texas Instrument's Beagle" if MACH_BEAGLE
        default "Texas Instrument's OMAP3EVM" if MACH_OMAP3EVM
        default "Texas Instrument's Panda" if MACH_PANDA
        default "Phytec phyCORE pcm049" if MACH_PCM049
        default "Phytec phyCARD-A-L1" if MACH_PCAAL1

  i tried it and it seems to work fine although the aesthetics in
"make menuconfig" is a bit strange WRT order:

    (Texas Instrument's Beagle) Board info
        Select OMAP board (Texas Instrument's Beagle Board)  --->

but that could be fixed just by moving the BOARDINFO entry below the
board choice in that file.

  was this already discussed and rejected once upon a time?  it's not
a big deal but it has the value of being moderately informative.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2012-02-06 15:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 15:57 Robert P. J. Day [this message]
2012-02-07  9:33 ` Sascha Hauer
2012-02-07 11:13   ` Robert P. J. Day
2012-02-07 11:56     ` Jean-Christophe PLAGNIOL-VILLARD

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=alpine.DEB.2.02.1202061041330.5018@oneiric \
    --to=rpjday@crashcourse.ca \
    --cc=barebox@lists.infradead.org \
    /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