Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754116AbaFJUwM (ORCPT ); Tue, 10 Jun 2014 16:52:12 -0400 Received: from mail-ve0-f178.google.com ([209.85.128.178]:62187 "EHLO mail-ve0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753038AbaFJUwJ (ORCPT ); Tue, 10 Jun 2014 16:52:09 -0400 MIME-Version: 1.0 In-Reply-To: References: <1397859600-11507-1-git-send-email-robherring2@gmail.com> <1397859600-11507-4-git-send-email-robherring2@gmail.com> <20140503220731.GA10927@kroah.com> <20140503221658.GA13403@kroah.com> Date: Tue, 10 Jun 2014 13:52:08 -0700 Message-ID: Subject: Re: [PATCH v2 3/7] tty/serial: convert 8250 to generic earlycon From: Tony Luck To: Rob Herring Cc: Greg Kroah-Hartman , Yinghai Lu , "linux-arm-kernel@lists.infradead.org" , Linux Kernel Mailing List , "linux-serial@vger.kernel.org" , Jiri Slaby , Catalin Marinas , Russell King , Will Deacon , Arnd Bergmann , Andrew Morton Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 9, 2014 at 4:18 PM, Rob Herring wrote: > It should do auto detect of the baud-rate if it is not specified which > for 8250 is just reading the baud-rate divider and calculating the > baud-rate using the uart clock. It should just reprogram the divider > with the same divider value. I don't see anything obvious why this > would have broken. Something very weird is happening. Output is good so long as I put the trailing ",115200" on the command line. But I made early_serial8250_setup() printk() the return value it got from probe_baud() - in case is was somehow getting 115201 or some other silly value ... nope. Exactly 115200. I also can't explain why the "noise" comes and goes a dozen times during boot, Does some other place in the kernel look at the "uart..." command line argument? -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/