Announcement

Collapse
No announcement yet.

Vulkan 1.2.194 Brings New Extension For Google's Fuchsia OS

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • krOoze
    replied
    Originally posted by lowflyer View Post
    For the "unilateral things":
    Are you actually saying that I can create my own VK_LOWFLYER_non_woke_language extension for my pet raspberry-pi project (where I have vague plans to sell it sometime in the future) and get it properly registered???
    Simplistically speaking, yes. Might be questionable why are you making an extension for a device you are not a vendor of. Realistically in this case, your work should probably be championed by Mesa, Broadcom, or Raspi Foundation. You should likely also be in some kind of legal relationship with Khronos. Not sure if you need to be a full-fledged member. I don't see that being strictly necessary though. Not sure if even Mesa is; I think they are some kind of honorary member on the account they are just an open source project.

    KHR extension require some quality control and some compromise of vendors. EXT extensions imply some collaboration, or ecosystem thing, but it is much muddier. Vendor extensions (AMD, NV, ...) are largely between you (the app developer) and the vendor. As far as I know, it does not need to be voted on by the group. It only has to have all the formalities (registered in XML, not break the spec document or something, should be implemented I think on release, newly I think they very much prefer if you at least pretend you gonna implement Validation for it, and such).
    Last edited by krOoze; 30 September 2021, 05:39 AM.

    Leave a comment:


  • lowflyer
    replied
    Originally posted by krOoze View Post

    That's fine. Khronos did not cave here, because vendors can always make as many extensions as they want, as long as they register the names. Non-EXT and non-KHR extensions are pretty unilateral things...

    What Khronos did fully cave on recently is oligarchical collectivism from Google though.
    One is the result of the other. Khronos did cave in to goggle's weight (read: money). The wokeism and the benevolent acceptance of private extensions are just the visible part of it. The fundamentals that have been changed are kept secret to the public.

    For the "unilateral things":
    Are you actually saying that I can create my own VK_LOWFLYER_non_woke_language extension for my pet raspberry-pi project (where I have vague plans to sell it sometime in the future) and get it properly registered???

    Leave a comment:


  • krzyzowiec
    replied
    Originally posted by bug77
    That's pretty insane.
    Whoa, careful there! According to that document, you just used “ablelist” (whatever that means) language, buddy.

    Speaking for myself, I will continue using terms like master copy and blacklist/whitelist, because I favor clarity.

    Leave a comment:


  • Vistaus
    replied
    Originally posted by bug77 View Post

    That's pretty insane. In one of my first English lessons, my teacher (God rest his soul, he was such a great man - am I still allowed to say this?) taught me that in English "man" is often synonym to "person/people". Not anymore, it seems.
    I think that's pretty universal. In Dutch, we also use “man” and “boys” when referring a person/people.

    Leave a comment:


  • bug77
    replied
    Originally posted by krOoze View Post

    That's fine. Khronos did not cave here, because vendors can always make as many extensions as they want, as long as they register the names. Non-EXT and non-KHR extensions are pretty unilateral things...

    What Khronos did fully cave on recently is oligarchical collectivism from Google though.
    That's pretty insane. In one of my first English lessons, my teacher (God rest his soul, he was such a great man - am I still allowed to say this?) taught me that in English "man" is often synonym to "person/people". Not anymore, it seems.

    On topic, I can somehow understand having some Windows specific stuff in there. Windows is still a behemoth, after all. But Fuchsia? I couldn't get a Fuchsia enabled device today if my life depended on it

    Leave a comment:


  • marlock
    replied
    [rant mode on]
    guess what's 1000x more obnoxious, toxic and destructive than implementing inclusive language in software?

    yes, actively complaining and fighting against it everywhere without any context or explicit legitimate motivation

    we were talking about software, but oh no! someone just had to try to derail it, because god help us all if we are tortured into not using our favourite racist slur! that's such a crime that it just has to be THE topic EVERYWHERE, ALL THE TIME!
    [rant mode off]

    can we please stay on topic?

    Leave a comment:


  • krOoze
    replied
    Originally posted by lowflyer View Post
    I have some reservations against these extensions. Khronos caving in before software giant Google. If you're big enough you can have your own private "extension"?
    That's fine. Khronos did not cave here, because vendors can always make as many extensions as they want, as long as they register the names. Non-EXT and non-KHR extensions are pretty unilateral things...

    What Khronos did fully cave on recently is oligarchical collectivism from Google though.

    Leave a comment:


  • marlock
    replied
    While Vulkan's WSI chapter holds various platform-specific extensions, it also clearly aims to support different creation methods with a unified abstracted surface object as a result... and there is just that single platform-specific method for each... to the point that using and even destroying the resulting surface is done via unified methods.

    It's impossible to completely abstract away the platforms, but this is clearly a best-effort unification, not the wild west.

    Also, regarding other extensions, I am not intimate with the governance involved, but I do know there is a history of vendor-specific extensions later being revised into general-purpose extensions and even into the core specification...

    Leave a comment:


  • skeevy420
    replied
    VK_EXT_physical_device_drm

    This extension provides new facilities to query DRM properties for physical devices, enabling users to match Vulkan physical devices with DRM nodes on Linux.
    Oh, look, a Linux Vulkan extension.

    Also, check: 33. Window System Integration (WSI). That's basically nothing but OS specific stuff. Y'all are gonna love 33.2.3.

    Leave a comment:


  • lowflyer
    replied
    I have some reservations against these extensions. Khronos caving in before software giant Google. If you're big enough you can have your own private "extension"?

    Leave a comment:

Working...
X