kobject is only needed when we want to fully emulate linux drivers
and not when we need linux helpers like in drmkpi.
No functional changes intended.
Differential D26727
linuxkpi: Move kobject related function in its own file manu on Oct 9 2020, 9:28 PM. Authored by Tags None Referenced Files
Details
kobject is only needed when we want to fully emulate linux drivers No functional changes intended.
Diff Detail
Event Timeline
Comment Actions Can you quickly elaborate what "drmkpi" is? Is that what we know as drm.ko? If that's it then is the reason that you basically have a freebsd module implementation there and just an internal glue to the linux device? I don't see how you could currently fully split kobj off from a linux device and make it optional? So while I like the idea of having the functions in their own file, I am confused a bit by the short explanation given.
Comment Actions See D23085 (Or https://github.com/evadot/freebsd/tree/drm_base_v5.6-20201007 for a more up to date version).
drmkpi is basically linuxkpi without linux device emulation part
Comment Actions Another tree. Thanks!
So is the goal to be able to merge this into linuxkpi as well and hence the separation of files or will it stay separate? Comment Actions Some people didn't like the code duplication (which is understandable) so my goal is to split linuxkpi into "helpers" and device/file emulation part. |