Replies: 1 comment
-
user here, i think the larger (vendor) modules aren't so relevant. they'll do their own thing primarily, what worries me is all the outdated / tiny stuff. i.e. when you fix/reactivate some forgotten broadcom 10g driver that actually works perfectly fine but noone took care of. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Looking across various projects using dkms (bbswitch, nvidia driver, openzfs and a bunch of others). The vast majority of them copy/paste the default (in-dkms) make/clean commands:
That has a few interesting side effects - both
kernel_source_dir
(aka the linux path) and$dkms_tree
are hard-coded in their config.Glancing at the more complex modules (nvidia, openzfs) - they are glorified wrappers allowing behaviour changes (via funky indirection).
Off the top of my head, to handle these we could introduce a variable which gets added to the make command above. Say
BUILD_FLAGS
orBUILD_DEFINES
(must include only-D...
) or alike. As always thedkms.conf
file will have the default, which can be altered by users with the existingconf.d
override mechanism.@scaronni @xuzhen any preferences?
@hadogenes considering your experience with openzfs what your take?
0 votes ·
Beta Was this translation helpful? Give feedback.
All reactions