Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Michael Schmitz <schmitzmic@gmail.com>,
	linux-m68k@vger.kernel.org, geert@linux-m68k.org
Cc: Miro Kropacek <miro.kropacek@gmail.com>, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v2 2/5] fbdev: Give atafb proper parent
Date: Mon, 17 Aug 2026 09:57:58 +0200	[thread overview]
Message-ID: <3347106a-f0f9-415a-94e4-94bc9b8182ef@suse.de> (raw)
In-Reply-To: <5a2d0139-84db-cab8-c7fb-7806a71c53b2@gmail.com>



Am 17.08.26 um 09:49 schrieb Michael Schmitz:
> Hi Thomas,
>
> Am 17.08.2026 um 18:34 schrieb Thomas Zimmermann:
>> Hi
>>
>> Am 16.08.26 um 09:37 schrieb Michael Schmitz:
>>> From: Miro Kropacek <miro.kropacek@gmail.com>
>>>
>>> The atafb fb device registers no parent, causing a missing symlink
>>> (/sys/class/graphics/fb0/device). Xorg fbdevhw driver looks for that
>>> symlink when scanning for devices, so add a parent node for atafb.
>>
>> Do you really have these devices to test with?
>
> Not the particular hardware that patches 3 and 4 add support for, but 
> the 'normal' Videl that is found in every Falcon, yes.
>
>> If so, could you also replace the hard coded fb_info with a call to
>> framebuffer_alloc()?
>
> Can't see how that would work - fb_info isn't passed to all functions 
> that need to use it, especially in the hardware detection phase (hence 
> the use of a static fb_info struct)?

You'd have to modify the driver to pass the allocated instance, of 
course. It's not a trivial oneliner, but if this driver is still 
relevant, it might be worth improving it.

Best regards
Thomas

>
> Cheers,
>
>     Michael
>
>>>
>>> Signed-off-by: Miro Kropacek <miro.kropacek@gmail.com>
>>> Reviewed-by: Michael Schmitz <schmitzmic@gmail.com>
>>> Signed-off-by: Michael Schmitz <schmitzmic@gmail.com>
>>> Cc: <linux-fbdev@vger.kernel.org>
>>> Link: https://lists.debian.org/debian-68k/2026/08/msg00000.html
>>> ---
>>>   drivers/video/fbdev/atafb.c | 5 +++++
>>>   1 file changed, 5 insertions(+)
>>>
>>> diff --git a/drivers/video/fbdev/atafb.c b/drivers/video/fbdev/atafb.c
>>> index b8ed1c537293..3d540803dc2b 100644
>>> --- a/drivers/video/fbdev/atafb.c
>>> +++ b/drivers/video/fbdev/atafb.c
>>> @@ -3101,6 +3101,11 @@ static int __init atafb_probe(struct
>>> platform_device *pdev)
>>>   #endif /* ATAFB_EXT */
>>>     //    strcpy(fb_info.mode->name, "Atari Builtin ");
>>> +    /* Parent the fb device properly: without this fb0 registers as a
>>> +     * virtual sysfs device with no /sys/class/graphics/fb0/device 
>>> link,
>>> +     * which makes Xorg's fbdevhw reject it ("No devices detected").
>>> +     */
>>> +    fb_info.device = &pdev->dev;
>>
>> Because this is supposed to happen in framebuffer_alloc() and keeping it
>> there would be preferable.
>>
>> Best regards
>> Thomas
>>
>>>       fb_info.fbops = &atafb_ops;
>>>       // try to set default (detected; requested) var
>>>       do_fb_set_var(&atafb_predefined[default_par - 1], 1);
>>
>

-- 
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Jochen Jaser, Andrew McDonald, (HRB 36809, AG Nürnberg)



  reply	other threads:[~2026-08-17  7:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260816073752.16656-1-schmitzmic@gmail.com>
2026-08-16  7:37 ` [PATCH v2 2/5] fbdev: Give atafb proper parent Michael Schmitz
2026-08-16 14:38   ` Helge Deller
2026-08-16 18:37     ` Michael Schmitz
2026-08-17  6:34   ` Thomas Zimmermann
2026-08-17  7:49     ` Michael Schmitz
2026-08-17  7:57       ` Thomas Zimmermann [this message]
2026-08-16  7:37 ` [PATCH v2 3/5] fbdev: Add support for further video bit depths on atafb:external Michael Schmitz
2026-08-16  7:37 ` [PATCH v2 4/5] fbdev: Add support for SuperVidel's SuperBlitter Michael Schmitz

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=3347106a-f0f9-415a-94e4-94bc9b8182ef@suse.de \
    --to=tzimmermann@suse.de \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=miro.kropacek@gmail.com \
    --cc=schmitzmic@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox