Announcement

Collapse
No announcement yet.

Wayland Is Driving Fragmentation Around EDID Parsing - A Call To Fix That

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

  • #31
    Originally posted by bug77 View Post
    Wayland is more than a protocol, because it doesn't stop at defining how some parties must talk to each other, it also defines which parties talk. That's the part that's giving everyone a hard time. Implementing Wayland is not like implementing IPv6 where you already have IPv4, it's a freaking rewrite of everything you already have.
    Then X11 is also not a protocol.

    Comment


    • #32
      Originally posted by mos87 View Post
      What, an architectural oversight leading to implementations having to do the same thing every client has to each on their own??
      Totally unexpected tbh from the redhat/gnome/PROGRESSIVEPEOPLEOFTHEFUTURE stack =P
      It was okay when every X compositor was implementing and doing the same things?

      Comment


      • #33
        Originally posted by birdie View Post
        Ah, here we go again, Wayland doesn't provide a standard(ized) WM/WC out of the box or is Wayland = Gnome?
        Here is a link to: https://github.com/wayland-project/weston

        X11 comes without a standard WM, Xorg as the most popular implementation too.

        When you need to troll, at least put some work in it.

        Comment


        • #34
          Originally posted by Zan Lynx View Post
          No, there's like six X implementation that run on x86 hardware. Most of them are obsolete and haven't been maintained for ages but they're there.
          You seem to have a problem understanding language. They're obsolete so they are not there. There is only one implementation of X and that's what everyone is using. (And, no, it doesn't matter if some obscure system is running 30 years old software with a legacy X windowing system in the backroom of some factory offline.)

          Comment


          • #35
            Originally posted by microcode View Post
            EDID parsing is not that complicated, and the styles of many of these projects are different (though some of them are similar enough). I feel like it's not really a big deal to have EDID parser fragmentation.
            Not complicated? There was a decade-old sample parser and it had about 1500 lines of C code. It was an example so probably didn't even cover everything, plus being very old. The implementation used by Linux TV seems to be multiple thousands of rows of code in C++.

            https://git.linuxtv.org/edid-decode.git/tree/

            Comment


            • #36
              Originally posted by Alexmitter View Post
              Then X11 is also not a protocol.
              Wow, you blow my mind. Any day now you may figure out on your own water is wet.

              The X Window System (X11, or simply X) is a windowing system for bitmap displays, common on Unix-like operating systems.
              https://en.wikipedia.org/wiki/X_Window_System

              Not to mention what X is (or isn't) is totally irrelevant in this context.

              Comment


              • #37
                Originally posted by Alexmitter View Post

                Here is a link to: https://github.com/wayland-project/weston

                X11 comes without a standard WM, Xorg as the most popular implementation too.

                When you need to troll, at least put some work in it.
                X11 = X.org for the past >10 years. Weston is not a standard WM/compositor and Mutter/Kwin/wlroot/etc implement various desktop APIs differently.

                When you want to look smug at least have your arguments right.

                Comment


                • #38
                  Originally posted by birdie View Post
                  X11 = X.org for the past >10 years. Weston is not a standard WM/compositor and Mutter/Kwin/wlroot/etc implement various desktop APIs differently.

                  When you want to look smug at least have your arguments right.
                  This is not having the long term history. X11=X.org does not in fact go back perfectly 10 years.

                  Solaris only moved to X.org fully in 2010 before that that platform was a choice between X.org and Xsun. But you go and use a HPuX server today and its HP X11 that don't use X.org. This is the thing when you say X11 most commonly on Linux these days it equals X.org. But there are still Linux distributions where you found MicroXwin or equal closed source until 2015.

                  https://github.com/tinycorelinux/tinyx
                  We still have Linux distributions like tinycorelinux shipping with their own customs X11 servers today.

                  So birdie "X11=X.org for the past >10 Years" in reality is not true. There is a lot of X11 fragmentation you have just ignored

                  libwayland-server has over time expended in the features in provides. Please note Mutter/Kwin and Wlroots all use libwayland-server.
                  https://gitlab.freedesktop.org/wayla...ree/master/src
                  Yes there is a core common code part to wayland in libraries from the main project.

                  Also Weston is officially the reference compositor for Wayland the same way X.org X11 was the reference X11 server for the X11 protocol. So its kind of sad that libweston has not been picked up by more compositors. This is normal levels of fragmentation for what was going on with X11 server before wayland that you have been failing to see birdie.

                  Comment


                  • #39
                    Originally posted by oiaohm View Post
                    So birdie "X11=X.org for the past >10 Years" in reality is not true. There is a lot of X11 fragmentation you have just ignored
                    I'm not sure I agree about fragmentation when everything that's not X.org is either very niche or already dead.

                    Comment


                    • #40
                      Originally posted by Alexmitter View Post

                      It was okay when every X compositor was implementing and doing the same things?
                      Lol, X and compositing??))) Oh the irony.
                      I'll just say that X for a system from 80-something worked (and continues to work) quite well, despite maybe internally becoming a mess over the years.

                      Comment

                      Working...
                      X