All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Prindeville <philipp_subx@redfish-solutions.com>
To: David Woodhouse <dwmw2@infradead.org>
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 14:56:18 -0700	[thread overview]
Message-ID: <4EEE6182.6070107@redfish-solutions.com> (raw)
In-Reply-To: <1324244805.2132.4.camel@shinybook.infradead.org>

On 12/18/11 2:46 PM, David Woodhouse wrote:
> 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?
>

Well, if we want to hold it up while someone adds device-tree support to x86... my understanding was it was PPC that used device-tree mostly at this point.

Until then, it's not clear that older platforms that are considered 'stable' are going to have new BIOS issued to their users going forward, or that any of the thousands of boards out there are going to be updated by their users.

Why not have support for existing boards that are out there?

Many of these boards are also produced by small engineering houses that aren't particularly quick to update their manufacturing processes to whatever the latest version of coreboot trunk is.

I agree that going forward, new boards coming out should support device-tree once it's stable and widely adopted, but let's not have the perfect become the enemy of the good.

-Philip

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-12-18 21:56 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
2011-12-18 21:56   ` Philip Prindeville [this message]
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=4EEE6182.6070107@redfish-solutions.com \
    --to=philipp_subx@redfish-solutions.com \
    --cc=akpm@linux-foundation.org \
    --cc=c-d.hailfinger.devel.2006@gmx.net \
    --cc=dilinger@queued.net \
    --cc=dwmw2@infradead.org \
    --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 \
    /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.