mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Indan Zupancic" <indan@nul.nu>
To: "Indan Zupancic" <indan@nul.nu>,
	"Chris Wilson" <chris@chris-wilson.co.uk>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	"Matthew Garrett" <mjg@redhat.com>, "Len Brown" <lenb@kernel.org>,
	"Alan Cox" <alan@linux.intel.com>
Subject: Re: [PATCH] ACPI/Intel: Rework Opregion support
Date: Tue, 15 Mar 2011 12:46:29 +0100 (CET)	[thread overview]
Message-ID: <24fd59c964cf67c5ec048caa512afcd6.squirrel@webmail.greenhost.nl> (raw)
In-Reply-To: <20110315112724.6729.qmail@stuge.se>

On Tue, March 15, 2011 12:27, Peter Stuge wrote:
> coreboot has existed for about eleven years and some 250 mainboards of
> varying shapes and sizes (from laptop to server) are supported, but it's

I've been wanting to get rid of BIOSes and use Coreboot for ages,
but the amount of hassle needed to get it working for my hardware
and the lack of features (suspend), as well the chance of bricking
the system always put me off.

> only just recently that things are really taking off, with the code
> release from AMD to initialize their most recent Fusion platform.

They don't give their Linux devs any Fusion hardware, nor do they
open the UVD spec, but at least they release info like this.

Greetings,

Indan



  reply	other threads:[~2011-03-15 11:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-22 20:03 [PATCH 1/2] " Matthew Garrett
2011-02-22 20:03 ` [PATCH 2/2] staging: Use generic IGD opregion code for gma500 Matthew Garrett
2011-02-22 21:15   ` Alan Cox
2011-03-03  2:14   ` Len Brown
2011-03-03  2:16     ` Len Brown
2011-03-03 11:43       ` Alan Cox
2011-03-03 11:43     ` Alan Cox
2011-03-03 13:07       ` Matthew Garrett
2011-03-03 12:52         ` Alan Cox
2011-02-22 20:18 ` [Intel-gfx] [PATCH 1/2] ACPI/Intel: Rework Opregion support Jesse Barnes
2011-03-03  2:14 ` Len Brown
2011-03-14 17:59 ` [PATCH] " Chris Wilson
2011-03-15  1:18   ` Indan Zupancic
2011-03-15  1:52     ` Matthew Garrett
2011-03-15 13:30       ` [Intel-gfx] " Olivier Galibert
2011-03-15 13:32         ` Matthew Garrett
2011-03-15 13:40           ` Olivier Galibert
2011-03-15 13:43             ` Matthew Garrett
2011-03-15  8:37     ` Chris Wilson
2011-03-15 11:13       ` Indan Zupancic
2011-03-15 11:27         ` Peter Stuge
2011-03-15 11:46           ` Indan Zupancic [this message]
2011-03-15 16:06             ` Alex Deucher
2011-03-16  0:02               ` Indan Zupancic
2011-03-16  2:17                 ` Alex Deucher
2011-03-16  6:26                   ` Indan Zupancic
2011-03-16 14:11                     ` Jerome Glisse
2011-03-16  3:46       ` Dave Airlie

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=24fd59c964cf67c5ec048caa512afcd6.squirrel@webmail.greenhost.nl \
    --to=indan@nul.nu \
    --cc=alan@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®