From: Valdis.Kletnieks@vt.edu
To: Alan Hourihane <alanh@fairlite.demon.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/01] New FBDev driver for Intel Vermilion Range
Date: Thu, 05 Apr 2007 13:38:23 -0400 [thread overview]
Message-ID: <8776.1175794703@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 05 Apr 2007 11:44:46 BST." <1175769886.10382.29.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
On Thu, 05 Apr 2007 11:44:46 BST, Alan Hourihane said:
> Attached is a patch against 2.6.21-rc5 which adds the Intel Vermilion
> Range support.
One non-technical question here...
> +config FB_VERMILION
> + tristate "Vermilion support"
> + depends on FB && PCI && X86
> + select FB_MODE_HELPERS
> + select FB_CFB_FILLRECT
> + select FB_CFB_COPYAREA
> + select FB_CFB_IMAGEBLIT
> + help
> + This driver supports the Vermilion Range chipset
Is 'Vermillion' the project codename, or the name that end users will actually
see when hardware ships? Most of the Intel graphics chopsets have been
named things like i810, i925, and so on - if the user-visible name is known,
that should probably be reflected in the 'tristate' string and help
text (FB_VERMILLION in the code is fine by be though).
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2007-04-05 17:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 10:44 Alan Hourihane
2007-04-05 17:38 ` Valdis.Kletnieks [this message]
2007-04-05 18:42 ` James Simmons
2007-04-05 18:58 ` Alan Hourihane
[not found] ` <200704052138.08897.arnd@arndb.de>
2007-04-05 21:42 ` Alan Hourihane
2007-04-05 21:56 ` Arnd Bergmann
2007-04-05 22:00 ` Antonino A. Daplas
2007-04-06 0:09 ` Antonino A. Daplas
2007-04-06 13:39 ` Alan Hourihane
2007-04-09 20:10 ` Pavel Machek
2007-04-20 9:04 ` Alan Hourihane
2007-04-20 13:51 ` Antonino A. Daplas
2007-04-20 13:54 ` Alan Hourihane
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=8776.1175794703@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=alanh@fairlite.demon.co.uk \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®