From: David Woodhouse <dwmw2@infradead.org>
To: Philip Prindeville <philipp_subx@redfish-solutions.com>
Cc: Ed Wildgoose <ed@wildgooses.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-geode@lists.infradead.org,
Andres Salomon <dilinger@queued.net>,
Nathan Williams <nathan@traverse.com.au>,
Guy Ellis <guy@traverse.com.au>,
Patrick Georgi <patrick.georgi@secunet.com>,
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>,
linux-mm@kvack.org
Subject: Re: [PATCH 2/4] coreboot: Add support for detecting Coreboot BIOS signatures
Date: Sun, 18 Dec 2011 21:46:45 +0000 [thread overview]
Message-ID: <1324244805.2132.4.camel@shinybook.infradead.org> (raw)
In-Reply-To: <1324241211-7651-1-git-send-email-philipp_subx@redfish-solutions.com>
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
On Sun, 2011-12-18 at 13:46 -0700, Philip Prindeville wrote:
> Add support for Coreboot BIOS detection. This in turn can be used by
> platform drivers to verify they are running on the correct hardware,
> as many of the low-volume SBC's (especially in the Atom and Geode
> universe) don't always identify themselves via DMI or PCI-ID.
It's Coreboot. So doesn't that mean we can just fix it to pass a
device-tree to the kernel properly?
Don't we only need this kind of hack for boards with crappy
closed-source firmware?
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5818 bytes --]
next prev parent reply other threads:[~2011-12-18 21:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-18 20:46 [PATCH 2/4] coreboot: Add support for detecting Coreboot BIOS signatures Philip Prindeville
2011-12-18 21:46 ` David Woodhouse [this message]
2011-12-18 21:56 ` Philip Prindeville
2011-12-19 21:10 ` Philip Prindeville
2011-12-21 17:32 ` Jordan Crouse
-- strict thread matches above, loose matches on Subject: below --
2011-12-28 19:42 Philip Prindeville
2011-12-18 19:23 Philip Prindeville
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=1324244805.2132.4.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=c-d.hailfinger.devel.2006@gmx.net \
--cc=dilinger@queued.net \
--cc=ed@wildgooses.com \
--cc=guy@traverse.com.au \
--cc=linux-geode@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=nathan@traverse.com.au \
--cc=patrick.georgi@secunet.com \
--cc=philipp_subx@redfish-solutions.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 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.