Hi Daniel,
we've considered making cursor a plane but haven't done so (yet) because
cursor is sort of a unique concept in our HW and doesn't map well to planes.
Will take the time to look at the other mappings a bit more closely.
Cheers,
Harry
On 2016-02-14 09:01 AM, Daniel Vetter wrote:
>
Hi Jerome,
some of the kernel API is abstracted to allow testing of this driver in
user space for pre- and post-silicon validation. An alternative that
we've considered is implementing the kernel functions in user space.
That's definitely an option.
We're definitely open to push things into
Hi Rob,
thanks for the heads-up for this. We're definitely interested in
contributing to proposed new frameworks.
I'm not sure we want to tightly couple userspace with hardware, though.
Your proposal seems to assume that user mode is responsible for knowing
how many planes any given
Hi Harry,
On 13 February 2016 at 00:05, Wentland, Harry wrote:
> The goal with DAL is to provide a unified, full featured display stack to
> service all of our Linux offerings. This driver will have to support our full
> feature set beyond what's supported by amdgpu, e.g.
> - synchronzied
top-level post since I can't reply to the diagram directly. So from
very cursor reading-around in the code I think you have a few
mismatches in how you map drm concepts to dal structures:
- cursor is just a drm_plane - step 0 of atomic support is universale
plane support, and you didn't do that
On Sun, Feb 14, 2016 at 2:32 PM, Rob Clark wrote:
> On Fri, Feb 12, 2016 at 7:05 PM, Wentland, Harry
> wrote:
>> The current amdgpu display stack grew somewhat organically and as such is
>> not well suited to handling all of the hardware dependencies involved
>> especially in areas like
On Sun, Feb 14, 2016 at 12:22 PM, Jerome Glisse wrote:
>> There's still a bunch of legacy stuff in these patches that's on our list of
>> things to refactor. Some of that is
>> - dc/adapter
>> - dc/asic_capability
>> - dc/audio
>> - dc/bios
>> - dc/gpio
>>
>> We should be able to cut the size of
On Sat, Feb 13, 2016 at 12:05:48AM +, Wentland, Harry wrote:
> Hi Dave, Daniel, others,
[...]
> There's still a bunch of legacy stuff in these patches that's on our list of
> things to refactor. Some of that is
> - dc/adapter
> - dc/asic_capability
> - dc/audio
> - dc/bios
> - dc/gpio
>
>
On Fri, Feb 12, 2016 at 7:05 PM, Wentland, Harry
wrote:
>
> The current amdgpu display stack grew somewhat organically and as such is not
> well suited to handling all of the hardware dependencies involved especially
> in areas like audio. The drm abstractions used by the old code map less
Hi Dave, Daniel, others,
The goal with DAL is to provide a unified, full featured display stack to
service all of our Linux offerings. This driver will have to support our full
feature set beyond what's supported by amdgpu, e.g.
- synchronzied timings across different displays
- freesync
On 12 February 2016 at 07:06, Daniel Vetter wrote:
> On Thu, Feb 11, 2016 at 9:52 PM, Dave Airlie wrote:
>> On 12 February 2016 at 03:19, Harry Wentland
>> wrote:
>>> This set of patches enables the new DAL display driver for amdgpu on Carrizo
>>> Tonga, and Fiji ASICs. This driver will allow
On 12 February 2016 at 03:19, Harry Wentland wrote:
> This set of patches enables the new DAL display driver for amdgpu on Carrizo
> Tonga, and Fiji ASICs. This driver will allow us going forward to bring
> display features on the open amdgpu driver (mostly) on par with the Catalyst
> driver.
>
>
On Thu, Feb 11, 2016 at 10:06:14PM +0100, Daniel Vetter wrote:
> On Thu, Feb 11, 2016 at 9:52 PM, Dave Airlie wrote:
> > On 12 February 2016 at 03:19, Harry Wentland
> > wrote:
> >> This set of patches enables the new DAL display driver for amdgpu on
> >> Carrizo
> >> Tonga, and Fiji ASICs.
On Thu, Feb 11, 2016 at 9:52 PM, Dave Airlie wrote:
> On 12 February 2016 at 03:19, Harry Wentland
> wrote:
>> This set of patches enables the new DAL display driver for amdgpu on Carrizo
>> Tonga, and Fiji ASICs. This driver will allow us going forward to bring
>> display features on the open
That applies only to Carrizo, unfortunately.
Harry
From: Mike Lothian [mailto:m...@fireburn.co.uk]
Sent: February 11, 2016 3:03 PM
To: Wentland, Harry ; dri-devel at
lists.freedesktop.org
Subject: Re: [PATCH 00/29] Enabling new DAL display driver for amdgpu on
Carrizo and Tonga
Hi
Does that
Hi
Does that mean Tonga is capable of HDMI 2.0 or is it only Carrizo
Cheers
Mike
On Thu, 11 Feb 2016 at 17:20 Harry Wentland wrote:
> This set of patches enables the new DAL display driver for amdgpu on
> Carrizo
> Tonga, and Fiji ASICs. This driver will allow us going forward to bring
>
This set of patches enables the new DAL display driver for amdgpu on Carrizo
Tonga, and Fiji ASICs. This driver will allow us going forward to bring
display features on the open amdgpu driver (mostly) on par with the Catalyst
driver.
This driver adds support for
- Atomic KMS API
- MST
- HDMI 2.0
17 matches
Mail list logo
