linux-kernel - Re: [PATCH 01/01] New FBDev driver for Intel Vermilion Range

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1175799493.10105.40.camel@jetpack.demon.co.uk>
Date:	Thu, 05 Apr 2007 19:58:13 +0100
From:	Alan Hourihane <alanh@...rlite.demon.co.uk>
To:	Valdis.Kletnieks@...edu
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 01/01] New FBDev driver for Intel Vermilion Range

On Thu, 2007-04-05 at 13:38 -0400, Valdis.Kletnieks@...edu wrote:
> 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).

I've asked the question and the part number would be...

LE80578

So, if that desperately needs changing let me know and I'll submit
another patch, or maybe someone can make the tweak for me.

Thanks,

Alan.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/