lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTim6H3UCCsT1iAR2O=PL=5K4ypkT7UqcjqbAf3Vp@mail.gmail.com>
Date:	Tue, 15 Mar 2011 12:06:04 -0400
From:	Alex Deucher <alexdeucher@...il.com>
To:	Indan Zupancic <indan@....nu>
Cc:	Chris Wilson <chris@...is-wilson.co.uk>,
	intel-gfx@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
	dri-devel@...ts.freedesktop.org, Matthew Garrett <mjg@...hat.com>,
	Len Brown <lenb@...nel.org>, Alan Cox <alan@...ux.intel.com>
Subject: Re: [PATCH] ACPI/Intel: Rework Opregion support

On Tue, Mar 15, 2011 at 7:46 AM, Indan Zupancic <indan@....nu> wrote:
> 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.
>

They do give us fusion hw; before launch even.  That's why we had
Linux support before hw was available publicly.  My board just
happened to get bricked recently during a failed bios upgrade.  A new
one is on the way.  Also we are looking into a potential release of
UVD, but unfortunately, our decode hw is intimately tied in with our
drm implementation and if someone managed to use the released
information to compromise the drm in our windows driver it would very
negatively impact our ability to sell into the windows market and
would probably get the open source graphics initiative shut down.

Alex

> Greetings,
>
> Indan
>
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@...ts.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ