From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id CF8E61381F3 for ; Fri, 2 Aug 2013 15:53:49 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 23FC5E0AFC; Fri, 2 Aug 2013 15:53:38 +0000 (UTC) Received: from mail-lb0-f174.google.com (mail-lb0-f174.google.com [209.85.217.174]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id CE2B7E0AB9 for ; Fri, 2 Aug 2013 15:53:36 +0000 (UTC) Received: by mail-lb0-f174.google.com with SMTP id w20so564479lbh.5 for ; Fri, 02 Aug 2013 08:53:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=OY9H9ZaXV5hkik7gIcFCwJbLnaIyK8eWf0lJQswhZBg=; b=p0NKgN8NWy0d891cSQUb/9UvIcVgamT5WTKsDZx0nr2BkGn1XGYpbZWdAQnr20sLDN zGwNQ09W9aN/SYV/XA/UW7yrhB3gX/iz9f2VNT16CdzilvNT7xH71EhpVsGFF/WPUEZX UNyyulaMHmM0znhmq8Ov/9YfV3z8e/96DJQstNhD/Au4M53ZN22pXaZCbjLtS5ql7bDW CjwSwhKAO+pxIW182zhG5J9hdSgf398scr45VLk/D+LrA8bQt+ZdXv35jQQtf75TEask RO4jrSVDCrnQn/FdszfdD5tec4I9wzccPP+B7gTyvred0Mai1/cqW54dlWsveyQrJaWs 3TPw== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.112.92.73 with SMTP id ck9mr3693147lbb.69.1375458815108; Fri, 02 Aug 2013 08:53:35 -0700 (PDT) Received: by 10.114.96.2 with HTTP; Fri, 2 Aug 2013 08:53:35 -0700 (PDT) In-Reply-To: <8738qsw0y4.fsf@newsguy.com> References: <8738qsw0y4.fsf@newsguy.com> Date: Fri, 2 Aug 2013 10:53:35 -0500 Message-ID: Subject: Re: [gentoo-user] Is Vesa/Uvesa still the way for Frame buffer From: =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw6lz?= To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: db4ccc69-d6e3-41ed-bd79-e6a5c3c14d94 X-Archives-Hash: 530d0a139761c54f662360b1dc4f33b6 On Fri, Aug 2, 2013 at 10:45 AM, 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=3D/dev/sdb3 vga=3D0x31A video=3Dvesafb: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 > > > =E2=94=82 Symbol: FB_VESA [=3Dy] = =E2=94=82 > =E2=94=82 Type : boolean = =E2=94=82 > =E2=94=82 Prompt: VESA VGA graphics support = =E2=94=82 > =E2=94=82 Defined at drivers/video/Kconfig:755 = =E2=94=82 > =E2=94=82 Depends on: HAS_IOMEM [=3Dy] && FB [=3Dy]=3Dy && X86 [=3Dy]= =E2=94=82 > =E2=94=82 Location: = =E2=94=82 > =E2=94=82 -> Device Drivers = =E2=94=82 > =E2=94=82 -> Graphics support = =E2=94=82 > =E2=94=82 (1) -> Support for frame buffer devices (FB [=3Dy]) = =E2=94=82 > =E2=94=82 Selects: FB_CFB_FILLRECT [=3Dy] && FB_CFB_COPYAREA [=3Dy] &= & | > | FB_CFB_IMAGEBLIT [=3Dy] && FB_BOOT_VE =E2= =94=82 > =E2=94=82 = =E2=94=82 > =E2=94=82 = =E2=94=82 > =E2=94=82 Symbol: FB_UVESA [=3Dn] = =E2=94=82 > =E2=94=82 Type : tristate = =E2=94=82 > =E2=94=82 Prompt: Userspace VESA VGA graphics support = =E2=94=82 > =E2=94=82 Defined at drivers/video/Kconfig:737 = =E2=94=82 > =E2=94=82 Depends on: HAS_IOMEM [=3Dy] && FB [=3Dy] && CONNECTOR [=3D= n] =E2=94=82 > =E2=94=82 Location: = =E2=94=82 > =E2=94=82 -> Device Drivers = =E2=94=82 > =E2=94=82 -> Graphics support = =E2=94=82 > =E2=94=82 (2) -> Support for frame buffer devices (FB [=3Dy]) = =E2=94=82 > =E2=94=82 Selects: FB_CFB_FILLRECT [=3Dy] && FB_CFB_COPYAREA [=3Dy] &= & | > | FB_CFB_IMAGEBLIT [=3Dy] && FB_MODE_HE =E2= =94=82 > =E2=94=82 = =E2=94=82 > =E2=94=82 = =E2=94=82 > =E2=94=82 Symbol: FB_BOOT_VESA_SUPPORT [=3Dy] = =E2=94=82 > =E2=94=82 Type : boolean = =E2=94=82 > =E2=94=82 Selected by: FB_VESA [=3Dy] && HAS_IOMEM [=3Dy] && FB [=3Dy= ]=3Dy && | > | X86 [=3Dy] || FB_INTEL [=3Dn] && HAS = =E2=94=82 First: /usr/src/linux/Documentation/fb/uvesafb.txt Second: what card do you use? Regards. --=20 Canek Pel=C3=A1ez Vald=C3=A9s Posgrado en Ciencia e Ingenier=C3=ADa de la Computaci=C3=B3n Universidad Nacional Aut=C3=B3noma de M=C3=A9xico