From: Vladimir Pantelic <vladoman@gmail.com> To: Daniel Mack <zonque@gmail.com> Cc: 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>, "Gadiyar, Anand" <gadiyar@ti.com> Subject: Re: Trouble with newer kernels on Gumstix Overo boards Date: Wed, 22 Jun 2011 08:57:06 +0200 [thread overview] Message-ID: <4E019242.1050503@gmail.com> (raw) In-Reply-To: <BANLkTim5H3340RChbaVUOpSYb4tQr9X9YA@mail.gmail.com> Daniel Mack wrote: > Well, it doesn't really affect me as I just use this as a development > platform for now. But please consider that there is hardware out there > which gets software updates through automated download and install > procedures. In such cases, you want as little dependencies between the > bootloader and the kernel, so you can boot both older and newer If you want *minimal* dependency, then a compiled-in command line is the way to go and the bootloader only providing a few board identifying tags > kernels (and full software distribution images) with no pain. Or maybe > quickly switch from one version to the other for testing. Depending on > the complexity of the system, the bootloader might also add extra > parameters to the cmdline dynamically. AFAIK there is way to have the bootloader provided cmdline appended to the compiled-in one > The serial console change breaks this approach, at it forces the > kernel to ship its own CMDLINE and override the one the bootloader > provides. I'm sure this is a problem that affects people out there. FWIW, for our firmware update deployment it's not a problem at all, since we do *not* want to rely on a kernel commandline provided by the bootloader for the exact same reason. Kernels change and thus the kernel command line belongs to the kernel. What does not change is e.g. the board id or revision or mem size, that (and only that) is provided by the bootloader to the kernel.
WARNING: multiple messages have this Message-ID (diff)
From: vladoman@gmail.com (Vladimir Pantelic) To: linux-arm-kernel@lists.infradead.org Subject: Trouble with newer kernels on Gumstix Overo boards Date: Wed, 22 Jun 2011 08:57:06 +0200 [thread overview] Message-ID: <4E019242.1050503@gmail.com> (raw) In-Reply-To: <BANLkTim5H3340RChbaVUOpSYb4tQr9X9YA@mail.gmail.com> Daniel Mack wrote: > Well, it doesn't really affect me as I just use this as a development > platform for now. But please consider that there is hardware out there > which gets software updates through automated download and install > procedures. In such cases, you want as little dependencies between the > bootloader and the kernel, so you can boot both older and newer If you want *minimal* dependency, then a compiled-in command line is the way to go and the bootloader only providing a few board identifying tags > kernels (and full software distribution images) with no pain. Or maybe > quickly switch from one version to the other for testing. Depending on > the complexity of the system, the bootloader might also add extra > parameters to the cmdline dynamically. AFAIK there is way to have the bootloader provided cmdline appended to the compiled-in one > The serial console change breaks this approach, at it forces the > kernel to ship its own CMDLINE and override the one the bootloader > provides. I'm sure this is a problem that affects people out there. FWIW, for our firmware update deployment it's not a problem at all, since we do *not* want to rely on a kernel commandline provided by the bootloader for the exact same reason. Kernels change and thus the kernel command line belongs to the kernel. What does not change is e.g. the board id or revision or mem size, that (and only that) is provided by the bootloader to the kernel.
next prev parent reply other threads:[~2011-06-22 6:57 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 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 [this message] 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=4E019242.1050503@gmail.com \ --to=vladoman@gmail.com \ --cc=gadiyar@ti.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=tony@atomide.com \ --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: linkBe 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.