All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alessandro Rubini <rubini@gnudd.com>
To: benh@kernel.crashing.org
Cc: hpa@zytor.com, 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, lenb@kernel.org
Subject: Re: [PATCH] x86/platform: sta2x11: add platform code
Date: Mon, 4 Jun 2012 12:21:41 +0200	[thread overview]
Message-ID: <20120604102141.GA7967@mail.gnudd.com> (raw)
In-Reply-To: <1338804972.7150.77.camel@pasglop>

> Right, a device-tree blob could easily be passed an x86 has the
> infrastructure to use it already afaik.

Yes, that's the direction I'm aiming at.  I hope it's possibly to also
load a device sub-tree later (which is needed when the pci device is
a plug-in board instead of the main chipset in the motherboard.

> That or the ACPI way but I know nothing about it and thus naturally
> assume it's harder :-)

I'm studying this first, hoping to confirm my bad feeling about it and
be happier when working with fdt. Also, I'd better remain portable, in
case vendors will package the sta2x11 as a pci board -- the one I have is
just the development system and it's not largely marketed.

Thanks
/alessandro

  reply	other threads:[~2012-06-04 10:22 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
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 [this message]
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=20120604102141.GA7967@mail.gnudd.com \
    --to=rubini@gnudd.com \
    --cc=alan@linux.intel.com \
    --cc=benh@kernel.crashing.org \
    --cc=giancarlo.asnaghi@st.com \
    --cc=hpa@zytor.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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.