All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Alessandro Rubini <rubini@gnudd.com>
Cc: linux-kernel@vger.kernel.org, giancarlo.asnaghi@st.com,
	alan@linux.intel.com, tglx@linutronix.de, mingo@redhat.com,
	sameo@linux.intel.com, x86@kernel.org
Subject: Re: [PATCH] x86/platform: sta2x11: add platform code
Date: Mon, 28 May 2012 23:43:15 -0700	[thread overview]
Message-ID: <4FC47003.1080906@zytor.com> (raw)
In-Reply-To: <20120529063738.GA22711@mail.gnudd.com>

On 05/28/2012 11:37 PM, Alessandro Rubini wrote:
>> There is absolutely NO WAY this kind of ARM-like sh*t is going into the
>> x86 kernel.
> 
> Ok. Then, how do you suggest to provide platform data to the various
> drivers?  It really depends on how the board is wired.
> 
> BTW: it's not uncommon for pci cards to differ in the same way, see
> drivers/media/video/bt8xx/bttv-cards.c for example.  I can have all
> board configurations without config choices or whatever is acceptable.
> Just tell me how to proceed.
> 

We have two mechanisms for parameterizing this kind of information: ACPI
5 (which can be considered the "native" method on x86) or flattened
device tree (as already used by the CE4100 platform.)  Keep in mind that
an explicit goal for Linux/x86 is that the same kernel should boot on
all platforms, and backsliding on that is not acceptable.

The best is for the firmware on your platforms to provide the ACPI or
DTB information, as it should.  If it doesn't, it gets nastier, but
there is absolutely no way we are going into the ARM swamp of having
different kernels for different boards.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2012-05-29  6:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-27 20:50 [PATCH] x86/platform: sta2x11: add platform code Alessandro Rubini
2012-05-28 23:38 ` H. Peter Anvin
2012-05-29  6:37   ` Alessandro Rubini
2012-05-29  6:43     ` H. Peter Anvin [this message]
2012-05-29  7:05       ` Alessandro Rubini
2012-05-29  7:15         ` H. Peter Anvin
2012-05-29  7:34           ` Alessandro Rubini
2012-05-29  7:39             ` H. Peter Anvin
2012-05-29  7:44               ` Alessandro Rubini
2012-06-04 10:16               ` Benjamin Herrenschmidt
2012-06-04 10:21                 ` Alessandro Rubini
2012-06-04 10:17         ` Benjamin Herrenschmidt

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=4FC47003.1080906@zytor.com \
    --to=hpa@zytor.com \
    --cc=alan@linux.intel.com \
    --cc=giancarlo.asnaghi@st.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rubini@gnudd.com \
    --cc=sameo@linux.intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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.