From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: dri-devel <dri-devel@lists.sourceforge.net>,
fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [Dri-devel] rage/radeon fb driver patch again!
Date: 17 Aug 2003 10:07:36 +0200 [thread overview]
Message-ID: <1061107655.602.17.camel@gaston> (raw)
In-Reply-To: <20030817034344.12442.qmail@web14901.mail.yahoo.com>
On Sun, 2003-08-17 at 05:43, Jon Smirl wrote:
> linux/pci_ids.h changed which stomped my patch again.
> I am really getting tired of editing patches consiting
> of hundreds of hex numbers. I spent a full day
> collecting this set of Rage and Radeon PCI IDs and it
> is a real pain that it is being added to pci_ids.h
> piecemeal. This patch sorts the list, adds more
> missing entries, removes some known wrong ones, and
> fixes some spelling.
Oops, my fault, I sent a patch fixing some incorrect IDs in
James latest one, that was breaking some M9 based PowerMacs.
Maybe you could submit the pci_ids.h patch to Linus right now,
separate from the actual radeon/r128 driver patches ?
> The IGP PCIs should be added in the X0/X1/X2 form, not
> as RS300_speed. If we are going to switch to chip
> family/speed for the name then do it to all of the IDs
> not just a couple.
-------------------------------------------------------
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-17 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-17 3:43 rage/radeon fb driver patch again! Jon Smirl
2003-08-17 8:07 ` Benjamin Herrenschmidt [this message]
2003-08-17 16:13 ` [Dri-devel] " 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=1061107655.602.17.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=jonsmirl@yahoo.com \
--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 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).