public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-user] Is Vesa/Uvesa still the way for Frame buffer
@ 2013-08-02 15:45 Harry Putnam
  2013-08-02 15:53 ` Canek Peláez Valdés
                   ` (2 more replies)
  0 siblings, 3 replies; 5+ messages in thread
From: Harry Putnam @ 2013-08-02 15:45 UTC (permalink / raw
  To: gentoo-user

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                              │



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [gentoo-user] Is Vesa/Uvesa still the way for Frame buffer
  2013-08-02 15:45 [gentoo-user] Is Vesa/Uvesa still the way for Frame buffer Harry Putnam
@ 2013-08-02 15:53 ` 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
  2 siblings, 1 reply; 5+ messages in thread
From: Canek Peláez Valdés @ 2013-08-02 15:53 UTC (permalink / raw
  To: gentoo-user

On Fri, Aug 2, 2013 at 10:45 AM, Harry Putnam <reader@newsguy.com> wrote:
> 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                              │

First:

/usr/src/linux/Documentation/fb/uvesafb.txt

Second: what card do you use?

Regards.
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [gentoo-user] Is Vesa/Uvesa still the way for Frame buffer
  2013-08-02 15:45 [gentoo-user] Is Vesa/Uvesa still the way for Frame buffer Harry Putnam
  2013-08-02 15:53 ` Canek Peláez Valdés
@ 2013-08-02 15:56 ` Bruce Hill
  2013-08-02 15:57 ` [gentoo-user] " Harry Putnam
  2 siblings, 0 replies; 5+ messages in thread
From: Bruce Hill @ 2013-08-02 15:56 UTC (permalink / raw
  To: gentoo-user

On Fri, Aug 02, 2013 at 11:45:55AM -0400, Harry Putnam wrote:
> 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                              │

It depends upon which video driver you use. Most of them now use KMS. Start
reading https://wiki.gentoo.org/wiki/Xorg/Configuration and if you still need
help after that post back.

Welcome to the list,
Bruce
-- 
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

A: Because it messes up the order in which people normally read text.                                                                                                                                                          
Q: Why is top-posting such a bad thing?                                                                                                                                                                                        
A: Top-posting.                                                                                                                                                                                                                
Q: What is the most annoying thing in e-mail?

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [gentoo-user] Re: Is Vesa/Uvesa still the way for Frame buffer
  2013-08-02 15:45 [gentoo-user] Is Vesa/Uvesa still the way for Frame buffer Harry Putnam
  2013-08-02 15:53 ` Canek Peláez Valdés
  2013-08-02 15:56 ` [gentoo-user] " Bruce Hill
@ 2013-08-02 15:57 ` Harry Putnam
  2 siblings, 0 replies; 5+ messages in thread
From: Harry Putnam @ 2013-08-02 15:57 UTC (permalink / raw
  To: gentoo-user

Harry Putnam <reader@newsguy.com> writes:

> 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

I should have included this information:

Kernel is v. 3.8.13, and it is a gentoo install as guest on a windows7
64bit, using vbox=4.2.16 r86992



^ permalink raw reply	[flat|nested] 5+ messages in thread

* [gentoo-user] Re: Is Vesa/Uvesa still the way for Frame buffer
  2013-08-02 15:53 ` Canek Peláez Valdés
@ 2013-08-02 16:01   ` Harry Putnam
  0 siblings, 0 replies; 5+ messages in thread
From: Harry Putnam @ 2013-08-02 16:01 UTC (permalink / raw
  To: gentoo-user

Canek Peláez Valdés <caneko@gmail.com> writes:

> First:
>
> /usr/src/linux/Documentation/fb/uvesafb.txt
>
> Second: what card do you use?

I haven't taken care of 'First' yet but here is the answer to
'second': Its a virtual box install of gentoo as guest on win7.

Apparently this is what the vm supplies for video card.

,----
| 
|    00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH
|    VirtualBox Graphics Adapter (prog-if 00 [VGA controller])
| 
|         Flags: bus master, fast devsel, latency 0, IRQ 11
|         Memory at e0000000 (32-bit, prefetchable) [size=16M]
|         Expansion ROM at <unassigned> [disabled]
`----



^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2013-08-02 16:05 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-08-02 15:45 [gentoo-user] Is Vesa/Uvesa still the way for Frame buffer Harry Putnam
2013-08-02 15:53 ` 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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox