From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Michal Januszewski <spock@gentoo.org>,
linux-fbdev@vger.kernel.org,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uvesafb: make scaling configurable on Nvidia cards
Date: Thu, 08 Oct 2015 12:21:31 +0000 [thread overview]
Message-ID: <56165FCB.30504@ti.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1510080744170.20879@file01.intranet.prod.int.rdu2.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]
On 08/10/15 14:51, Mikulas Patocka wrote:
>> I have to say I don't know much about x86 video, but isn't uvesafb
>> supposed to be a generic driver? Adding nvidia specific features there
>> doesn't sound like a right way to handle this.
>>
>> Tomi
>
> Where do you think that this functionality should be added? To Nouveau? -
> Nouveau can't be used with nVidia binary driver, and this functionality is
> useful especially with nVidia binary driver (it allows to get nice console
> with sharp fonts).
I don't know where is should be. But with a quick look I don't see any
gfx card specific features in uvesafb, and the doc clearly says it's a
generic driver. So if we add this nvidia feature there, shall we add
other features for other cards also? It's a kind of slippery road.
So how does uvesafb work with nvidia driver? uvesafb is used for initial
console, and nvidia driver takes over later when (and if) it's loaded?
And it's not possible to change the scaling via nvidia's driver?
> BTW. I don't know if this BIOS function is supported on AMD or not. Could
> someone try it? I don't have an AMD card.
Quick googling shows that 0x4f14 might be used by other gfx cards (Epia)
for something else. But I can't really say for sure. So in the minimum I
think the parameter should be renamed to "nvidia_scaling" or similar.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-10-08 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 6:56 [PATCH] uvesafb: make scaling configurable on Nvidia cards Mikulas Patocka
2015-09-02 21:23 ` Mikulas Patocka
2015-10-08 9:31 ` Tomi Valkeinen
2015-10-08 11:51 ` Mikulas Patocka
2015-10-08 12:21 ` Tomi Valkeinen [this message]
2015-10-08 13:55 ` Mikulas Patocka
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=56165FCB.30504@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=plagnioj@jcrosoft.com \
--cc=spock@gentoo.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;
as well as URLs for NNTP newsgroup(s).