linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Simmons <jsimmons@infradead.org>
To: Amit Shah <shahamit@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1: Framebuffer problem
Date: Thu, 17 Jul 2003 18:05:54 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0307171804370.10255-100000@phoenix.infradead.org> (raw)
In-Reply-To: <200307161107.40159.shahamit@gmx.net>


> > #
> > # Graphics support
> > #
> > CONFIG_FB=y
> > # CONFIG_FB_CIRRUS is not set
> > # CONFIG_FB_PM2 is not set
> > # CONFIG_FB_CYBER2000 is not set
> > # CONFIG_FB_IMSTT is not set
> > CONFIG_FB_VGA16=y 		<---- to many drivers selected. Please 
				<---- pick only one.
> > CONFIG_FB_VESA=y
> > CONFIG_VIDEO_SELECT=y
> > # CONFIG_FB_HGA is not set
> > CONFIG_FB_RIVA=y		<-----
> > # CONFIG_FB_I810 is not set
> > # CONFIG_FB_MATROX is not set
> > # CONFIG_FB_RADEON is not set
> > # CONFIG_FB_ATY128 is not set
> > # CONFIG_FB_ATY is not set
> > # CONFIG_FB_SIS is not set
> > # CONFIG_FB_NEOMAGIC is not set
> > # CONFIG_FB_3DFX is not set
> > # CONFIG_FB_VOODOO1 is not set
> > # CONFIG_FB_TRIDENT is not set
> > # CONFIG_FB_PM3 is not set
> > # CONFIG_FB_VIRTUAL is not set


  reply	other threads:[~2003-07-17 16:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15  5:47 2.6.0-test1: Framebuffer problem Amit Shah
2003-07-16  5:37 ` Amit Shah
2003-07-17 17:05   ` James Simmons [this message]
2003-07-17 17:21     ` Alan Cox
2003-07-17 17:34       ` James Simmons
2003-07-18  9:53         ` Amit Shah
2003-07-18 12:57         ` Alan Cox
2003-07-18 20:18           ` Geert Uytterhoeven
2003-07-18 21:15             ` Alan Cox
2003-07-19  6:02               ` Geert Uytterhoeven
2003-07-19 13:07                 ` Alan Cox
2003-07-21 20:14                   ` Geert Uytterhoeven

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=Pine.LNX.4.44.0307171804370.10255-100000@phoenix.infradead.org \
    --to=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shahamit@gmx.net \
    /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).