Why ?
It really doesn't make sense to me to add every member to every struct that linux uses just to satisfy compilation.

For Linux webcamd I usually stub it. Will this be fully implemented for ARM64 I presume?

In D34318#777015, @hselasky wrote:

For Linux webcamd I usually stub it. Will this be fully implemented for ARM64 I presume?

That would be crazy.

In D34318#777013, @manu wrote:

Why ?
It really doesn't make sense to me to add every member to every struct that linux uses just to satisfy compilation.

Because it's a lot easier to add the error returning stubs then to #ifdef out the drivers and maintain that over time.

In D34318#777059, @bz wrote:

In D34318#777013, @manu wrote:

Why ?
It really doesn't make sense to me to add every member to every struct that linux uses just to satisfy compilation.

Because it's a lot easier to add the error returning stubs then to #ifdef out the drivers and maintain that over time.

I've been maintaining drm-kmod from quite some time now and for me it's better to ifdef out in the code. It also shows that we have no intention of implementing this.

In D34318#777064, @manu wrote:

In D34318#777059, @bz wrote:

In D34318#777013, @manu wrote:

Why ?
It really doesn't make sense to me to add every member to every struct that linux uses just to satisfy compilation.

Because it's a lot easier to add the error returning stubs then to #ifdef out the drivers and maintain that over time.

I've been maintaining drm-kmod from quite some time now and for me it's better to ifdef out in the code. It also shows that we have no intention of implementing this.

Did you add the CONFIG_OF around the drm code or was it there?

I have more instances of this in a single file than I can find in the entire drm-kmod code and given the KConfig of my drivers doesn't even depend on CONFIG_OF I assume Linux must have dummy fallbacks as well as otherwise these drivers wouldn't compile in Linux for non OF kernels.

So your suggestion is to deal with these three drivers which need the pointer and completely #ifdef all the calls out and then if actually needed add native FreeBSD code and then maintain that rather that add a pointer and dummy calls? So double the work with each driver and the other ones to come? Right. Happy weekend.

IMO things we want to have in future should be #ifdef-ed in driver rather than dummy-implemented in LKPI
But in that case we can define opaque struct device_node; in linux/of.h to satisfy struct device_node *of_node; member of struct class and than add dummy implementation somewhere in wifi driver to get rid of extra #ifdef-s