unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Bengt Richter <bokr@bokr.com>
Cc: 40538@debbugs.gnu.org
Subject: bug#40538: installer: Support uvesafb to install on machines without KMS.
Date: Sun, 12 Apr 2020 10:56:21 +0200	[thread overview]
Message-ID: <20200412085621.5pzvrgs3rg3mvrsy@pelzflorian.localdomain> (raw)
In-Reply-To: <20200412063702.GA4097@LionPure>

On Sun, Apr 12, 2020 at 08:37:02AM +0200, Bengt Richter wrote:
> Did you mean s/ksmcon/kmscon/ ?

Yes.


> If that is a descendant of David Herrmann's work,
> I wonder if it wouldn't just look for /sys/class/drm/card0 and, if found,
> ignore /dev/fb0 and the uvesafb (along with the latter's user stuff requirements).
> […]
> I had thought that some version of Wayland/weston had a back end that
> could run on plain /dev/fb0, and if so could provide Xwayland for X11 clients.
> 
> Of course, if /sys/class/drm/card0 is available, Wayland will prefer that,
> and you're home free for all kinds of GUIs.

Well only with uvesafb I get a /dev/fb0 device and with /dev/fb0 I can
use xf86-video-fbdev or kmscon.  It seems kmscon has multiple
backends, I do not know if it can work in other ways, but by default
it does not work without uvesafb.

Regards,
Florian

  parent reply	other threads:[~2020-04-12  8:57 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10 12:54 bug#40538: installer: Support uvesafb to install on machines without KMS pelzflorian (Florian Pelz)
2020-04-10 14:38 ` Ludovic Courtès
2020-04-10 14:58   ` pelzflorian (Florian Pelz)
2020-04-12  6:37     ` Bengt Richter
2020-04-12  8:35       ` Bengt Richter
2020-04-12  8:56       ` pelzflorian (Florian Pelz) [this message]
2020-04-11 18:43   ` pelzflorian (Florian Pelz)
2020-04-11 19:03     ` pelzflorian (Florian Pelz)
2020-04-11 20:59     ` Ludovic Courtès
2020-04-11 21:11       ` Efraim Flashner
2020-04-12  9:23         ` pelzflorian (Florian Pelz)
2020-04-12 14:28           ` Ludovic Courtès
2020-04-12 18:33             ` pelzflorian (Florian Pelz)
2020-04-12  9:02       ` pelzflorian (Florian Pelz)
2020-04-12 11:24         ` pelzflorian (Florian Pelz)
2020-04-12 12:33           ` pelzflorian (Florian Pelz)
2020-04-12 14:48           ` Mathieu Othacehe
2020-04-12 15:30             ` pelzflorian (Florian Pelz)
2020-04-12 17:48               ` Bengt Richter
2020-04-12 18:11                 ` pelzflorian (Florian Pelz)
2020-04-13  5:00                   ` Bengt Richter
2020-04-13  5:37                     ` pelzflorian (Florian Pelz)
2020-04-14  8:57                       ` pelzflorian (Florian Pelz)
2020-04-14  7:24               ` Mathieu Othacehe
2020-04-14  8:16                 ` pelzflorian (Florian Pelz)
2020-04-14  8:34                   ` pelzflorian (Florian Pelz)
2020-04-14 10:09                   ` Ludovic Courtès
2020-04-14 10:28                     ` pelzflorian (Florian Pelz)
2020-04-14 13:14                       ` pelzflorian (Florian Pelz)
2020-04-14 14:12                         ` Ludovic Courtès
2020-04-14 17:09                         ` Mathieu Othacehe
2020-04-14 21:31                           ` pelzflorian (Florian Pelz)

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200412085621.5pzvrgs3rg3mvrsy@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=40538@debbugs.gnu.org \
    --cc=bokr@bokr.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).