[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230503190317.GA422961@ravnborg.org>
Date: Wed, 3 May 2023 21:03:17 +0200
From: Sam Ravnborg <sam@...nborg.org>
To: Thomas Zimmermann <tzimmermann@...e.de>
Cc: linux-arch@...r.kernel.org, linux-fbdev@...r.kernel.org,
linux-ia64@...r.kernel.org, loongarch@...ts.linux.dev,
arnd@...db.de, deller@....de, chenhuacai@...nel.org,
javierm@...hat.com, dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org,
James.Bottomley@...senpartnership.com,
linux-m68k@...ts.linux-m68k.org, geert@...ux-m68k.org,
linux-parisc@...r.kernel.org, vgupta@...nel.org,
sparclinux@...r.kernel.org, kernel@...0n.name,
linux-snps-arc@...ts.infradead.org, davem@...emloft.net,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 5/6] fbdev: Move framebuffer I/O helpers into
<asm/fb.h>
Hi Thomas,
> > But I am missing something somewhere as I cannot see how this builds.
> > asm-generic now provide the fb_read/fb_write helpers.
> > But for example sparc has an architecture specifc fb.h so it will not
> > use the asm-generic variant. So I wonder how sparc get hold of the
> > asm-generic fb.h file?
>
> All architecture's <asm/fb.h> files include <asm-generic/fb.h>, so that they
> all get the interfaces which they don't define themselves. For Sparc, this
> is at [1].
>
> Best regards
> Thomas
>
>
> [1]
> https://cgit.freedesktop.org/drm/drm-tip/tree/arch/sparc/include/asm/fb.h#n19
>
> >
> > Maybe it is obvious, but I miss it.
OK, it was obvious and I missed it.
I looked at the mainline kernel, and not the drm-tip variant.
Sorry for the noise.
Sam
Powered by blists - more mailing lists