| 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
| ||
|
Message-ID: <1417405600-19232-3-git-send-email-suravee.suthikulpanit@amd.com> Date: Sun, 30 Nov 2014 21:46:40 -0600 From: <suravee.suthikulpanit@....com> To: <arnd@...db.de>, <mark.rutland@....com>, <will.deacon@....com>, <marc.zyngier@....com>, <catalin.marinas@....com> CC: <robherring2@...il.com>, <liviu.dudau@....com>, <linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>, <arm@...nel.org>, Suravee Suthikulpanit <Suravee.Suthikulpanit@....com> Subject: [PATCH 2/2] arm64: amd-seattle: Fix PCI bus range due to SMMU limitation From: Suravee Suthikulpanit <Suravee.Suthikulpanit@....com> Since PCIe is using SMMUv1 which only supports 15-bit stream ID, only 7-bit PCI bus id is used to specify stream ID. Therefore, we only limit the PCI bus range to 0x7f. Signed-off-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@....com> --- arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi b/arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi index f370f03..a6534c4 100644 --- a/arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi +++ b/arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi @@ -151,7 +151,7 @@ #size-cells = <2>; #interrupt-cells = <1>; device_type = "pci"; - bus-range = <0 0xff>; + bus-range = <0 0x7f>; msi-parent = <&v2m0>; reg = <0 0xf0000000 0 0x10000000>; -- 1.9.3 -- 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