public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: request: bring back framebuffer
Date: Mon, 04 Apr 2022 10:03:11 +0100	[thread overview]
Message-ID: <A6109C7D-E90A-46DE-B20B-CE5901DAB478@ipfire.org> (raw)
In-Reply-To: <CAGGyJTpEgmbXtvb42FheYM0395xv7Z=mdEfAXWU5rk2HpNQBxA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]

Hello Paul,

I don’t think we would bring back framebuffer.

This is very outdated technology and difficult to use and configure, especially when you want to rely on auto-configuration.

The point is not that it increases size of the image. The modules are all still there; the kernel is only configured to not load them.

If you want a higher resolution you should be looking at DRM which more modern and should automatically detect the correct resolution automatically.

The modules are all there. They are just not loaded and blacklisted together with the framebuffer modules.

-Michael

> On 3 Apr 2022, at 16:04, paul kairis <kairis(a)gmail.com> wrote:
> 
> Re: https://community.ipfire.org/t/increase-monitor-resolution/6205/23
> 
> At times, when I go to customer sites, all I can access is the ipfire console with a wide monitor 1920x1080. In the past I was able to modify GRUB and increase resolution so I can see messages as wide as possible. I brought up the issue to the Community site and was told framebuffer was removed on cu157 (it existed in cu156). It would be a waste to lose all that work that someone did in cu156. And I doubt it adds many MB to the core system. So my request is to bring back the framebuffer capability. 
> Thank you, Paul
> 
> 


           reply	other threads:[~2022-04-04  9:03 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAGGyJTpEgmbXtvb42FheYM0395xv7Z=mdEfAXWU5rk2HpNQBxA@mail.gmail.com>]

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=A6109C7D-E90A-46DE-B20B-CE5901DAB478@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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