On Mon, 17 Jul 2023 at 14:54, Simon Ser wrote:
>
> On Monday, July 17th, 2023 at 15:24, Emil Velikov
> wrote:
>
> > > > For going forward, here is one way we can shave this yak:
> > > > - update libdrm to max 64 nodes
> > > > - roll libdrm release, nag distributions to update to it // could
On Monday, July 17th, 2023 at 15:24, Emil Velikov
wrote:
> > > For going forward, here is one way we can shave this yak:
> > > - update libdrm to max 64 nodes
> > > - roll libdrm release, nag distributions to update to it // could be
> > > folded with the next release below
> > > - update
On Mon, 17 Jul 2023 at 10:45, Simon Ser wrote:
>
> On Monday, July 17th, 2023 at 09:30, Emil Velikov
> wrote:
>
> > > I'm worried what might happen with old user-space, especially old libdrm.
> >
> > I also share the same concern. Although the bigger issue is not libdrm
> > - since we can
On Monday, July 17th, 2023 at 09:30, Emil Velikov
wrote:
> > I'm worried what might happen with old user-space, especially old libdrm.
>
> I also share the same concern. Although the bigger issue is not libdrm
> - since we can update it and prod distributions to update it.
> The biggest
On Fri, 14 Jul 2023 at 11:32, Simon Ser wrote:
>
> (cc Daniel Vetter and Pekka because this change has uAPI repercussions)
>
> On Friday, June 30th, 2023 at 13:56, James Zhu wrote:
>
> > From: Christian König
> >
> > This makes room for up to 128 DRM devices.
> >
> > Signed-off-by: Christian
On Friday, July 14th, 2023 at 12:31, Simon Ser wrote:
> Before this patch, 0..63 are for primary, 64..127 are for control (never
> exposed by the kernel), 128..191 are for render, 2048..2112 are for accel.
> After this patch, 0..127 are for primary, 64..191 are for control (never
> exposed by
(cc Daniel Vetter and Pekka because this change has uAPI repercussions)
On Friday, June 30th, 2023 at 13:56, James Zhu wrote:
> From: Christian König
>
> This makes room for up to 128 DRM devices.
>
> Signed-off-by: Christian König
> Signed-off-by: James Zhu
> ---
>
