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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 28 May 2012 23:43:15 -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
Subject: Re: [PATCH] x86/platform: sta2x11: add platform code

On 05/28/2012 11:37 PM, Alessandro Rubini wrote:
>> There is absolutely NO WAY this kind of ARM-like sh*t is going into the
>> x86 kernel.
> 
> Ok. Then, how do you suggest to provide platform data to the various
> drivers?  It really depends on how the board is wired.
> 
> BTW: it's not uncommon for pci cards to differ in the same way, see
> drivers/media/video/bt8xx/bttv-cards.c for example.  I can have all
> board configurations without config choices or whatever is acceptable.
> Just tell me how to proceed.
> 

We have two mechanisms for parameterizing this kind of information: ACPI
5 (which can be considered the "native" method on x86) or flattened
device tree (as already used by the CE4100 platform.)  Keep in mind that
an explicit goal for Linux/x86 is that the same kernel should boot on
all platforms, and backsliding on that is not acceptable.

The best is for the firmware on your platforms to provide the ACPI or
DTB information, as it should.  If it doesn't, it gets nastier, but
there is absolutely no way we are going into the ARM swamp of having
different kernels for different boards.

	-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