From: Imre Kaloz <kaloz@kernel.org>
To: "Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>
Cc: David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] drm/radeon: Sun XVR-300 support on sparc64
Date: Sun, 27 Sep 2026 16:55:03 +0200 [thread overview]
Message-ID: <20260927145505.16883-1-kaloz@kernel.org> (raw)
These two patches get radeon KMS working on the Sun XVR-300, a
FireMV 2200 PCIe (RV370) board, in sparc64 hosts.
Patch 1 fixes an Oops that any posted radeon card on sparc64 hits in
igp_read_bios_from_vram(), which dereferences an ioremap() cookie to
check the VBIOS signature. It is tagged for stable.
Patch 2 adds a legacy connector table for the XVR-300, which has no
COMBIOS for the driver to parse, so both DVI-I outputs are found.
The XVR-300 needs both.
Tested on a Sun Ultra 45 with an XVR-300.
Changes in v2:
- Read the signature with readb() before the allocation instead of
checking the RAM copy, as radeon_read_bios() does (patch 1).
Imre Kaloz (2):
drm/radeon: Read the VRAM VBIOS signature with readb()
drm/radeon: add a connector table for the Sun XVR-300
drivers/gpu/drm/radeon/radeon_bios.c | 6 ++-
drivers/gpu/drm/radeon/radeon_combios.c | 51 +++++++++++++++++++++++++
drivers/gpu/drm/radeon/radeon_mode.h | 3 +-
3 files changed, 58 insertions(+), 2 deletions(-)
base-commit: fe2ec83746e501645709761605c2464a44fd2929
--
2.47.3
next reply other threads:[~2026-09-27 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 14:55 Imre Kaloz [this message]
2026-09-27 14:55 ` [PATCH v2 1/2] drm/radeon: Read the VRAM VBIOS signature with readb() Imre Kaloz
2026-09-27 14:55 ` [PATCH v2 2/2] drm/radeon: add a connector table for the Sun XVR-300 Imre Kaloz
2026-09-27 19:26 ` [PATCH v2 0/2] drm/radeon: Sun XVR-300 support on sparc64 Alex Deucher
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=20260927145505.16883-1-kaloz@kernel.org \
--to=kaloz@kernel.org \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simona@ffwll.ch \
/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.