From: Felix Kuehling <felix.kuehling@amd.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel <dri-devel@lists.freedesktop.org>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: CONFIG_AMDGPU triggers full rebuild
Date: Mon, 28 Sep 2020 12:17:42 -0400 [thread overview]
Message-ID: <ef014d4c-1406-d0a7-839f-7715d7afd15c@amd.com> (raw)
In-Reply-To: <e7f5e4ae-7a6a-0a3c-666c-05180a8fe726@suse.de>
If I had to guess, I'd say something HMM-related. There has been some
back-and-forth between kernel releases. So I won't say anything more
specific without knowing exactly which branch or release you're on.
Regards,
Felix
Am 2020-09-25 um 10:29 a.m. schrieb Thomas Zimmermann:
> Hi,
>
> whenever I change the option CONFIG_AMDGPU, I have to rebuild the whole
> kernel. I guess it auto-selects some architecture-specific feature. That
> full rebuild might be avoidable if I could enable that feature permanently.
>
> Any ideas what this could be and how to avoid the full rebuilt?
>
> Best regards
> Thomas
>
>
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=02%7C01%7Cfelix.kuehling%40amd.com%7Cc20a2a8c47254a18c90b08d8615f6e31%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637366409873197811&sdata=k2S8ouQzP6GKO3AWJRheEFblXp7CkULMvxrhGUHWq3g%3D&reserved=0
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2020-09-28 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 14:29 CONFIG_AMDGPU triggers full rebuild Thomas Zimmermann
2020-09-25 14:54 ` Christian König
2020-09-25 15:04 ` Thomas Zimmermann
2020-09-28 16:17 ` Felix Kuehling [this message]
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=ef014d4c-1406-d0a7-839f-7715d7afd15c@amd.com \
--to=felix.kuehling@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=tzimmermann@suse.de \
/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