Re: [PATCH v6 3/4] drm: Expand max DRM device number to full MINORBITS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH v6 3/4] drm: Expand max DRM device number to full MINORBITS
From: James Zhu <jamesz@xxxxxxx>
Date: Wed, 23 Aug 2023 10:06:37 -0400
Cc: Matthew Wilcox <willy@xxxxxxxxxxxxx>, Michał Winiarski <michal.winiarski@xxxxxxxxx>, Thomas Zimmermann <tzimmermann@xxxxxxx>, David Airlie <airlied@xxxxxxxx>, Emil Velikov <emil.l.velikov@xxxxxxxxx>, intel-gfx@xxxxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, dri-devel@xxxxxxxxxxxxxxxxxxxxx, Oded Gabbay <ogabbay@xxxxxxxxxx>, Maxime Ripard <mripard@xxxxxxxxxx>, Pekka Paalanen <pekka.paalanen@xxxxxxxxxxxxx>, James Zhu <James.Zhu@xxxxxxx>, Christian König <christian.koenig@xxxxxxx>
In-reply-to: <f1Cwh796fW9-Sse4KkXw1Xpgaknx9yWMP3bi-8mGhNOmZ2_aeqg5unzrBNuHiNCPzvXTs6B2tH-XxNH7jVWDzg3PnVmCa5XaXTe3xhxyTM8=@emersion.fr>
Organization: AMD RTG
References: <20230724211428.3831636-1-michal.winiarski@intel.com> <20230724211428.3831636-4-michal.winiarski@intel.com> <83s0YPWEdYE6C2a8pa6UAa3EaWZ2zG-q7IL9M-y6W1ucF9V54VnZtigKj3BGKUA2FZpIrs0VVxmpHO2RAhs_FdOnss9vNLQNSHySY8uH7YA=@emersion.fr> <69801f61-37b0-3e46-cbef-31ff80ae9a34@amd.com> <TAdBP5BOy3cy7VnUb4t7ZkDOMK6wI_gPCjXanItN3TOsA1TbSk_6yrlcPTqvk3AZjamo96yHlEhjpfNUPFF6tA_9K8iRoie3h_z5Jf6zNtc=@emersion.fr> <ad26d275-4373-429f-ecaa-3e35978f1fb0@amd.com> <61efe587-9a7a-063c-a388-eed9f51958d4@amd.com> <f1Cwh796fW9-Sse4KkXw1Xpgaknx9yWMP3bi-8mGhNOmZ2_aeqg5unzrBNuHiNCPzvXTs6B2tH-XxNH7jVWDzg3PnVmCa5XaXTe3xhxyTM8=@emersion.fr>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0

Hi Simon,

Thanks! Yes, this kernel patch should work with latest libdrm.

Best regards!

James Zhu

On 2023-08-23 06:53, Simon Ser wrote:

On Tuesday, August 8th, 2023 at 17:04, James Zhu <jamesz@xxxxxxx> wrote:

I have a MR for libdrm to support drm nodes type up to 2^MINORBITS
nodes which can work with these patches,

https://gitlab.freedesktop.org/mesa/drm/-/merge_requests/305

FWIW, this MR has been merged, so in theory this kernel patch should
work fine with latest libdrm.

References:
- [PATCH v6 0/4] drm: Use full allocated minor range for DRM
  - From: Michał Winiarski
- [PATCH v6 3/4] drm: Expand max DRM device number to full MINORBITS
  - From: Michał Winiarski
- Re: [PATCH v6 3/4] drm: Expand max DRM device number to full MINORBITS
  - From: Simon Ser
- Re: [PATCH v6 3/4] drm: Expand max DRM device number to full MINORBITS
  - From: Christian König
- Re: [PATCH v6 3/4] drm: Expand max DRM device number to full MINORBITS
  - From: Simon Ser
- Re: [PATCH v6 3/4] drm: Expand max DRM device number to full MINORBITS
  - From: Christian König
- Re: [PATCH v6 3/4] drm: Expand max DRM device number to full MINORBITS
  - From: James Zhu
- Re: [PATCH v6 3/4] drm: Expand max DRM device number to full MINORBITS
  - From: Simon Ser

Prev by Date: [Bug 217664] Laptop doesnt wake up from suspend mode.
Next by Date: Re: [PATCH drm-misc-next] drm/nouveau: uapi: don't pass NO_PREFETCH flag implicitly
Previous by thread: Re: [PATCH v6 3/4] drm: Expand max DRM device number to full MINORBITS
Next by thread: Re: [PATCH v6 0/4] drm: Use full allocated minor range for DRM
Index(es):
- Date
- Thread

[Index of Archives] [Linux DRI Users] [Linux Intel Graphics] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI] [XFree86] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Linux Kernel] [Linux SCSI] [XFree86]