From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: pengfuyuan <pengfuyuan@kylinos.cn>
Cc: "Danilo Krummrich" <dakr@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Rafael J . Wysocki" <rafael@kernel.org>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>, "Helge Deller" <deller@gmx.de>,
"Hans de Goede" <hansg@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Lee Jones" <lee@kernel.org>, "Sam Ravnborg" <sam@ravnborg.org>,
"Zsolt Kajtar" <soci@c64.rulez.org>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v1 v1 0/4] [RUST] Framebuffer driver support
Date: Mon, 26 Jan 2026 11:32:40 +0100 [thread overview]
Message-ID: <2026012627-uncut-plaything-759e@gregkh> (raw)
In-Reply-To: <20260126081744.781392-1-pengfuyuan@kylinos.cn>
On Mon, Jan 26, 2026 at 04:17:40PM +0800, pengfuyuan wrote:
> This series has been tested on:
> - ARM64 platforms with various display configurations
> - AMD RX550 graphics card
> - Moore Threads S30 graphics card
> - Multiple other graphics cards
How? If there is no rust framebuffer drivers for those hardware
platforms, how exactly were these new codepaths tested?
> All tested configurations show normal display functionality with proper
> framebuffer initialization, rendering operations (including I/O, color register
> management, and blitting), memory mapping, and resource cleanup. The simplefb
> test driver successfully demonstrates the usage of all framebuffer framework
> APIs and validates the abstraction's correctness.
Really? Where are the drivers for this? Or did simplefb really work
for all of them?
confused,
greg k-h
next prev parent reply other threads:[~2026-01-26 10:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 8:17 [PATCH v1 v1 0/4] [RUST] Framebuffer driver support pengfuyuan
2026-01-26 8:17 ` [PATCH v1 v1 1/4] rust: io: mem: add ioremap_wc support pengfuyuan
2026-01-26 8:17 ` [PATCH v1 v1 2/4] rust: device: add platdata accessors pengfuyuan
2026-01-26 8:17 ` [PATCH v1 v1 3/4] rust: fb: add framebuffer driver support pengfuyuan
2026-01-26 22:29 ` kernel test robot
2026-01-26 8:17 ` [PATCH v1 v1 4/4] rust: fb: add simplefb test driver pengfuyuan
2026-01-26 10:01 ` [PATCH v1 v1 0/4] [RUST] Framebuffer driver support Thomas Zimmermann
2026-01-26 10:28 ` Alexandre Courbot
2026-01-26 11:46 ` Miguel Ojeda
2026-01-27 8:30 ` pengfuyuan
2026-01-27 8:04 ` pengfuyuan
2026-01-27 8:16 ` Helge Deller
2026-01-27 8:58 ` pengfuyuan
2026-01-27 9:35 ` Greg Kroah-Hartman
2026-01-27 9:38 ` Helge Deller
2026-01-28 14:55 ` Alexandre Courbot
2026-01-26 12:27 ` Helge Deller
2026-01-26 10:32 ` Greg Kroah-Hartman [this message]
2026-01-26 12:15 ` Miguel Ojeda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026012627-uncut-plaything-759e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=a.hindborg@kernel.org \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=hansg@kernel.org \
--cc=lee@kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=pengfuyuan@kylinos.cn \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=simona@ffwll.ch \
--cc=soci@c64.rulez.org \
--cc=tmgross@umich.edu \
--cc=tzimmermann@suse.de \
--cc=ville.syrjala@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.