From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: Trouble with newer kernels on Gumstix Overo boards Date: Tue, 21 Jun 2011 10:22:22 +0300 Message-ID: <20110621072220.GA21159@atomide.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mho-03-ewr.mailhop.org ([204.13.248.66]:48271 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S932233Ab1FUHW3 (ORCPT ); Tue, 21 Jun 2011 03:22:29 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Daniel Mack Cc: "Gadiyar, Anand" , "linux-omap@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" * Daniel Mack [110617 18:06]: > On Fri, Jun 17, 2011 at 4:03 PM, Gadiyar, Anand wrote: > >> console=ttyS2,115200 root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait > > > > Here is your problem. We now use the OMAP-serial driver for the UARTs. > > Which breaks backward-compatibility with bootloaders set up for older > kernels. Now I have to deploy kernels with CONFIG_CMDLINE_FORCE=y. Was > that really necessary? In most cases you can just setenv cmdline then saveenv in u-boot. Who knows, maybe at some point we can make 8250.c behave with runtime PM and Linux generic DMA API, but that might take a while before we get there :) Regards, Tony From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Tue, 21 Jun 2011 10:22:22 +0300 Subject: Trouble with newer kernels on Gumstix Overo boards In-Reply-To: References: Message-ID: <20110621072220.GA21159@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Daniel Mack [110617 18:06]: > On Fri, Jun 17, 2011 at 4:03 PM, Gadiyar, Anand wrote: > >> console=ttyS2,115200 root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait > > > > Here is your problem. We now use the OMAP-serial driver for the UARTs. > > Which breaks backward-compatibility with bootloaders set up for older > kernels. Now I have to deploy kernels with CONFIG_CMDLINE_FORCE=y. Was > that really necessary? In most cases you can just setenv cmdline then saveenv in u-boot. Who knows, maybe at some point we can make 8250.c behave with runtime PM and Linux generic DMA API, but that might take a while before we get there :) Regards, Tony