All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Daniel Mack <zonque@gmail.com>
Cc: "Gadiyar, Anand" <gadiyar@ti.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:22:22 +0300	[thread overview]
Message-ID: <20110621072220.GA21159@atomide.com> (raw)
In-Reply-To: <BANLkTimfeS1Xin779eg=8cdjqmqcQeB6HA@mail.gmail.com>

* Daniel Mack <zonque@gmail.com> [110617 18:06]:
> 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?

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

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Trouble with newer kernels on Gumstix Overo boards
Date: Tue, 21 Jun 2011 10:22:22 +0300	[thread overview]
Message-ID: <20110621072220.GA21159@atomide.com> (raw)
In-Reply-To: <BANLkTimfeS1Xin779eg=8cdjqmqcQeB6HA@mail.gmail.com>

* Daniel Mack <zonque@gmail.com> [110617 18:06]:
> 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?

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

  parent reply	other threads:[~2011-06-21  7:22 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
2011-06-21  8:21         ` Daniel Mack
2011-06-21  7:22     ` Tony Lindgren [this message]
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=20110621072220.GA21159@atomide.com \
    --to=tony@atomide.com \
    --cc=gadiyar@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=zonque@gmail.com \
    /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.