From: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: Richard R?jfors
<richard.rojfors-gfIc91nka+FZroRs9YW3xA@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org
Subject: Re: [PATCH 0/1] misc: Add Tunnel creek In-Vehicle I2C loader driver
Date: Fri, 15 Oct 2010 13:10:43 +0100 [thread overview]
Message-ID: <20101015121042.GA27369@sirena.org.uk> (raw)
In-Reply-To: <20101015104902.1047c978-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
On Fri, Oct 15, 2010 at 10:49:02AM +0200, Jean Delvare wrote:
> As a matter of fact, I have been discussing this with Intel people
> recently:
> http://marc.info/?t=128683908500001&r=1&w=2
> It is pretty clear that Intel have added board config support to x86
> already, even though that change may not be public yet. So I can only
> encourage you to discuss this with Jacob Pan, Feng Tang and Alan Cox.
That stuff is very specific to the Moorestown CPUs and a new BIOS type
they have, the board_info part was posted on lkml about two weeks ago if
you search through the archives.
next prev parent reply other threads:[~2010-10-15 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 14:41 [PATCH 0/1] misc: Add Tunnel creek In-Vehicle I2C loader driver Richard Röjfors
2010-09-29 8:38 ` Richard Röjfors
[not found] ` <4CA2FB10.2020605-gfIc91nka+FZroRs9YW3xA@public.gmane.org>
2010-10-15 8:49 ` Jean Delvare
[not found] ` <20101015104902.1047c978-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2010-10-15 12:10 ` Mark Brown [this message]
[not found] ` <20101015121042.GA27369-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2010-10-15 12:21 ` Jean Delvare
[not found] ` <20101015142130.1cf14629-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2010-10-15 12:30 ` Mark Brown
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=20101015121042.GA27369@sirena.org.uk \
--to=broonie-yzvpicuk2aatku/dhu1wvuem+bqzidxxqq4iyu8u01e@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=richard.rojfors-gfIc91nka+FZroRs9YW3xA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).