From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: kronos <kronos@kronoz.cjb.net>,
fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Unifying radeon.h constant files
Date: Mon, 01 Sep 2003 08:08:37 +0200 [thread overview]
Message-ID: <1062396517.32736.71.camel@gaston> (raw)
In-Reply-To: <20030901052543.31422.qmail@web14915.mail.yahoo.com>
On Mon, 2003-09-01 at 07:25, Jon Smirl wrote:
> What do you think about getting rid of include/video/radeon.h and replacing it
> with the much more comprehensive one from XFree86? It would make life easier if
> constants had the same names in the kernel and XFree86 code. radeonfb would
> need to be touched up for about 100 name changes.
>
> char/drm/radeon_drv.h has a third set of names but that is up to the DRI people
> to fix. If we can get radeonfb and 2D XFree on the same set of names I'll see
> if I can get the 3D people to go along.
>
> If this works for Radeon we should do it for Rage128 too.
I'm all for doing that, but not until I've finished the new version of
the driver ;) Also, I have a bunch of additional constants used by the
Power Management code that don't have the RADEON_ prefix neither and are
not in XFree, we would have to fixup that too.
Ben.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-09-01 6:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 5:25 Unifying radeon.h constant files Jon Smirl
2003-09-01 6:08 ` Benjamin Herrenschmidt [this message]
2003-09-01 15:56 ` Jon Smirl
2003-09-01 19:38 ` Benjamin Herrenschmidt
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=1062396517.32736.71.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=jonsmirl@yahoo.com \
--cc=kronos@kronoz.cjb.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 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).