been using Arch for years but i am still a novice, yesterday i had found that in order for something to work on my system i will need to edit a few lines in kernel which i did, then removed unnecessary modules > intel, > nvidia, compiled. it worked great but with Arch and its rolling release i am dreading the next update and having to go through this again.
what methods are there to automate this process?
What modifications were required? The good part of a rolling release is that upstreaming things means you only have to deal with manual fixes for like 2 or 3 updates.
set
LINK_TRAINING_ATTEMPTSfrom5to10in drivers/gpu/drm/amd/display/dc/link/link_dpms.c and setLINK_TRAINING_RETRY_DELAYfrom50to100in drivers/gpu/drm/amd/display/dc/link/protocols/link_dp_training.c.i doubt this will be added to kernel as its a fix for an issue that isn’t wide spread.
Use diff patches and automate with some bash scripting.
That wouldn’t be accepted as is, but those sound like tunables. They could be exposed as kernel parameters. May be worth submitting the patch as an RFC just to call attention to it.
thank you i will read up on how to submit this kind of stuff.
I followed your advice, Github my edit link_dpms.c, - Github my edit link_dp_training.c how do i submit as RFC. total noob with github lol.
Successful GitHub pulls are rare; more often, patches live like this. You’re better off contacting the maintainer of the subsystem you’re editing. See the official submission guide.
Not to be dejecting!
thank you and no dejection taken. you’re actually very helpful :D
Ah, so the kernel actually uses mailing lists. You need to use the get maintainers Perl script to get the people you need to send the email TO and then send it to them with the dri-devel list CC’d.