From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Mack Subject: Re: Trouble with newer kernels on Gumstix Overo boards Date: Tue, 21 Jun 2011 10:21:42 +0200 Message-ID: References: <4DFF4BCB.1000206@visionsystems.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from mail-pw0-f46.google.com ([209.85.160.46]:61429 "EHLO mail-pw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751344Ab1FUIVn (ORCPT ); Tue, 21 Jun 2011 04:21:43 -0400 Received: by pwj7 with SMTP id 7so856097pwj.19 for ; Tue, 21 Jun 2011 01:21:42 -0700 (PDT) In-Reply-To: <4DFF4BCB.1000206@visionsystems.de> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: yegor_sub1@visionsystems.de Cc: "Gadiyar, Anand" , Tony Lindgren , "linux-omap@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" On Mon, Jun 20, 2011 at 3:31 PM, Yegor Yefremov wrote: > Am 17.06.2011 17:11, schrieb Daniel Mack: >> 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? >> >>> Change the ttyS2 to ttyO2 and you should be fine. >> >> You're right, that did the trick. Thanks a lot! > > Are you using some extra patches? I have a custom board based on am3517 SoC and I have much more errors during booting as I can see from your boot log. I have no problems booting 2.6.32/37 though. Any idea? I don't use any extra patches. Just a plain 3.0.0-rc3 from Linus' master branch plus the patch I've sent some days ago to this list. With that setup, and console=ttyO2, my systems runs just fine. Daniel From mboxrd@z Thu Jan 1 00:00:00 1970 From: zonque@gmail.com (Daniel Mack) Date: Tue, 21 Jun 2011 10:21:42 +0200 Subject: Trouble with newer kernels on Gumstix Overo boards In-Reply-To: <4DFF4BCB.1000206@visionsystems.de> References: <4DFF4BCB.1000206@visionsystems.de> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, Jun 20, 2011 at 3:31 PM, Yegor Yefremov wrote: > Am 17.06.2011 17:11, schrieb Daniel Mack: >> 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? >> >>> Change the ttyS2 to ttyO2 and you should be fine. >> >> You're right, that did the trick. Thanks a lot! > > Are you using some extra patches? I have a custom board based on am3517 SoC and I have much more errors during booting as I can see from your boot log. I have no problems booting 2.6.32/37 though. Any idea? I don't use any extra patches. Just a plain 3.0.0-rc3 from Linus' master branch plus the patch I've sent some days ago to this list. With that setup, and console=ttyO2, my systems runs just fine. Daniel