From: Daniel Mack <zonque@gmail.com>
To: yegor_sub1@visionsystems.de
Cc: "Gadiyar, Anand" <gadiyar@ti.com>,
Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Trouble with newer kernels on Gumstix Overo boards
Date: Tue, 21 Jun 2011 10:21:42 +0200 [thread overview]
Message-ID: <BANLkTim8Sh7kZp=92jhoU3NxgzAu0YgoWw@mail.gmail.com> (raw)
In-Reply-To: <4DFF4BCB.1000206@visionsystems.de>
On Mon, Jun 20, 2011 at 3:31 PM, Yegor Yefremov
<yegor_sub1@visionsystems.de> wrote:
> Am 17.06.2011 17:11, schrieb Daniel Mack:
>> On Fri, Jun 17, 2011 at 4:03 PM, Gadiyar, Anand <gadiyar@ti.com> 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
WARNING: multiple messages have this Message-ID (diff)
From: zonque@gmail.com (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: Trouble with newer kernels on Gumstix Overo boards
Date: Tue, 21 Jun 2011 10:21:42 +0200 [thread overview]
Message-ID: <BANLkTim8Sh7kZp=92jhoU3NxgzAu0YgoWw@mail.gmail.com> (raw)
In-Reply-To: <4DFF4BCB.1000206@visionsystems.de>
On Mon, Jun 20, 2011 at 3:31 PM, Yegor Yefremov
<yegor_sub1@visionsystems.de> wrote:
> Am 17.06.2011 17:11, schrieb Daniel Mack:
>> On Fri, Jun 17, 2011 at 4:03 PM, Gadiyar, Anand <gadiyar@ti.com> 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
next prev parent reply other threads:[~2011-06-21 8:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 14:00 Trouble with newer kernels on Gumstix Overo boards Daniel Mack
2011-06-17 14:00 ` Daniel Mack
2011-06-17 14:03 ` Gadiyar, Anand
2011-06-17 14:03 ` Gadiyar, Anand
2011-06-17 15:11 ` Daniel Mack
2011-06-17 15:11 ` Daniel Mack
2011-06-20 13:31 ` Yegor Yefremov
2011-06-20 13:31 ` Yegor Yefremov
2011-06-20 14:02 ` Premi, Sanjeev
2011-06-20 14:02 ` Premi, Sanjeev
2011-06-20 14:31 ` Yegor Yefremov
2011-06-20 14:31 ` Yegor Yefremov
2011-06-21 8:21 ` Daniel Mack [this message]
2011-06-21 8:21 ` Daniel Mack
2011-06-21 7:22 ` Tony Lindgren
2011-06-21 7:22 ` Tony Lindgren
2011-06-21 8:20 ` Daniel Mack
2011-06-21 8:20 ` Daniel Mack
2011-06-22 6:57 ` Vladimir Pantelic
2011-06-22 6:57 ` Vladimir Pantelic
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='BANLkTim8Sh7kZp=92jhoU3NxgzAu0YgoWw@mail.gmail.com' \
--to=zonque@gmail.com \
--cc=gadiyar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=yegor_sub1@visionsystems.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.