Skip to contentSkip to conversation

Patch "firmware: google: framebuffer: Do not mark framebuffer as busy" has been added to the 6.18-stable tree

PATCH [email protected] 1 participant 1 message Apr 27 ChromeOS EC subdrivers

lore
Share & tools
lore

[email protected]

author Applied
#0 lore raw

This is a note to let you know that I've just added the patch titled

firmware: google: framebuffer: Do not mark framebuffer as busy

to the 6.18-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
firmware-google-framebuffer-do-not-mark-framebuffer-as-busy.patch
and it can be found in the queue-6.18 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.

From f3850d399de3b6142b02315227ef9e772ed0c302 Mon Sep 17 00:00:00 2001
From: Thomas Zimmermann <[email protected]>
Date: Tue, 17 Feb 2026 16:56:12 +0100
Subject: firmware: google: framebuffer: Do not mark framebuffer as busy

From: Thomas Zimmermann <[email protected]>

commit f3850d399de3b6142b02315227ef9e772ed0c302 upstream.

Remove the flag IORESOURCE_BUSY flag from coreboot's framebuffer resource. It prevents simpledrm from successfully requesting the range for its own use; resulting in errors such as

[    2.775430] simple-framebuffer simple-framebuffer.0: [drm] could not acquire memory region [mem 0x80000000-0x80407fff flags 0x80000200]

As with other uses of simple-framebuffer, the simple-framebuffer device should only declare it's I/O resources, but not actively use them.

Fixes 851b4c14532d ("firmware: coreboot: Add coreboot framebuffer driver")
Cc Samuel Holland <[email protected]>
Cc Greg Kroah-Hartman <[email protected]>
Cc Tzung-Bi Shih <[email protected]>
Cc Brian Norris <[email protected]>
Cc Julius Werner <[email protected]>
Cc <[email protected]> # v4.18+
---
 drivers/firmware/google/framebuffer-coreboot.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/firmware/google/framebuffer-coreboot.c +1 -1
@@ -67,7 +67,7 @@ static int framebuffer_probe(struct core
 		return -ENODEV;
 
 	memset(&res, 0, sizeof(res));
-	res.flags = IORESOURCE_MEM | IORESOURCE_BUSY;
+	res.flags = IORESOURCE_MEM;
 	res.name = "Coreboot Framebuffer";
 	res.start = fb->physical_address;
 	length = PAGE_ALIGN(fb->y_resolution * fb->bytes_per_line);

Patches currently in stable-queue which might be from [email protected] are

queue-6.18/drm-nouveau-fix-u32-overflow-in-pushbuf-reloc-bounds-check.patch queue-6.18/firmware-google-framebuffer-do-not-mark-framebuffer-as-busy.patch