All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: make fbdev/fbcon switchable per driver?
Date: Mon, 30 Jan 2017 09:15:50 +0100	[thread overview]
Message-ID: <1485764150.20455.11.camel@redhat.com> (raw)
In-Reply-To: <20170127113019.6621b1b5@t450s.home>

  Hi,

> The vgaarb code has a concept of a vga_default_device(), it's rather
> PCI-centric, but maybe better than nothing.  This is typically the
> first VGA class code device found with I/O and MMIO enabled.  If fbcon
> defaulted to running on the vga_default_device(), a user could select
> which to use by re-ordering the VM hardware.

The qemu drivers don't register as vgaarb clients though.  Which easily
explains why igd always wins the primary selection, no matter how you
order your hardware.

So, should they register?  The drivers don't need access to the vga
registers[1][2].

cheers,
  Gerd

[1] Well, except cirrus, but that is deprecated anyway.
[2] And bochs-drm, when running on old qemu versions, where the
    stdvga has no mmio bar yet.  But those qemu versions don't
    support igd pass-through.

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-01-30  8:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-27 10:00 make fbdev/fbcon switchable per driver? Gerd Hoffmann
2017-01-27 14:02 ` Daniel Vetter
2017-01-27 14:41   ` Liviu Dudau
2017-01-27 18:30 ` Alex Williamson
2017-01-30  8:15   ` Gerd Hoffmann [this message]
2017-01-30 17:45     ` Alex Williamson
2017-01-31  8:00       ` Daniel Vetter
2017-01-31 10:06         ` Gerd Hoffmann

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=1485764150.20455.11.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.