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: <4FC47D49.50204@zytor.com>
Date:	Tue, 29 May 2012 00:39:53 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Alessandro Rubini <rubini@...dd.com>
CC:	linux-kernel@...r.kernel.org, giancarlo.asnaghi@...com,
	alan@...ux.intel.com, tglx@...utronix.de, mingo@...hat.com,
	sameo@...ux.intel.com, x86@...nel.org, Len Brown <lenb@...nel.org>
Subject: Re: [PATCH] x86/platform: sta2x11: add platform code

On 05/29/2012 12:34 AM, Alessandro Rubini wrote:
> 
> So, it seems I must go device-tree for the chipset-like mounting. And
> what about plug in boards? I may arrange a firmware-loader mechanism
> as an alternative, so the vendor of each board can provide the the
> platform data for all the sub devices. Actually, if firmware loader is
> acceptable, I'd try it first, to avoid changing the boot procedure;
> maybe I can save myself from the device tree.
> 

If you're going to use a binary blob for the loader, use either ACPI 5
SSDT or device tree format.  This is *not* something where (re)invention
is encouraged.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
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