dt [mailto:benh at kernel.crashing.org]
> Sent: Saturday, June 07, 2014 3:16 PM
> To: Dave Airlie
> Cc: dri-devel at lists.freedesktop.org; YC Chen
> Subject: Re: ast2400 woes
>
> On Sat, 2014-06-07 at 09:20 +1000, Benjamin Herrenschmidt wrote:
>
> > IE. Is there a r
. Chen
-Original Message-
From: Benjamin Herrenschmidt [mailto:b...@kernel.crashing.org]
Sent: Saturday, June 07, 2014 3:16 PM
To: Dave Airlie
Cc: dri-devel at lists.freedesktop.org; YC Chen
Subject: Re: ast2400 woes
On Sat, 2014-06-07 at 09:20 +1000, Benjamin Herrenschmidt wrote:
> IE. Is there
On Sat, 2014-06-07 at 09:20 +1000, Benjamin Herrenschmidt wrote:
> IE. Is there a reason why bASTIsVGAEnabled() and vASTEnableVGAMMIO
> use the IO ports ? The latter reads 0x43 and writes 0x43 and 0x42,
> can it be made to always use MMIO 0x3c3 and write 0x3c3 and 0x3c2 ?
>
> On my AST2400 at lea
On Fri, 2014-06-06 at 21:31 +1000, Benjamin Herrenschmidt wrote:
> The spec is pretty tricky to read but seems to indicate that the above
> offset should also work for PIO if needed, however, it seems like the
> X driver is pretty happy to use MMIO unconditionally for them.
>
> Any objection on m
Hi Dave !
So your AST KMS driver in -next is blowing up on my power8 box :-)
There are several issues that I want to discuss here (YC Chen on CC
might also have some valuable input here) before I send you patches
to fix it :-)
* First, accessors. The first obvious cause for blowing up for me is
Hi Dave !
So your AST driver in -next is blowing up on my power8 box :-)
There are several issues that I want to discuss here (YC Chen on CC
might also have some valuable input here).
* First, accessors. The first obvious cause for blowing up for me is
that you are using the "old style" PIO offs
