linux-kernel - Re: Memory and IO space Enabling different in x86 and ARM64

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: <7127812.WYSppNUyGc@wuerfel>
Date:	Fri, 15 Jul 2016 10:33:06 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	linux-arm-kernel@...ts.infradead.org
Cc:	Bharat Kumar Gogada <bharat.kumar.gogada@...inx.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	nofooter <nofooter@...inx.com>,
	"Liviu.Dudau@....com" <Liviu.Dudau@....com>
Subject: Re: Memory and IO space Enabling different in x86 and ARM64

On Friday, July 15, 2016 8:29:49 AM CEST Bharat Kumar Gogada wrote:
> I observe that memory and IO space are enabled by BIOS in x86.
> 
> In ARM64 we need to call pci_enable_device form End Point to enable these resources.
> 
> Why the resource enablement is different in x86 and ARM64 ?
> 
> Please correct me if my observation is wrong.

This is a difference between systems with a BIOS and embedded systems with
a plain bootloader that ignores PCI. On an ARM64 server system with UEFI
you should expect the device to be usable too, but on an embedded system,
Linux takes the role of the BIOS.

	Arnd