rote:
>
> >Date: Mon, 10 Nov 2003 06:38:24 -0800 (PST)
> >From: Alex Deucher <[EMAIL PROTECTED]>
> >To: [EMAIL PROTECTED]
> >Reply-To: [EMAIL PROTECTED]
> >Content-Type: text/plain; charset=us-ascii
> >Subject: Re: "nv" driver obscurities...
&g
On Mon, Nov 10, 2003 at 06:38:24AM -0800, Alex Deucher wrote:
> Sorry I haven't looked at the glint driver in a while. I was just
> trying to make a point that lots of drivers out there use hex rather
> than symbolic names. I seemed to recall glint as being one of them,
> but I guess I was wrong.
On Mon, 10 Nov 2003, Alex Deucher wrote:
>Date: Mon, 10 Nov 2003 06:38:24 -0800 (PST)
>From: Alex Deucher <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Reply-To: [EMAIL PROTECTED]
>Content-Type: text/plain; charset=us-ascii
>Subject: Re: "nv" driver obscurities..
Some time ago, there was a chap in New Zealand who was attempting to reverse
engineer and documaent what all the nvidia registers did, -plus get DMA going
for various ops. Google may turn up something - I don't have a URL to hand.
The last I heard came from a couple of years back however.
Sorry I haven't looked at the glint driver in a while. I was just
trying to make a point that lots of drivers out there use hex rather
than symbolic names. I seemed to recall glint as being one of them,
but I guess I was wrong.
Alex
--- Sven Luther <[EMAIL PROTECTED]> wrote:
> On Sun, Nov 09, 2
On Sun, 9 Nov 2003, Alex Deucher wrote:
>I agree that with hex values the driver is much harder to read
>and debug (as a casual developer). that's part of the reason
>the radeon driver is so well developed and feature-rich.
>however, I'd say that most drivers in xfree86 use hex values
>rather t
On Sun, Nov 09, 2003 at 11:23:38AM -0800, Alex Deucher wrote:
> I agree that with hex values the driver is much harder to read and
> debug (as a casual developer). that's part of the reason the radeon
> driver is so well developed and feature-rich. however, I'd say that
> most drivers in xfree86
I agree that with hex values the driver is much harder to read and
debug (as a casual developer). that's part of the reason the radeon
driver is so well developed and feature-rich. however, I'd say that
most drivers in xfree86 use hex values rather than symbolic names so
symbolic names are hardly
On Sun, 9 Nov 2003, Thomas Winischhofer wrote:
>> I suppose that is fair enough. I'm trying to debug an annoying
>> problem in the driver for some users having problems, and seeing
>> hexadecimal registers everywhere instead of symbolic names is
>> very frustrating.
>
>Mike, I really can't ima
Mike A. Harris wrote:
I suppose that is fair enough. I'm trying to debug an annoying
problem in the driver for some users having problems, and seeing
hexadecimal registers everywhere instead of symbolic names is
very frustrating.
Mike, I really can't imagine how symbolic names would help you if
On Sun, 9 Nov 2003, Kevin Brosius wrote:
>Well, gee, Mike... You're question was filled with negative
>assumptions about why the driver might be 'obfuscated'. You
>shouldn't take offense if Mark is a little short with you.
>Focus on asking a question, leaving off the insinuations, and
>you'll g
"Mike A. Harris" wrote:
>
>
> On Fri, 7 Nov 2003, Mark Vojkovich wrote:
>
> >> Everywhere
> >> in the driver hex values are given premultiplied by 4 it seems,
> >> and specified as VALUE/4.
> >
> > The register pointers are dword pointers. The register offsets
> >are byte offsets. They are w
On Fri, 7 Nov 2003, Mark Vojkovich wrote:
>> Everywhere
>> in the driver hex values are given premultiplied by 4 it seems,
>> and specified as VALUE/4.
>
> The register pointers are dword pointers. The register offsets
>are byte offsets. They are written as VALUE/4 so that I can grep
>for VA
On Fri, 7 Nov 2003, Mike A. Harris wrote:
> Everywhere
> in the driver hex values are given premultiplied by 4 it seems,
> and specified as VALUE/4.
The register pointers are dword pointers. The register offsets
are byte offsets. They are written as VALUE/4 so that I can grep
for VALUE. T
I'm curious about some of the obscurity in the "nv" driver. In
particular, almost everywhere in the driver, registers are
addressed numerically, and not by symbolic names. That on it's
own is obscure enough to make things difficult to tell what's
going on, but we know the deal with Nvidia doc
15 matches
Mail list logo