From: James Zhu <jamesz@amd.com>
To: James Zhu <James.Zhu@amd.com>, dri-devel@lists.freedesktop.org
Cc: Alexander.Deucher@amd.com, christian.koenig@amd.com,
daniel.vetter@ffwll.ch, epilmore@gigaio.com
Subject: Re: [PATCH] drm: register more drm device nodes
Date: Thu, 29 Aug 2024 15:56:46 -0400 [thread overview]
Message-ID: <106fdf86-9705-4ce9-ad16-b9eca164d1af@amd.com> (raw)
In-Reply-To: <6a447a16-2d81-42a7-bcdf-6a9805c92d20@amd.com>
Please ignore this. need update unregister_chrdev in the meantime Will
send out v2 later,
On 2024-08-29 15:51, James Zhu wrote:
> Ping ...
>
> On 2024-05-30 11:34, James Zhu wrote:
>> Since the default number 256 can't handle large modern systems
>> with large numbers of GPUs, specify a more reasonable default.
>>
>> Signed-off-by: James Zhu <James.Zhu@amd.com>
>> ---
>> drivers/gpu/drm/drm_drv.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c
>> index 243cacb3575c..719ea57a70ab 100644
>> --- a/drivers/gpu/drm/drm_drv.c
>> +++ b/drivers/gpu/drm/drm_drv.c
>> @@ -1086,7 +1086,7 @@ static int __init drm_core_init(void)
>> drm_debugfs_root = debugfs_create_dir("dri", NULL);
>> - ret = register_chrdev(DRM_MAJOR, "drm", &drm_stub_fops);
>> + ret = __register_chrdev(DRM_MAJOR, 0, 1024, "drm", &drm_stub_fops);
>> if (ret < 0)
>> goto error;
next prev parent reply other threads:[~2024-08-29 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 15:34 [PATCH] drm: register more drm device nodes James Zhu
2024-08-29 19:51 ` James Zhu
2024-08-29 19:56 ` James Zhu [this message]
2024-08-29 21:37 ` [PATCH v2] " James Zhu
2024-09-02 10:40 ` Daniel Vetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=106fdf86-9705-4ce9-ad16-b9eca164d1af@amd.com \
--to=jamesz@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=James.Zhu@amd.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=epilmore@gigaio.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox