From: Dave Jones <davej@redhat.com>
To: Alexander Stohr <AlexanderS@ati.com>
Cc: fb-devel <linux-fbdev-devel@lists.sourceforge.net>,
dri-devel <dri-devel@lists.sourceforge.net>
Subject: Re: [Dri-devel] Linux kernel PCI IDs vs Xfree
Date: Sun, 10 Aug 2003 15:07:27 +0100 [thread overview]
Message-ID: <20030810140727.GC17154@redhat.com> (raw)
In-Reply-To: <328A30E823B7D511A0BF00065B042A3B0172D768@fgl00exh01.fgl.atitech.com>
On Sat, Aug 09, 2003 at 10:41:01PM +0200, Alexander Stohr wrote:
> Which ones? e.g. www.yourvote.com\pci is the database
> where the Linux kernel does get its listing.
wrong. it occasionally gets merges from http://pciids.sf.net,
though IDs also get added directly to the kernel tree without
being added 'upstream' too, so its a two-way merge process.
Dave
--
Dave Jones http://www.codemonkey.org.uk
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
next prev parent reply other threads:[~2003-08-10 14:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-09 20:41 [Dri-devel] Linux kernel PCI IDs vs Xfree Alexander Stohr
2003-08-10 4:20 ` Jon Smirl
2003-08-10 6:00 ` More Linux kernel PCI IDs vs Xfree - Radeon Jon Smirl
2003-08-10 21:32 ` Two Linux framebuffer patches, Radeon and Rage128 Jon Smirl
2003-08-10 22:44 ` [Dri-devel] " Ian Romanick
2003-08-11 3:57 ` Jon Smirl
2003-08-12 7:08 ` Jon Smirl
2003-08-10 14:07 ` Dave Jones [this message]
2003-08-10 15:07 ` Re: [Dri-devel] Linux kernel PCI IDs vs Xfree Jon Smirl
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=20030810140727.GC17154@redhat.com \
--to=davej@redhat.com \
--cc=AlexanderS@ati.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-fbdev-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.