From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Fri, 27 Apr 2012 09:47:52 -0700 Subject: [U-Boot] [PATCH v2 1/2] CONFIG_SYS_BAUDRATE_TABLE: Add , place there In-Reply-To: <20120427161749.9E092200244@gemini.denx.de> References: <1335480396-29478-1-git-send-email-trini@ti.com> <20120427063137.077F6200244@gemini.denx.de> <4F9AB2EE.3070202@ti.com> <20120427161749.9E092200244@gemini.denx.de> Message-ID: <4F9ACDB8.8000705@ti.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 04/27/2012 09:17 AM, Wolfgang Denk wrote: > Dear Tom Rini, > > In message<4F9AB2EE.3070202@ti.com> you wrote: >> >>> Argh... But you cannot change this without explicit ACK from the >>> respective board maintainers. >> >> 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 4800/9600/19200/38400/115200 (and reversed) and leave the rest alone. And then I'll drop it from the boards I own :) >>> Finally, your patch does not apply (I guess it is an incremental patch >>> over obsolete code?). >> >> That's odd actually, it was on v2012.04'ish and a pull and rebase -q >> went quietly. It was build-tested on MAKEALL -a powerpc/arm/x86. > > But you see the problem in the patch, don't you? With it not applying? No... -- Tom