linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
	Salvatore Bonaccorso <carnil@debian.org>,
	Cyril Brulebois <cyril@debamax.com>
Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org, stable@vger.kernel.org,
	Michal Suchanek <msuchanek@suse.de>
Subject: Re: [PATCH 1/2] fbdev/offb: Update expected device name
Date: Thu, 15 Jun 2023 15:06:28 +0200	[thread overview]
Message-ID: <fe3b90b0-b52f-9677-0245-a201975c3e0c@suse.de> (raw)
In-Reply-To: <11b342dc-1a46-d1be-5fdd-c6eee661e15a@leemhuis.info>


[-- Attachment #1.1: Type: text/plain, Size: 2137 bytes --]

Hi

Am 15.06.23 um 15:03 schrieb Linux regression tracking (Thorsten Leemhuis):
> On 16.04.23 14:34, Salvatore Bonaccorso wrote:
>>
>> On Wed, Apr 12, 2023 at 11:55:08AM +0200, Cyril Brulebois wrote:
>>> Since commit 241d2fb56a18 ("of: Make OF framebuffer device names unique"),
>>> as spotted by Frédéric Bonnard, the historical "of-display" device is
>>> gone: the updated logic creates "of-display.0" instead, then as many
>>> "of-display.N" as required.
>>>
>>> This means that offb no longer finds the expected device, which prevents
>>> the Debian Installer from setting up its interface, at least on ppc64el.
>>>
>>> It might be better to iterate on all possible nodes, but updating the
>>> hardcoded device from "of-display" to "of-display.0" is confirmed to fix
>>> the Debian Installer at the very least.
>> [...]
>> #regzbot ^introduced 241d2fb56a18
>> #regzbot title: Open Firmware framebuffer cannot find of-display
>> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=217328
>> #regzbot link: https://lore.kernel.org/all/20230412095509.2196162-1-cyril@debamax.com/T/#m34493480243a2cad2ae359abfd9db5e755f41add
>> #regzbot link: https://bugs.debian.org/1033058
> 
> No reply to my status inquiry[1] a few weeks ago, so I have to assume
> nobody cares anymore. If somebody still cares, holler!

I'd take a look if anyone can point me to an example of Geert's proposal.

Best regards
Thomas

> 
> #regzbot inconclusive: no answer to a status inquiry
> #regzbot ignore-activity
> 
> [1]
> https://lore.kernel.org/lkml/d1aee7d3-05f6-0920-b8e1-4ed5cf3f9f70@leemhuis.info/
> 
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> If I did something stupid, please tell me, as explained on that page.

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2023-06-15 13:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12  9:55 Updating hardcoded "of-display" devices Cyril Brulebois
2023-04-12  9:55 ` [PATCH 1/2] fbdev/offb: Update expected device name Cyril Brulebois
2023-04-16 12:34   ` Salvatore Bonaccorso
2023-06-15 13:03     ` Linux regression tracking (Thorsten Leemhuis)
2023-06-15 13:06       ` Thomas Zimmermann [this message]
2023-06-15 13:21         ` Michal Suchánek
2023-06-15 20:09           ` Rob Herring
2023-06-15 21:19             ` Cyril Brulebois
2023-06-20  6:24               ` Helge Deller
2023-06-20  8:04                 ` Michal Suchánek
2023-06-15 13:12       ` Cyril Brulebois
2023-04-22  9:50   ` Helge Deller
2023-04-24  7:31   ` Geert Uytterhoeven
2023-07-10 16:36   ` Michal Suchánek
2023-04-12  9:55 ` [PATCH 2/2] drm/ofdrm: " Cyril Brulebois
2023-04-24  7:33   ` Geert Uytterhoeven
2023-04-24  9:07     ` Thomas Zimmermann
2023-04-24  9:35       ` Helge Deller
2023-05-22  9:37         ` Linux regression tracking (Thorsten Leemhuis)
2023-05-22 11:44       ` Michal Suchánek
2023-07-10 16:36   ` Michal Suchánek

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=fe3b90b0-b52f-9677-0245-a201975c3e0c@suse.de \
    --to=tzimmermann@suse.de \
    --cc=carnil@debian.org \
    --cc=cyril@debamax.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msuchanek@suse.de \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).