From: Harry Putnam <reader@newsguy.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Is Vesa/Uvesa still the way for Frame buffer
Date: Fri, 02 Aug 2013 11:45:55 -0400 [thread overview]
Message-ID: <8738qsw0y4.fsf@newsguy.com> (raw)
Maybe a poorly worded question but I seem to recall some advances
where framebuffering is being handled differently than my old way.
It could be typified by the kernel line used in grub.conf like this
one:
kernel /vmlinuz root=/dev/sdb3 vga=0x31A video=vesafb:mtrr,ywrap
Or is that still a viable way to setup the framebuffer, and, of course,
making the proper Vesa and /or Uvesa choices at compile time.
OK, that leads into a second or related part to this question; I'm
having a heck of a time finding the uvesa setting in menuconfig.
A searched for 'vesa', using '/'. Output below. But I'm not finding
anything about 'UVESA' at that location.
I see, under the 'Type' line that they appear to either designate
'boolean' or 'Tristate' I know what boolean means in general but not
how to apply it here... But have no idea what Type: 'Tristate' might
mean.
I've really scrutinized that area of menuconfig... but not finding any
way to say 'y' to FB_UVESA
│ Symbol: FB_VESA [=y] │
│ Type : boolean │
│ Prompt: VESA VGA graphics support │
│ Defined at drivers/video/Kconfig:755 │
│ Depends on: HAS_IOMEM [=y] && FB [=y]=y && X86 [=y] │
│ Location: │
│ -> Device Drivers │
│ -> Graphics support │
│ (1) -> Support for frame buffer devices (FB [=y]) │
│ Selects: FB_CFB_FILLRECT [=y] && FB_CFB_COPYAREA [=y] && |
| FB_CFB_IMAGEBLIT [=y] && FB_BOOT_VE │
│ │
│ │
│ Symbol: FB_UVESA [=n] │
│ Type : tristate │
│ Prompt: Userspace VESA VGA graphics support │
│ Defined at drivers/video/Kconfig:737 │
│ Depends on: HAS_IOMEM [=y] && FB [=y] && CONNECTOR [=n] │
│ Location: │
│ -> Device Drivers │
│ -> Graphics support │
│ (2) -> Support for frame buffer devices (FB [=y]) │
│ Selects: FB_CFB_FILLRECT [=y] && FB_CFB_COPYAREA [=y] && |
| FB_CFB_IMAGEBLIT [=y] && FB_MODE_HE │
│ │
│ │
│ Symbol: FB_BOOT_VESA_SUPPORT [=y] │
│ Type : boolean │
│ Selected by: FB_VESA [=y] && HAS_IOMEM [=y] && FB [=y]=y && |
| X86 [=y] || FB_INTEL [=n] && HAS │
next reply other threads:[~2013-08-02 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 15:45 Harry Putnam [this message]
2013-08-02 15:53 ` [gentoo-user] Is Vesa/Uvesa still the way for Frame buffer Canek Peláez Valdés
2013-08-02 16:01 ` [gentoo-user] " Harry Putnam
2013-08-02 15:56 ` [gentoo-user] " Bruce Hill
2013-08-02 15:57 ` [gentoo-user] " Harry Putnam
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=8738qsw0y4.fsf@newsguy.com \
--to=reader@newsguy.com \
--cc=gentoo-user@lists.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