Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>,
	linux-kernel@vger.kernel.org, "Helge Deller" <deller@gmx.de>,
	linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	linux-mips@vger.kernel.org
Subject: Re: [RFC PATCH] fbdev: maxinefb: fix build issues
Date: Thu, 13 Aug 2026 19:14:17 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2608131908450.48788@angie.orcam.me.uk> (raw)
In-Reply-To: <7282ae0f-3bf5-4eb8-9585-04635de0084a@infradead.org>

On Sun, 9 Aug 2026, Randy Dunlap wrote:

> >> --- linux-next-20260807.orig/include/video/maxinefb.h
> >> +++ linux-next-20260807/include/video/maxinefb.h
> >> @@ -13,13 +13,13 @@
> >>   /*
> >>    * IMS332 video controller register base address
> >>    */
> >> -#define MAXINEFB_IMS332_ADDRESS        KSEG1ADDR(0x1c140000)
> >> +#define MAXINEFB_IMS332_ADDRESS        CKSEG1ADDR(0x1c140000)
> >>     /*
> >>    * Begin of DECstation 5000/xx onboard framebuffer memory, default resolution
> >>    * is 1024x768x8
> >>    */
> >> -#define DS5000_xx_ONBOARD_FBMEM_START    KSEG1ADDR(0x0a000000)
> >> +#define DS5000_xx_ONBOARD_FBMEM_START    CKSEG1ADDR(0x0a000000)
> > 
> > The change looks correct, but clearly this has never been tested
> > on a 64-bit DECstation, so I'm not sure having this code being
> > now built is an improvement.

 I don't expect any issues and FWIW the Maxine does support a 64-bit CPU 
module.

> > diff --git a/drivers/video/fbdev/Kconfig b/drivers/video/fbdev/Kconfig
> > index ac9ac4287c6a..ff17afe6b8b3 100644
> > --- a/drivers/video/fbdev/Kconfig
> > +++ b/drivers/video/fbdev/Kconfig
> > @@ -1436,7 +1436,7 @@ config FB_PMAGB_B
> > 
> >  config FB_MAXINE
> >         bool "Maxine (Personal DECstation) onboard framebuffer support"
> > -       depends on (FB = y) && MACH_DECSTATION
> > +       depends on (FB = y) && MACH_DECSTATION && 32BIT
> >         select FB_IOMEM_HELPERS
> >         help
> >           Support for the onboard framebuffer (1024x768x8) in the Personal
> > ---
> > 
> > ?
> 
> I guess I'm OK with that. I'm even OK with removing the driver completely.

 No need to limit the driver to 32BIT and as I suggest in the other reply 
fixing 64BIT will best be a separate change.

> Maciej did say in https://lore.kernel.org/all/alpine.DEB.2.21.2308152255080.8596@angie.orcam.me.uk/
> that: "the proper way would be by using `ioremap' really.  I'll make a patch."
> [That was 15.Aug.2023.]

 Even more properly this will best be converted to a platform device and 
then resource handling will DTRT.  I do hope to get a specimen eventually, 
so I think there's no need to rush making changes on paper.

  Maciej

  reply	other threads:[~2026-08-13 18:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-09 23:48 [RFC PATCH] fbdev: maxinefb: fix build issues Randy Dunlap
     [not found] ` <20260810000251.55AD61F000E9@smtp.kernel.org>
2026-08-10  0:27   ` Randy Dunlap
2026-08-14  2:46     ` Randy Dunlap
2026-08-10  3:24 ` Philippe Mathieu-Daudé
2026-08-10  3:29   ` Randy Dunlap
2026-08-13 18:14     ` Maciej W. Rozycki [this message]
2026-08-13 16:11 ` Helge Deller
2026-08-13 18:16   ` Maciej W. Rozycki
2026-08-13 20:52     ` Helge Deller
2026-08-13 17:31 ` Maciej W. Rozycki
2026-08-13 21:46   ` Randy Dunlap

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=alpine.DEB.2.21.2608131908450.48788@angie.orcam.me.uk \
    --to=macro@orcam.me.uk \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=philmd@oss.qualcomm.com \
    --cc=rdunlap@infradead.org \
    --cc=tsbogend@alpha.franken.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