From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: lacie_kw: add support for WIRELESS_SPACE
Date: Fri, 5 Oct 2012 22:40:00 +0200 [thread overview]
Message-ID: <20121005224000.66331fe3@lilith> (raw)
In-Reply-To: <505DF78E.3080903@ti.com>
Hi Tom,
On Sat, 22 Sep 2012 10:38:22 -0700, Tom Rini <trini@TI.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 09/22/12 01:51, Albert ARIBAUD wrote:
> > Hi Simon,
> >
> > On Wed, 22 Aug 2012 17:16:21 +0200, Simon Guinot
> > <simon.guinot@sequanux.org> wrote:
> >
> >> On Tue, Aug 21, 2012 at 12:16:40AM -0700, Prafulla Wadaskar
> >> wrote:
> >>>
> >>>
> >>>> -----Original Message----- From: u-boot-bounces at lists.denx.de
> >>>> [mailto:u-boot- bounces at lists.denx.de] On Behalf Of Albert
> >>>> ARIBAUD Sent: 18 August 2012 02:59 To: Tom Rini Cc:
> >>>> u-boot at lists.denx.de Subject: Re: [U-Boot] [PATCH] ARM:
> >>>> lacie_kw: add support for WIRELESS_SPACE
> >>>>
> >>>> Hi Tom,
> >>>>
> >>>> On Fri, 17 Aug 2012 10:55:38 -0700, Tom Rini <trini@ti.com>
> >>>> wrote:
> >>>>
> >>>>> On Thu, Aug 16, 2012 at 08:08:34PM +0200, Albert ARIBAUD
> >>>>> wrote:
> >>>>>
> >>>>>> Signed-off-by: Albert ARIBAUD
> >>>>>> <albert.u.boot@aribaud.net>
> >>>>> [snip]
> >>>>>> @@ -90,8 +100,14 @@ #define CONFIG_SYS_IDE_MAXDEVICE
> >>>>>> 1 #if defined(CONFIG_NET2BIG_V2) #define
> >>>>>> CONFIG_SYS_PROMPT "2big2> " -#else +#elif
> >>>>>> defined(CONFIG_NETSPACE_V2) #define CONFIG_SYS_PROMPT
> >>>>>> "ns2> " +#elif defined(CONFIG_INETSPACE_V2) +#define
> >>>>>> CONFIG_SYS_PROMPT "is2> " +#elif
> >>>>>> defined(CONFIG_WIRELESS_SPACE) +#define CONFIG_SYS_PROMPT
> >>>>>> "ws> " +#else +#define CONFIG_SYS_PROMPT "lacie-kw> "
> >>>>>
> >>>>> Is this really a good thing? Over here I've been trying /
> >>>>> hoping to get everyone to just use 'U-Boot # ' as the
> >>>>> prompt as this makes automated testing easier and there's
> >>>>> other run-time ways to see what we're on.
> >>>
> >>> I personally vote to have common boot prompt 'U-boot #'.
> >>>
> >>>>
> >>>> I quite like prompts that identify the board I'm on, but it's
> >>>> not a must either. Cc:ing Simon in cas his own patches re
> >>>> lacie_kw would be impacted by your suggestion.
> >>>
> >>> Well, we can expose a command to detect/print the board info,
> >>> if needed.
> >>
> >> The run-time command "version" already returns both the system
> >> and the machine informations. This command can be used for
> >> testing purposes. IMHO the only requirement for an U-Boot prompt
> >> is to be short enough. Everything else is a matter of taste. Mine
> >> goes for the machine name.
> >>
> >> Regards,
> >>
> >> Simon
> >
> > Tom,
> >
> > Can automated test cope with a general prompt of the form '.*#' ?
>
> Sure, probably. It's really just something that popped into my head
> rather than a hard requirement or anything. It's also possible to
> just setup your testing framework to take the prompt as a variable, so
> this is just a personal preference thing.
Ok, then, prompts will stay as they are in the patch.
BTW, I took a look at prompts across the whole codebase... You get all
sorts. :)
Amicalement,
--
Albert.
next prev parent reply other threads:[~2012-10-05 20:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 18:08 [U-Boot] [PATCH] ARM: lacie_kw: add support for WIRELESS_SPACE Albert ARIBAUD
2012-08-17 7:59 ` Prafulla Wadaskar
2012-08-17 17:37 ` Albert ARIBAUD
2012-08-17 17:55 ` Tom Rini
2012-08-17 21:28 ` Albert ARIBAUD
2012-08-21 7:16 ` Prafulla Wadaskar
2012-08-22 15:16 ` Simon Guinot
2012-09-22 8:51 ` Albert ARIBAUD
2012-09-22 17:38 ` Tom Rini
2012-10-05 20:40 ` Albert ARIBAUD [this message]
2012-10-19 21:38 ` [U-Boot] [PATCH v2 1/2] mvgbe: allow non-sequential PHY addresses Albert ARIBAUD
2012-10-19 21:38 ` [U-Boot] [PATCH v2 2/2] ARM: lacie_kw: add support for WIRELESS_SPACE Albert ARIBAUD
2012-10-19 22:57 ` Albert ARIBAUD
2012-10-20 0:17 ` Simon Guinot
2012-10-27 12:11 ` Albert ARIBAUD
2012-10-19 23:57 ` [U-Boot] [PATCH v3 1/2] mvgbe: allow non-sequential PHY addresses Albert ARIBAUD
2012-10-19 23:57 ` [U-Boot] [PATCH v3 2/2] ARM: lacie_kw: add support for WIRELESS_SPACE Albert ARIBAUD
2012-11-04 23:32 ` [U-Boot] [PATCH v4 1/4] mvgbe: allow non-sequential PHY addresses Albert ARIBAUD
2012-11-04 23:32 ` [U-Boot] [PATCH v4 2/4] mv88e61xx: refactor PHY and SWITCH level-code Albert ARIBAUD
2012-11-04 23:32 ` [U-Boot] [PATCH v4 3/4] kirkwood: make MPP arrays static const Albert ARIBAUD
2012-11-04 23:32 ` [U-Boot] [PATCH v4 4/4] ARM: lacie_kw: add support for WIRELESS_SPACE Albert ARIBAUD
2012-11-10 7:09 ` Prafulla Wadaskar
2012-11-25 3:21 ` Albert ARIBAUD
2012-11-25 6:41 ` Prafulla Wadaskar
2012-11-10 7:02 ` [U-Boot] [PATCH v4 3/4] kirkwood: make MPP arrays static const Prafulla Wadaskar
2012-11-10 6:56 ` [U-Boot] [PATCH v4 2/4] mv88e61xx: refactor PHY and SWITCH level-code Prafulla Wadaskar
2012-11-10 6:41 ` [U-Boot] [PATCH v4 1/4] mvgbe: allow non-sequential PHY addresses Prafulla Wadaskar
2012-11-26 21:27 ` [U-Boot] [PATCH v5 0/3] Add support for the LaCie Wireless Space Albert ARIBAUD
2012-11-26 21:27 ` [U-Boot] [PATCH v5 1/3] mv88e61xx: refactor PHY and SWITCH level-code Albert ARIBAUD
2012-11-26 21:27 ` [U-Boot] [PATCH v5 2/3] kirkwood: make MPP arrays static const Albert ARIBAUD
2012-11-26 21:27 ` [U-Boot] [PATCH v5 3/3] ARM: lacie_kw: add support for WIRELESS_SPACE Albert ARIBAUD
2012-12-20 6:51 ` [U-Boot] [PATCH v5 0/3] Add support for the LaCie Wireless Space Prafulla Wadaskar
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=20121005224000.66331fe3@lilith \
--to=albert.u.boot@aribaud.net \
--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