Announcement

Collapse
No announcement yet.

70 Patches Of Cleaning & Bug Fixes For Mesa

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

  • Hi-Angel
    replied
    Originally posted by bridgman View Post
    "Patchwork" is being used to track unreviewed patches
    Thank you!
    Originally posted by bridgman View Post
    , although it doesn't appear that they are being moved out of "New" state after they have been reviewed and submitted:

    https://patchwork.freedesktop.org/project/mesa/patches/
    Yeah, and besides this, the textbox "submitter" doesn't work with primary paste, doesn't work with right-click paste (but at least Ctrl+v works), but seem to require the user to paste the text, because it autocompletes if you pasted but not if you start typing manually. And the worst: if the completion didn't appear, and you pressed Enter, then α) search results doesn't include that line, β) the line clears, so you'd have to type from the beginning.

    Anyway, thanks for the link, it's better then nothing, I hope they will get the site into a usable state any time soon.

    Leave a comment:


  • Hi-Angel
    replied
    Originally posted by nuetzel View Post

    It _is_ there, now. (125 commits)
    https://cgit.freedesktop.org/mesa/mesa/log/

    compiled clean

    OpenGL vendor string: X.Org
    OpenGL renderer string: Gallium 0.4 on AMD TURKS (DRM 2.48.0 / 4.9.0-2.g6fbc0c0-default, LLVM 4.0.0)
    OpenGL core profile version string: 4.1 Mesa 13.1.0-devel (git-123e947)
    OpenGL core profile shading language version string: 4.10
    OpenGL core profile context flags: (none)
    OpenGL core profile profile mask: compatibility profile
    OpenGL core profile extensions:
    OpenGL version string: 4.1 Mesa 13.1.0-devel (git-123e947)
    OpenGL shading language version string: 4.10
    OpenGL context flags: (none)
    OpenGL profile mask: compatibility profile
    OpenGL extensions:
    OpenGL ES profile version string: OpenGL ES 3.0 Mesa 13.1.0-devel (git-123e947)
    OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
    OpenGL ES profile extensions:

    Now, I have to do some tests. ;-)
    Oh, wow, it's just(8h ago) landed! Thank you, whoever did it!

    Leave a comment:


  • smitty3268
    replied
    Shader cache cleanups? Good.

    Leave a comment:


  • nuetzel
    replied
    Originally posted by Hi-Angel View Post
    Have anybody an idea, is there a better way to track Mesa patches aside of daily checking https://cgit.freedesktop.org/mesa/mesa/log/ ? E.g. I'm waiting — already half a month — when the 84 nine patches would land into git, and still neither it did, nor even reviews appeared on the mailing list. I've got a feeling like everyone forgot them.
    It _is_ there, now. (125 commits)
    https://cgit.freedesktop.org/mesa/mesa/log/

    compiled clean

    OpenGL vendor string: X.Org
    OpenGL renderer string: Gallium 0.4 on AMD TURKS (DRM 2.48.0 / 4.9.0-2.g6fbc0c0-default, LLVM 4.0.0)
    OpenGL core profile version string: 4.1 Mesa 13.1.0-devel (git-123e947)
    OpenGL core profile shading language version string: 4.10
    OpenGL core profile context flags: (none)
    OpenGL core profile profile mask: compatibility profile
    OpenGL core profile extensions:
    OpenGL version string: 4.1 Mesa 13.1.0-devel (git-123e947)
    OpenGL shading language version string: 4.10
    OpenGL context flags: (none)
    OpenGL profile mask: compatibility profile
    OpenGL extensions:
    OpenGL ES profile version string: OpenGL ES 3.0 Mesa 13.1.0-devel (git-123e947)
    OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
    OpenGL ES profile extensions:

    Now, I have to do some tests. ;-)

    Leave a comment:


  • tarceri
    replied
    Originally posted by andrei_me View Post
    tarceri is there any user-facing change with the fixes, like some app doesn't crash/hang?

    Skimming through the mailing list, it seems like the patch lands improvements and better maintainability in the code base, as the SSO example you gave.
    No not that I'm aware of, the few bug fixes are for fairly obscure cases and just things I noticed during the clean-up

    Leave a comment:


  • bridgman
    replied
    "Patchwork" is being used to track unreviewed patches, although it doesn't appear that they are being moved out of "New" state after they have been reviewed and submitted:

    https://patchwork.freedesktop.org/project/mesa/patches/
    Last edited by bridgman; 20 December 2016, 05:06 PM.

    Leave a comment:


  • starshipeleven
    replied
    Originally posted by Hi-Angel View Post
    I've got a feeling like everyone forgot them.
    It's entirely possible. Sometimes you see someone pinging the devs on mailing lists on stuff that was simply overlooked.

    Leave a comment:


  • Hi-Angel
    replied
    Have anybody an idea, is there a better way to track Mesa patches aside of daily checking https://cgit.freedesktop.org/mesa/mesa/log/ ? E.g. I'm waiting — already half a month — when the 84 nine patches would land into git, and still neither it did, nor even reviews appeared on the mailing list. I've got a feeling like everyone forgot them.

    Leave a comment:


  • schmidtbag
    replied
    Cleaner code means future revisions/improvements will be faster and easier to accomplish. 70 patches is significant.

    Leave a comment:


  • ElectricPrism
    replied
    updated last night to latesr git, wake up and gdm wont boot again, ssh in and sddm starts.

    updated this morning now gdm boots again.

    At least rocket league n games are improving

    Leave a comment:

Working...
X