From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/2] CONFIG_SYS_BAUDRATE_TABLE: Add <config_fallbacks.h>, place there
Date: Fri, 27 Apr 2012 10:31:02 -0700 [thread overview]
Message-ID: <4F9AD7D6.4050202@ti.com> (raw)
In-Reply-To: <20120427171925.EAEC120627D@gemini.denx.de>
On 04/27/2012 10:19 AM, Wolfgang Denk wrote:
> Dear Tom,
>
> In message<4F9ACDB8.8000705@ti.com> you wrote:
>>
>>>> Then we're really SOL here. Even if we limit it to "I dropped
>>>> 300/600/900/1200/2400/4800 baud rate support, is that ok".
>>>
>>> What's wrong with keeping a customizes #define for the boards that use
>>> nonstandard settings?
>>
>> As I said in the commit message, I believe it was done for completeness
>> rather than need, but if you like I can change it to just delete
>
> As long as we don't know it exactly and for sure, we should not change
> the configuration of boards that don't belong to us (unless the changes
> are obviously harmless or clear bug fixes).
Alright, I'll drop those boards then.
>> 4800/9600/19200/38400/115200 (and reversed) and leave the rest alone.
>> And then I'll drop it from the boards I own :)
>
> OK.
>
>>> But you see the problem in the patch, don't you?
>>
>> With it not applying? No...
>
> Well, your patch reads for example:
>
> diff --git a/include/configs/AP1000.h b/include/configs/AP1000.h
> index b598371..fd074fb 100644
> --- a/include/configs/AP1000.h
> +++ b/include/configs/AP1000.h
> @@ -142,7 +142,6 @@
> #define CONFIG_SYS_INIT_CHAN2 0
>
> /* The following table includes the supported baudrates */
> -#undef CONFIG_SYS_BAUDRATE_TABLE
> #define CONFIG_SYS_BAUDRATE_TABLE \
> {300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200, 230400}
guh.. I'll go kick git some then.
--
Tom
next prev parent reply other threads:[~2012-04-27 17:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 22:46 [U-Boot] [PATCH v2 1/2] CONFIG_SYS_BAUDRATE_TABLE: Add <config_fallbacks.h>, place there Tom Rini
2012-04-26 22:46 ` [U-Boot] [PATCH v2 2/2] hush.c: Move default CONFIG_SYS_PROMPT_HUSH_PS2 to hush.c Tom Rini
2012-04-27 5:35 ` Mike Frysinger
2012-04-29 15:13 ` Stefano Babic
2012-04-26 23:53 ` [U-Boot] [PATCH v2 1/2] CONFIG_SYS_BAUDRATE_TABLE: Add <config_fallbacks.h>, place there Tom Rini
2012-04-27 5:34 ` Mike Frysinger
2012-04-27 14:31 ` Tom Rini
2012-04-27 6:31 ` Wolfgang Denk
2012-04-27 14:53 ` Tom Rini
2012-04-27 16:17 ` Wolfgang Denk
2012-04-27 16:47 ` Tom Rini
2012-04-27 17:19 ` Wolfgang Denk
2012-04-27 17:31 ` Tom Rini [this message]
2012-04-27 18:03 ` Tom Rini
2012-04-27 18:37 ` Mike Frysinger
2012-04-27 18:40 ` Wolfgang Denk
2012-04-27 19:02 ` Tom Rini
2012-06-19 20:50 ` Wolfgang Denk
2012-06-19 21:31 ` Tom Rini
2012-06-20 14:52 ` Tom Rini
2012-06-19 22:54 ` [U-Boot] [PATCH v4 " Tom Rini
2012-06-19 22:54 ` [U-Boot] [PATCH v4 2/2] hush.c: Move default CONFIG_SYS_PROMPT_HUSH_PS2 to hush.c Tom Rini
2012-06-20 9:14 ` Stefano Babic
2012-06-20 18:36 ` Wolfgang Denk
2012-06-20 18:36 ` [U-Boot] [PATCH v4 1/2] CONFIG_SYS_BAUDRATE_TABLE: Add <config_fallbacks.h>, place there 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=4F9AD7D6.4050202@ti.com \
--to=trini@ti.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