>In reality nvidia just chose to not invest in it. This sums it up
This article is proving my point. People were not willing to work with Nvidia and would prefer to stick to their unstandardized Mesa specific approach with gbm. As a path forward Nvidia tried proposing a cross platform open standard that would solve not only wayland's use case, which to me appears as Nvidia going above in investment.
>allow nouveau to reclock gpus
Nouveau able to if they load the proper firmware onto the GPU.
>at least there's one usable driver
It's quite a stretch to call it usable and would not make sense to be the default experience for the average user.
>follow the community consensus and go with GBM straight away
As I mentioned GBM was tightly coupled with Mesa, so that wasn't directly possible.
>open source their driver like other manufacturer and be part of mesa.
This is an unreasonable demand, that would never happen. Saying that Wayland won't work on Nvidia hardware because they won't open source the driver and port it to Mesa just shows how stubborn and uncooperative one is as opposed to trying to find solutions to deliver user value.
>dedicate a lot of time and effort to create a whole code path for nvidia only and having to debug it against a black box driver
There was never anything nvidia only in this situation. The only "only" was gbm being a proprietary API that was only a part of Mesa.
> This article is proving my point. People were not willing to work with Nvidia and would prefer to stick to their unstandardized Mesa specific approach with gbm. As a path forward Nvidia tried proposing a cross platform open standard that would solve not only wayland's use case, which to me appears as Nvidia going above in investment.
Kwin, gnome and xwayland did end up supporting eglstream, it was shit, people blamed wayland because it became a sport, nvidia did go gdm in the end and the eglstream backends which were a waste of time were dropped.
> Nouveau able to if they load the proper firmware onto the GPU.
Nvidia explicitly prevented them to do so by not providing the ability to load any firmware...
> As I mentioned GBM was tightly coupled with Mesa, so that wasn't directly possible.
It absolutely was and their driver is using GBM now as a proof.
> This is an unreasonable demand, that would never happen. Saying that Wayland won't work on Nvidia hardware because they won't open source the driver and port it to Mesa just shows how stubborn and uncooperative one is as opposed to trying to find solutions to deliver user value.
Why so? Most manufacturer do so.
> There was never anything nvidia only in this situation. The only "only" was gbm being a proprietary API that was only a part of Mesa.
GBM is specific to mesa maybe but far from proprietary what world do you live in? :D
>Kwin, gnome and xwayland did end up supporting eglstream, it was shit
Something is better than nothing.
>nvidia did go gdm in the end and the eglstream backends which were a waste of time were dropped.
If the wayland project was run better and there was proper collaboration this waste could have been avoided.
>Nvidia explicitly prevented them to do so by not providing the ability to load any firmware...
How would the GPU know? They should be able to do exactly what the real driver does to load the firmware.
>It absolutely was and their driver is using GBM now as a proof.
Only years later after due to Nvidia contributing code to allow for it to dynamically load backends. This wasn't a case of Nvidia ignoring an existing way for them to have a backend.
>Why so? Most manufacturer do so.
Because it's a trade secret and potentially can not be legally be open sourced. It also is a competitive advantage for nvidia not to. Plenty of companies also develop closed source drivers. Nvidia is not unique.
>GBM is specific to mesa maybe but far from proprietary
Recheck the definition of "proprietary." Compare how many GPUs and operating systems support OpenGL vs supporting GBM. GBM being exclusive to Mesa makes it proprietary.
This article is proving my point. People were not willing to work with Nvidia and would prefer to stick to their unstandardized Mesa specific approach with gbm. As a path forward Nvidia tried proposing a cross platform open standard that would solve not only wayland's use case, which to me appears as Nvidia going above in investment.
>allow nouveau to reclock gpus
Nouveau able to if they load the proper firmware onto the GPU.
>at least there's one usable driver
It's quite a stretch to call it usable and would not make sense to be the default experience for the average user.
>follow the community consensus and go with GBM straight away
As I mentioned GBM was tightly coupled with Mesa, so that wasn't directly possible.
>open source their driver like other manufacturer and be part of mesa.
This is an unreasonable demand, that would never happen. Saying that Wayland won't work on Nvidia hardware because they won't open source the driver and port it to Mesa just shows how stubborn and uncooperative one is as opposed to trying to find solutions to deliver user value.
>dedicate a lot of time and effort to create a whole code path for nvidia only and having to debug it against a black box driver
There was never anything nvidia only in this situation. The only "only" was gbm being a proprietary API that was only a part of Mesa.