From: David Mosberger <davidm@napali.hpl.hp.com>
To: torvalds@osdl.org, Michel D?nzer <michel@daenzer.net>,
Anton Blanchard <anton@samba.org>
Cc: davidm@hpl.hp.com, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: radeon warning on 64-bit platforms
Date: Wed, 18 Feb 2004 00:51:24 +0000 [thread overview]
Message-ID: <16434.46860.429861.157242@napali.hpl.hp.com> (raw)
In-Reply-To: <20040217234848.GB22534@krispykreme>
>>>>> On Wed, 18 Feb 2004 10:48:49 +1100, Anton Blanchard <anton@samba.org> said:
Anton> A small thing, could the comment be constrained to 80
Anton> columns? :)
I don't really see the point of that, given that pretty much all
existing Linux source code is formatted for 100 columns. I don't feel
strongly about it, however, so I changed it.
>>>>> On Tue, 17 Feb 2004 15:53:05 -0800 (PST), Linus Torvalds <torvalds@osdl.org> said:
Linus> How about this alternate edited one that gets indentation
Linus> right and is more explicit about what's going on? Does this
Linus> work for you?
Fine by me.
>>>>> On Wed, 18 Feb 2004 00:44:16 +0100, Michel Dänzer <michel@daenzer.net> said:
Michel> looks good to me, except for a detail:
>> + * Michael Dänzer, the ioctl() is only used on embedded
>> platforms, so not
Michel> ^^^^^^^ That's not quite my first name. :)
Sorry about that, fixed below (or so I hope).
--david
=== drivers/char/drm/radeon_state.c 1.23 vs edited ==--- 1.23/drivers/char/drm/radeon_state.c Tue Feb 3 21:29:26 2004
+++ edited/drivers/char/drm/radeon_state.c Tue Feb 17 16:49:15 2004
@@ -2185,10 +2185,21 @@
case RADEON_PARAM_STATUS_HANDLE:
value = dev_priv->ring_rptr_offset;
break;
+#if BITS_PER_LONG = 32
+ /*
+ * This ioctl() doesn't work on 64-bit platforms because hw_lock is a
+ * pointer which can't fit into an int-sized variable. According to
+ * Michel Dänzer, the ioctl() is only used on embedded platforms, so
+ * not supporting it shouldn't be a problem. If the same functionality
+ * is needed on 64-bit platforms, a new ioctl() would have to be added,
+ * so backwards-compatibility for the embedded platforms can be
+ * maintained. --davidm 4-Feb-2004.
+ */
case RADEON_PARAM_SAREA_HANDLE:
/* The lock is the first dword in the sarea. */
- value = (int)dev->lock.hw_lock;
- break;
+ value = (long)dev->lock.hw_lock;
+ break;
+#endif
case RADEON_PARAM_GART_TEX_HANDLE:
value = dev_priv->gart_textures_offset;
break;
next prev parent reply other threads:[~2004-02-18 0:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16434.35199.597235.894615@napali.hpl.hp.com>
[not found] ` <1077054385.2714.72.camel@thor.asgaard.local>
[not found] ` <16434.36137.623311.751484@napali.hpl.hp.com>
[not found] ` <1077055209.2712.80.camel@thor.asgaard.local>
[not found] ` <16434.37025.840577.826949@napali.hpl.hp.com>
[not found] ` <1077058106.2713.88.camel@thor.asgaard.local>
2004-02-17 23:28 ` radeon warning on 64-bit platforms David Mosberger
2004-02-17 23:44 ` Michel Dänzer
2004-02-17 23:48 ` Anton Blanchard
2004-02-18 0:51 ` David Mosberger [this message]
2004-02-18 1:54 ` Matthew Wilcox
2004-02-18 1:59 ` David Mosberger
2004-02-18 2:28 ` Matthew Wilcox
2004-02-18 4:48 ` David Mosberger
2004-02-19 22:30 ` Valdis.Kletnieks
2004-02-20 15:51 ` Andreas Schwab
2004-02-20 22:14 ` Valdis.Kletnieks
2004-02-17 23:53 ` Linus Torvalds
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=16434.46860.429861.157242@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=anton@samba.org \
--cc=davidm@hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.net \
--cc=torvalds@osdl.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