[Qemu-devel] [PATCH] hw/arm/virt: bus-range/end is off by one

2015-02-12 Thread Laszlo Ersek
According to PCI Bus Binding to IEEE Std 1275-1994, 3.1.2. Bus-specific Properties for Bus Nodes, the second integer in bus-range is an inclusive limit. This seems to be consistent with several *.dtsi files in the kernel tree, where examples like bus-range = 0 0; are visible. In addition,

Re: [Qemu-devel] [PATCH] hw/arm/virt: bus-range/end is off by one

2015-02-12 Thread Wei Huang
On 02/12/2015 12:50 PM, Laszlo Ersek wrote: According to PCI Bus Binding to IEEE Std 1275-1994, 3.1.2. Bus-specific Properties for Bus Nodes, the second integer in bus-range is an inclusive limit. This seems to be consistent with several *.dtsi files in the kernel tree, where examples

Re: [Qemu-devel] [PATCH] hw/arm/virt: bus-range/end is off by one

2015-02-12 Thread Alexander Graf
On 12.02.15 19:50, Laszlo Ersek wrote: According to PCI Bus Binding to IEEE Std 1275-1994, 3.1.2. Bus-specific Properties for Bus Nodes, the second integer in bus-range is an inclusive limit. This seems to be consistent with several *.dtsi files in the kernel tree, where examples like

Re: [Qemu-devel] [PATCH] hw/arm/virt: bus-range/end is off by one

2015-02-12 Thread Peter Maydell
On 13 February 2015 at 01:12, Alexander Graf ag...@suse.de wrote: On 12.02.15 19:50, Laszlo Ersek wrote: According to PCI Bus Binding to IEEE Std 1275-1994, 3.1.2. Bus-specific Properties for Bus Nodes, the second integer in bus-range is an inclusive limit. This seems to be consistent with