From: Gilles Risch <gilles.risch@gmail.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: alexander.deucher@amd.com, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/radeon: fix internal display on iMac11, 1 (RV770/DCE3.1)
Date: Sun, 17 May 2026 15:53:51 +0200 [thread overview]
Message-ID: <d5262f65-22b5-4ff3-b905-12bb2a4b587d@gmail.com> (raw)
In-Reply-To: <agiy9II5jkHEgPAq@wunner.de>
Good afternoon Lukas,
thanks for the review.
The initial launch date can either be verified in the TeraScale
architecture comparison table on Wikipedia [1] or directly in the kernel
source at drivers/gpu/drm/radeon/radeon_family.h where CHIP_RV770 (line
74) precedes CHIP_RV730 (line 75).
The test robot mentions that it cannot find ASIC_IS_DCE31(); this is
because both patches build on one another. Should I submit both patches
as a series?
Kind regards,
Gilles
On 16.05.26 20:09, Lukas Wunner wrote:
> On Sat, May 16, 2026 at 11:24:21AM +0200, Gilles Risch wrote:
>> The Apple iMac11,1 (late 2009) has an integrated ATI Mobility Radeon
>> HD 4850 (RV770/M98L) with a 2560x1440 internal panel connected via an
>> internal DisplayPort path. This machine suffers from a similar problem
>> as the iMac10,1 (late 2009) and the iMac11,2 (mid 2010). Without this
>> fix the display stays dark under KMS. Two issues are addressed:
>>
>> 1. The RV770 implements DCE3.1 and not DCE3.2. ASIC_IS_DCE32() starts at
>> CHIP_RV730 which is newer than RV770, so the RV770 never matched the
>> DCE3.2 PLL and encoder logic. Introduce ASIC_IS_DCE31() starting at
>> CHIP_RV770 to fix this.
>>
>> 2. Apple routed the internal display through Link B of the DIG encoder
>> instead of Link A, as observed in the kernel display connector log.
>> The same quirk already exists for iMac10,1 and iMac11,2 - iMac11,1
>> was simply missing from the list.
> Not an expert in the radeon driver or AMD chip revisions, but if it
> helps improve support for older Macs I'll be happy to offer my:
>
> Reviewed-by: Lukas Wunner <lukas@wunner.de>
>
> It's not immediately obvious that CHIP_RV770 precedes CHIP_RV730
> in the enum and that hence ASIC_IS_DCE31() subsumes ASIC_IS_DCE32().
>
> Thanks,
>
> Lukas
next prev parent reply other threads:[~2026-05-17 13:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 18:54 [PATCH] The Apple iMac11, 1 (late 2009) has an integrated ATI Mobility Radeon HD 4850. This machine suffers from a similar problem as the iMac10, 1 (late 2009) and the iMac11, 2 (mid 2010). This small patch fixes the issue on this machine Gilles Risch
2026-05-16 5:26 ` Claude review: " Claude Code Review Bot
2026-05-16 5:26 ` Claude Code Review Bot
2026-05-16 9:24 ` [PATCH v2] drm/radeon: fix internal display on iMac11, 1 (RV770/DCE3.1) Gilles Risch
2026-05-16 18:09 ` Lukas Wunner
2026-05-17 13:53 ` Gilles Risch [this message]
2026-05-17 14:05 ` Lukas Wunner
2026-05-18 6:36 ` Claude review: " Claude Code Review Bot
2026-05-16 18:52 ` [PATCH] drm/radeon: fix eDP resume from suspend on iMac11, 1 / DCE3.1 systems Gilles Risch
2026-05-17 3:28 ` kernel test robot
2026-05-17 5:12 ` kernel test robot
2026-05-18 6:57 ` Claude review: drm/radeon: fix internal display on iMac11, 1 (RV770/DCE3.1) Claude Code Review Bot
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=d5262f65-22b5-4ff3-b905-12bb2a4b587d@gmail.com \
--to=gilles.risch@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=lukas@wunner.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox