On Sun, 2016-07-03 at 21:12 +0200, Matthias Brugger wrote:
>
> On 07/03/2016 08:24 AM, Matthias Brugger wrote:
> >
> >
> > On 06/08/2016 11:51 AM, honghui.zh...@mediatek.com wrote:
> >> From: Honghui Zhang
> >>
> >> Add the dtsi node of iommu and smi for mt2701.
> >>
On 07/03/2016 08:24 AM, Matthias Brugger wrote:
On 06/08/2016 11:51 AM, honghui.zh...@mediatek.com wrote:
From: Honghui Zhang
Add the dtsi node of iommu and smi for mt2701.
Signed-off-by: Honghui Zhang
---
在 7/3/2016 8:59 AM, sunnydrake 写道:
[description]
working in kernel 3.9
Oops in current 4.4.0-28,4.7.0-040700rc5
kernel options ivrs_ioapic[7]=00:14.0 ivrs_ioapic[8]=00:00.1
workaround to fix ivrs table
cause kernel Oops on boot
Do you mean "ivrs_ioapic[7]=00:14.0 ivrs_ioapic[8]=00:00.1" are
On 29/06/16 08:07, Alex Williamson wrote:
> On Tue, 28 Jun 2016 23:37:06 +0200
> Heiner Kallweit wrote:
>
>> Am 28.06.2016 um 22:09 schrieb Alex Williamson:
>>> On Tue, 28 Jun 2016 20:40:37 +0200
>>> Heiner Kallweit wrote:
>>>
The init
Per VT-d spec Section 10.4.2 ("Capability Register"), the maximum
number of possible domains is 64K; indeed this is the maximum value
that the cap_ndoms() macro will expand to. Since the value 65536
will not fix in a u16, the 'did' variable must be promoted to an
int, otherwise the test for <
On Sat, Jul 02, 2016 at 09:23:24PM -0300, Aaron Campbell wrote:
> Per VT-d spec Section 10.4.2 ("Capability Register"), the maximum
> number of possible domains is 64K; indeed this is the maximum value
> that the cap_ndoms() macro will expand to.
Good catch. Before 3bd4f9112f87, the loop ended at
On 06/08/2016 11:51 AM, honghui.zh...@mediatek.com wrote:
From: Honghui Zhang
Add the dtsi node of iommu and smi for mt2701.
Signed-off-by: Honghui Zhang
---
arch/arm/boot/dts/mt2701.dtsi | 51