On Mon, 2012-04-23 at 14:30 +0100, Alan Cox wrote:
>
> > fbdev objects once exposed to userspace or to fbcon, thanks to some
> > wonderful
> > API design way back, the mmaps on the fbdev device are direct to the VRAM
> > physical pages. Can't tear them down and move them into system RAM pages
> >
On Mon, 2012-04-23 at 14:30 +0100, Alan Cox wrote:
>
> > fbdev objects once exposed to userspace or to fbcon, thanks to some
> > wonderful
> > API design way back, the mmaps on the fbdev device are direct to the VRAM
> > physical pages. Can't tear them down and move them into system RAM pages
> >
> ends up in the in-VRAM object. I'll have to add defio support to make this
> work
> properly now that I think about it a bit more, but defio isn't a major
> amount of work.
Ok
> fbdev objects once exposed to userspace or to fbcon, thanks to some wonderful
> API design way back, the mmaps on th
On Mon, Apr 23, 2012 at 1:44 PM, Alan Cox wrote:
>> This driver has a slightly different design than other KMS drivers, but
>> future server chips will probably share similiar setup. As these GPUs
>> commonly
>> have low video RAM, it doesn't make sense to put the kms console in VRAM
>> always. T
> This driver has a slightly different design than other KMS drivers, but
> future server chips will probably share similiar setup. As these GPUs commonly
> have low video RAM, it doesn't make sense to put the kms console in VRAM
> always. This driver places the kms console into system RAM, and doe
> ends up in the in-VRAM object. I'll have to add defio support to make this
> work
> properly now that I think about it a bit more, but defio isn't a major
> amount of work.
Ok
> fbdev objects once exposed to userspace or to fbcon, thanks to some wonderful
> API design way back, the mmaps on th
On Mon, Apr 23, 2012 at 1:44 PM, Alan Cox wrote:
>> This driver has a slightly different design than other KMS drivers, but
>> future server chips will probably share similiar setup. As these GPUs
>> commonly
>> have low video RAM, it doesn't make sense to put the kms console in VRAM
>> always. T
> This driver has a slightly different design than other KMS drivers, but
> future server chips will probably share similiar setup. As these GPUs commonly
> have low video RAM, it doesn't make sense to put the kms console in VRAM
> always. This driver places the kms console into system RAM, and doe
From: Dave Airlie
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be use
