On Sat, Oct 22, 2016 at 1:08 AM, Jason Ekstrand wrote:
> On Fri, Oct 21, 2016 at 10:58 PM, Dave Airlie wrote:
>>
>> On 22 Oct. 2016 15:51, "Jason Ekstrand" wrote:
>> >
>> > Wait... Why are we building the AMD driver on ARM? I know AMD has been
>> > talking about ARM-based servers, but are they
On Fri, Oct 21, 2016 at 10:58 PM, Dave Airlie wrote:
> On 22 Oct. 2016 15:51, "Jason Ekstrand" wrote:
> >
> > Wait... Why are we building the AMD driver on ARM? I know AMD has been
> talking about ARM-based servers, but are they actually strapping GPUs to
> them?
>
> PCIE on ARM somewhere.
>
I
On 22 Oct. 2016 15:51, "Jason Ekstrand" wrote:
>
> Wait... Why are we building the AMD driver on ARM? I know AMD has been
talking about ARM-based servers, but are they actually strapping GPUs to
them?
PCIE on ARM somewhere.
Dave.
>
> On Fri, Oct 21, 2016 at 1:16 AM, Nicolai Hähnle
wrote:
>>
>
Wait... Why are we building the AMD driver on ARM? I know AMD has been
talking about ARM-based servers, but are they actually strapping GPUs to
them?
On Fri, Oct 21, 2016 at 1:16 AM, Nicolai Hähnle wrote:
> On 21.10.2016 00:20, Rob Herring wrote:
>
>> The use of regparm causes an error on arm/a
On 21.10.2016 00:20, Rob Herring wrote:
The use of regparm causes an error on arm/arm64 builds with clang.
fastcall is allowed, but still throws a warning. As both options only
have effect on 32-bit x86 builds, limit them to that case.
While we haven't been particularly good at syncing things
The use of regparm causes an error on arm/arm64 builds with clang.
fastcall is allowed, but still throws a warning. As both options only
have effect on 32-bit x86 builds, limit them to that case.
Signed-off-by: Rob Herring
---
src/amd/addrlib/addrtypes.h | 10 +++---
1 file changed, 7 insert
