From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Vaibhav Hiremath <hvaibhav@ti.com>,
"Hebbar, Gururaja" <gururaja.hebbar@ti.com>,
"alsa-user@lists.sourceforge.net"
<alsa-user@lists.sourceforge.net>, "Girdwood, Liam" <lrg@ti.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: How to handle parameter variation across different boards but same platform
Date: Thu, 5 Jul 2012 10:38:08 +0100 [thread overview]
Message-ID: <20120705093808.GJ4111@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201207050832.16750.arnd@arndb.de>
[-- Attachment #1.1: Type: text/plain, Size: 475 bytes --]
On Thu, Jul 05, 2012 at 08:32:16AM +0000, Arnd Bergmann wrote:
> On Thursday 05 July 2012, Vaibhav Hiremath wrote:
> > Does machine ID still gets set? May be I am missing something...
> No, it doesn't.
This is a *really* unfortunate decision, BTW - it means that if your
bootloader has a device tree available it needs to know if the kernel
it's booting is DT or non-DT which is just generally unhelpful. Sadly I
don't hold out much hope of being able to fix it, though.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2012-07-05 9:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 12:45 How to handle parameter variation across different boards but same platform Hebbar, Gururaja
2012-07-04 13:17 ` Mark Brown
2012-07-04 13:43 ` Hebbar, Gururaja
2012-07-04 14:01 ` Mark Brown
2012-07-04 14:17 ` Hebbar, Gururaja
2012-07-04 14:27 ` Mark Brown
[not found] ` <20120704142745.GC4111-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-07-05 5:42 ` Vaibhav Hiremath
2012-07-05 8:32 ` Arnd Bergmann
2012-07-05 9:38 ` Mark Brown [this message]
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=20120705093808.GJ4111@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-user@lists.sourceforge.net \
--cc=arnd@arndb.de \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=gururaja.hebbar@ti.com \
--cc=hvaibhav@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lrg@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox