public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Mikulas Patocka <mpatocka@redhat.com>,
	Michal Januszewski <spock@gentoo.org>
Cc: <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, 8 Oct 2015 12:31:50 +0300	[thread overview]
Message-ID: <56163806.40608@ti.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1509021719170.12073@file01.intranet.prod.int.rdu2.redhat.com>

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


On 03/09/15 00:23, Mikulas Patocka wrote:
> [ I sent this some times ago, but didn't get any response ]
> 
> 
> Nvidia cards have a BIOS function 0x4f14 that allows to set flat panel
> scaling. This patch adds a module parameter "scaling" that uses this
> function to set the scaling. By default, the parameter is -1, so that the
> driver doesn't attempt to call the scaling function.
> 
> This patch is useful when using the binary Nvidia graphics driver - in
> that case, the console may be only in text mode or VESA mode. By default,
> the video card does scaling that degrades font quality and changes aspect
> ratio. This patch makes it possible to turn off the scaling and improve
> font quality on the console.
> 
> The allowed values depend on VESA BIOS. On my card, the following values
> are allowed:
> -1	- do not change the scaling
> 0	- scale to full screen
> 1, 2	- don't scale
> 3	- scale and preserve aspect ratio
> 4	- scale with black border around
> 
> Example use:
> echo 1 >/sys/module/uvesafb/parameters/scaling; fbset 1280x1024-60 -depth 32 -a
> - this sets unscaled 1280x1024 video mode that has much sharper font than
>   the scaled modes.

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


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-10-08  9:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02 21:23 [PATCH] uvesafb: make scaling configurable on Nvidia cards Mikulas Patocka
2015-10-08  9:31 ` Tomi Valkeinen [this message]
2015-10-08 11:51   ` Mikulas Patocka
2015-10-08 12:21     ` Tomi Valkeinen
2015-10-08 13:55       ` Mikulas Patocka
  -- strict thread matches above, loose matches on Subject: below --
2015-05-17  6:56 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=56163806.40608@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