GL framebuffer fetch behavior
Hi, An issue recently came up in the GL working group: what is the robustness behavior of framebuffer fetch? For example, if a framebuffer attachment format is R8_UNORM, what are the YZW components which get read back? If people from all the drivers (besides panfrost) which support this extension could reply with the expected behavior on their hardware, that would be helpful. Thanks, Mike
Re: GL framebuffer fetch behavior
For v3d yzw would be 0,0,1. Iago El mié, 23-04-2025 a las 12:24 -0400, Mike Blumenkrantz escribió: > Hi, > > An issue recently came up in the GL working group: what is the > robustness behavior of framebuffer fetch? For example, if a > framebuffer attachment format is R8_UNORM, what are the YZW > components which get read back? > > If people from all the drivers (besides panfrost) which support this > extension could reply with the expected behavior on their hardware, > that would be helpful. > > > Thanks, > Mike
[ANNOUNCE] mesa 25.1.0-rc2
Hello everyone, I'm happy to announce the next release candidate, 25.1.0-rc2. As always, if you find any issues please report them here: https://gitlab.freedesktop.org/mesa/mesa/-/issues/new Any issue that should block the release of 25.1.0 final, thus adding more 25.1.0-rc* release candidates, must be added to this milestone: https://gitlab.freedesktop.org/mesa/mesa/-/milestones/50 The next release candidate is expected in one week, on April 30th. Cheers, Eric --- Alyssa Rosenzweig (8): hk: fix underbinding scratch hk: fix tessellation + clipper queries hk: fix null FS corner cases agx: model sources as late-kill in demand calcs agx: late-kill sources agx: early-kill sources only if it won't shuffle hk: fix patch count = 0 handling asahi: fix possible null deref Boris Brezillon (2): panvk/csf: Pass less arguments to emit_vs_attrib() panvk/csf: Fix instance attribute offseting Connor Abbott (1): tu: Fix flushing when using a staging buffer for copies Danylo Piliaiev (1): tu,freedreno: Don't fallback to LINEAR with DRM_FORMAT_MOD_QCOM_COMPRESSED David Rosca (1): radeonsi/vcn: Fix decode target index for H264 interlaced streams Ella Stanforth (1): v3d/compiler: Fixup output types for all 8 outputs Eric Engestrom (10): .pick_status.json: Update to d5ad7981401c2393cac38fc3215e8bbb97de06b9 .pick_status.json: Update to 1bf8542490679fa2a244e27fb2b04bbc3d122f74 meson: remove duplicate `deprecated` for `gallium-xa` option meson: remove duplicate `deprecated` for `power8` option .pick_status.json: Update to 5f3a3740dcc6d243f2ef14138fb1c09bcbb9b5fd pick-ui: make `Backport-to: 25.0` backport to 25.0 *and more recent release branches* .pick_status.json: Update to dd3e1190a2bdbc6b996152510407adb9a8cb5618 pick-ui: add missing dependency [25.1 only] ci: don't treat misleading-indentation warnings are error on alpine VERSION: bump for 25.1.0-rc2 Faith Ekstrand (4): nak/legalize: Take a RegFile in copy_alu_src_and_lower_fmod nak/legalize: Take a RegFile in copy_alu_src_and_lower_ineg() nak/sm70: Fix the bit74_75_ar_mod assert nvk: Maxwell+ is now conformant GKraats (1): EGL: legacy-x11=dri2 should support hardware driver Georg Lehmann (4): nir/opt_algebraic: disable fsat(a + 1.0) opt if a can be NaN aco: set opsel_hi to 1 for WMMA aco/insert_exec: only restore wqm mask after control flow if necessary aco/insert_exec: reset temporary when recreating wqm mask from exact mask Janne Grunau (2): venus: Do not use instance pointer before NULL check venus: virtgpu: Require stable wire format José Roberto de Souza (3): intel: Program XY_FAST_COLOR_BLT::Destination Mocs for gfx12 intel: Fix the MOCS values in XY_FAST_COLOR_BLT for Xe2+ intel: Fix the MOCS values in XY_BLOCK_COPY_BLT for Xe2+ Karol Herbst (1): rusticl/device: fix panic when disabling 3D image write support Marek Olšák (1): radv: fix incorrect patch_outputs_read for TCS with dynamic state Mary Guillemard (2): panfrost: Take tiler memory budget into account in pan_select_tiler_hierarchy_mask panvk: reset dyn_bufs map count to 0 in create_copy_table Mel Henning (4): nak/spill_values: Spill constants across edges if needed nak: Handle idp4 ureg latencies nvk: SET_STATISTICS_COUNTER at start of meta_begin nvk: Override render enable for blits and resolves Mike Blumenkrantz (1): zink: verify that surface exists when adding implicit feedback loop Patrick Lerda (1): mesa_interface: fix legacy dri2 compatibility Pierre-Eric Pelloux-Prayer (2): winsys/amdgpu: disable VM_ALWAYS_VALID radeonsi: fix potential use after free in si_set_debug_callback Rhys Perry (2): aco/gfx12: don't use second VALU for VOPD's OPX if there is a WaR aco: combine VALU lanemask hazard into VALUMaskWriteHazard Rohan Garg (1): anv: re enable compression for CPS surfaces on platforms other than Xe Tapani Pälli (2): iris: force reallocate on eglCreateImage with GFX >= 20 iris: make sure to not mix compressed vs non-compressed Tomeu Vizoso (2): etnaviv/ml: Use etna_buffer_resource instead of etna_resource etnaviv: Release screen->dummy_desc_reloc.bo Yinjie Yao (1): gallium/pipe: Increase hevc max slice to 600 Yiwei Zhang (1): venus: fix missing renderer destructions git tag: mesa-25.1.0-rc2 https://mesa.freedesktop.org/archive/mesa-25.1.0-rc2.tar.xz SHA256: e6a7d1e198df97f36b0a2e029b1f9fef37e9feb86cdb7984de55c7052f23ec93 mesa-25.1.0-rc2.tar.xz SHA512: c1475aefa4d12412c33e177c42bb6b80abf10cee2ed46142b6c9f62cfcba29c1b126cc22fcbbe6bdc5d57b8c1b670fc7fc948cd4f846124d158bd7e019c88d21 mesa-25.1.0-rc2.tar.xz PGP: https://mesa.freedesktop.org/archive/mesa-25.1.0-rc2.tar.xz.sig signature.asc Description: PGP signature
Re: GL framebuffer fetch behavior
AMD lowers it to an image load, which follows the rules for image views, so (x, 0, 0, 1) for R8_UNORM. Marek On Wed, Apr 23, 2025 at 12:25 PM Mike Blumenkrantz < michael.blumenkra...@gmail.com> wrote: > Hi, > > An issue recently came up in the GL working group: what is the robustness > behavior of framebuffer fetch? For example, if a framebuffer attachment > format is R8_UNORM, what are the YZW components which get read back? > > If people from all the drivers (besides panfrost) which support this > extension could reply with the expected behavior on their hardware, that > would be helpful. > > > Thanks, > Mike >
Announcement: 2025 X.Org Foundation Election Candidates
To all X.Org Foundation Members: The election for the X.Org Foundation Board of Directors will begin on 30 April 2025. We have five candidates who are running for four seats. They are (in alphabetical order): * Andres Gomez * Arkadiusz Hiler * Megan Knight * Lyude Paul * Harry Wentland Attached below are the Personal Statements each candidate submitted for your consideration along with their Statements of Contribution that they submitted with the membership application. Please review each of the candidates' statements to help you decide whom to vote for during the upcoming election. If you have questions of the candidates, you should feel free to ask them here on the mailing list. The election committee will provide detailed instructions on how the voting system will work when the voting period begins. PLEASE NOTE: To participate in this election you MUST renew your membership by 28 April 2025! Please go to the Members page for your membership application or renewal. Best, Mark Filion, on behalf of the X.Org elections committee Nominees (in alphabetical order) Andres Gomez Current Affiliation: Igalia Personal Statement: I have been an active Open Source contributor since 2003, participating in projects like GNOME, and FreeDesktop, among others. I started to be actively involved with OSS graphic drivers in 2014, where I continue devoting much of my time, although from a coordination perspective for our team of developers at Igalia. By joining X.Org board I hope to give a bit more back to the community, helping to get things done. Among other things, I've contributed to create the graphic design for the public image of some past OSS events. I'll be happy to work in other tasks, including the organization of XDC. I could take part in the CfP committee, for example, or anything else the board could need help with. Arkadiusz Hiler Current Affiliation: CodeWeavers Personal Statement: Gaming on Linux is one of the main driving forces for the development of a lot of the technologies under the X.Org umbrella. I would like to represent the gaming part of the user space. During my 2 years on the board I've helped with finances and planning for the freedesktop.org migration, assuring that it's sustainable. I also have experience with running conferences and I'm more than happy to help any future XDC organizers on the ground and with streaming the events. Megan Knight Current Affiliation: Director of Software Communities, Arm Personal Statement: I am very new to the X.Org community, but eager to help out! I’ve been in open source for over a decade and have extensive experience planning large scale OS events, engaging with communities, delivering on Advocacy initiatives and being the translator between technical and business decision makers. Currently, I am working on a proposal to organize the upcoming 2026 edition of XDC and alsop plan to attend XDC 2025. I currently serve as the Advocacy Chair for Yocto Project and in the last four years have improved developer relations, improved documentation and onboarding processes, increased their website SEO, migrated/redesigned their website to increase traffic, produce(d) 5+ events a year from start to finish, and increased revenue by attracting new members/upleveling existing members. If elected, I look forward to diving deep into X.Org and will apply these skills so developers can focus on building great tech. Lyude Paul Current Affiliation: Red Hat Personal Statement: Hi! My name is Lyude Paul, and I'm currently employed at Red Hat as a Software Engineer. I'm also currently on the X.org Board of Directors as X.org's Secretary, and am also a member of the CoC team. I've also been a member of X.org for multiple years now and have contributed to a plethora of various projects in the X.org/freedesktop.org/linux kernel space such as: nova, nouveau, i915, amdgpu, the wayland protocol, igt- gpu-tools, libinput, and more. I've had a pretty long tenure on the board where I've accomplished a number of cool things For instance, I restarted X.org's relationship with VESA in order to give X.org members access to various VESA specifications that they might not have access to otherwise without a prior VESA membership. I worked to help enable X.og to provide funding for professional CoC training for any X.org/freeesktop.org project that requests it, and I've assisted through the transition of parent foundations for X.org from SPI to SFC. I love working in this community, and will do my best to serve the community throughout my tenusre if re-elected to the board of directors. Harry Wentland Current Affiliation: AMD Personal Statement: I've been lucky to be paid to help improve the Linux Desktop experience on AMD HW and in that capacity align with X.Org's mission to further the state of the open-source desktop. A healthy, diverse, open-source, and general-purpose desktop provides tremendous value to many people and is a bulwark against corporate silo
Re: GL framebuffer fetch behavior
NVIDIA is a texelFetch, so (x, 0, 0, 1) Intel is a TexelFetch pre-SKL. I'm not sure what it is for SKL+. Probably (x, 0, 0, 1) but it's been a while. ~Faith On Wed, Apr 23, 2025 at 1:11 PM Marek Olšák wrote: > AMD lowers it to an image load, which follows the rules for image views, > so (x, 0, 0, 1) for R8_UNORM. > > Marek > > On Wed, Apr 23, 2025 at 12:25 PM Mike Blumenkrantz < > michael.blumenkra...@gmail.com> wrote: > >> Hi, >> >> An issue recently came up in the GL working group: what is the robustness >> behavior of framebuffer fetch? For example, if a framebuffer attachment >> format is R8_UNORM, what are the YZW components which get read back? >> >> If people from all the drivers (besides panfrost) which support this >> extension could reply with the expected behavior on their hardware, that >> would be helpful. >> >> >> Thanks, >> Mike >> >
