From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2306D3DB65C; Mon, 27 Apr 2026 17:01:02 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777309262; cv=none; b=m84MHfgIE3Fn/sQa+47RwN4xGKgaZkwN+1qXmzkvtkbcUhatVBF5fb14ByAD6xBu2ybrt2DqKLJh3ydHBAEMIRnpmDDv4pq3LJMVrVGgQ7vTcOwLM2ioJ8k7f49ZzPXjBHw0lkzNl8QzsIbSAbqtAf8Gn+c+lXSk85h8JRU8Zv8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777309262; c=relaxed/simple; bh=MDezOQfGi5YWLGCvaBHDrWq4RWp+885pPaMUQ9kzAog=; h=Subject:To:Cc:From:Date:Message-ID:MIME-Version:Content-Type; b=cOowwxKDfm+/RBVx0u1IRGk08EPObcLtY2rGk4nUxeOm2hneMehAKKfK/PEt28LDNIBFxRsFwIIEQP87az6zVw8BwrglShw/C1S0Jeyj1t877o1J/62ykqeOI06RCraEOVHBpv28RwkwSARhtSNaWRuJMYYbfWjkz2wZAiF6yZE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=k5p0jy6i; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="k5p0jy6i" Received: by smtp.kernel.org (Postfix) with ESMTPSA id CCB07C19425; Mon, 27 Apr 2026 17:01:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1777309262; bh=MDezOQfGi5YWLGCvaBHDrWq4RWp+885pPaMUQ9kzAog=; h=Subject:To:Cc:From:Date:From; b=k5p0jy6iHYyJn+uhA2NsuwDxIS5AZgkR+Bu7vT94yminPrgk6OGbZGJBzzX5vAM2v YFF39DqKncR8gFeaqXRHk8ZTByocIHd7P6ME/Zby0onQqFGxAzceISJEIDMxbBYdx6 XKHxiouqhPikzEIlQvJx491Io1TwoQE6fhYrlMbo= Subject: Patch "firmware: google: framebuffer: Do not mark framebuffer as busy" has been added to the 6.18-stable tree To: briannorris@chromium.org,chrome-platform@lists.linux.dev,gregkh@linuxfoundation.org,jwerner@chromium.org,samuel@sholland.org,tzimmermann@suse.de,tzungbi@kernel.org Cc: From: Date: Mon, 27 Apr 2026 10:55:03 -0600 Message-ID: <2026042703-blurb-suffice-bda0@gregkh> Precedence: bulk X-Mailing-List: chrome-platform@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=ANSI_X3.4-1968 Content-Transfer-Encoding: 8bit X-stable: commit X-Patchwork-Hint: ignore 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 know about it. >From f3850d399de3b6142b02315227ef9e772ed0c302 Mon Sep 17 00:00:00 2001 From: Thomas Zimmermann Date: Tue, 17 Feb 2026 16:56:12 +0100 Subject: firmware: google: framebuffer: Do not mark framebuffer as busy From: Thomas Zimmermann 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. Signed-off-by: Thomas Zimmermann Fixes: 851b4c14532d ("firmware: coreboot: Add coreboot framebuffer driver") Acked-by: Tzung-Bi Shih Acked-by: Julius Werner Cc: Samuel Holland Cc: Greg Kroah-Hartman Cc: Tzung-Bi Shih Cc: Brian Norris Cc: Julius Werner Cc: chrome-platform@lists.linux.dev Cc: # v4.18+ Link: https://patch.msgid.link/20260217155836.96267-3-tzimmermann@suse.de Signed-off-by: Greg Kroah-Hartman --- drivers/firmware/google/framebuffer-coreboot.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/drivers/firmware/google/framebuffer-coreboot.c +++ b/drivers/firmware/google/framebuffer-coreboot.c @@ -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 tzimmermann@suse.de 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