Displaying 3 results from an estimated 3 matches for "new_style_valid_mod".
2019 Oct 15
1
[PATCH] drm: Generalized NV Block Linear DRM format mod
...y're used on (we have a similar case on the intel side too).
>
> To make sure I'm clear, it would behave like this?
>
> fixed_mod = canonicalize(old_style_valid_mod, true);
> assert(fixed_mod == old_style_valid_mod | (0xfe << 12));
> fixed_mod = canonicalize(new_style_valid_mod, [false,true]);
> assert(fixed_mod == new_style_valid_mod);
>
> I'm unclear what it should do in this case though:
>
> fixed_mod = canonicalize(old_style_valid_mod, false);
>
> Since there's no code out there using the old style modifiers with
> Turing+ yet, an...
2019 Oct 15
0
[PATCH] drm: Generalized NV Block Linear DRM format mod
...about the
> platform they're used on (we have a similar case on the intel side too).
To make sure I'm clear, it would behave like this?
fixed_mod = canonicalize(old_style_valid_mod, true);
assert(fixed_mod == old_style_valid_mod | (0xfe << 12));
fixed_mod = canonicalize(new_style_valid_mod, [false,true]);
assert(fixed_mod == new_style_valid_mod);
I'm unclear what it should do in this case though:
fixed_mod = canonicalize(old_style_valid_mod, false);
Since there's no code out there using the old style modifiers with
Turing+ yet, and I don't want to try to support...
2019 Oct 15
2
[PATCH] drm: Generalized NV Block Linear DRM format mod
On Mon, Oct 14, 2019 at 03:13:21PM -0700, James Jones wrote:
> Builds upon the existing NVIDIA 16Bx2 block linear
> format modifiers by adding more "fields" to the
> existing parameterized
> DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK format modifier
> macro that allow fully defining a unique-across-
> all-NVIDIA-hardware bit layout using a minimal
> set of fields and values.