public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul G. Allen" <pgallen@randomlogic.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Dual Athlon, AGP, and PCI
Date: Fri, 03 Aug 2001 17:12:19 -0700	[thread overview]
Message-ID: <3B6B3DE3.CEB608FD@randomlogic.com> (raw)
In-Reply-To: <3B691B85.368D1BD0@randomlogic.com> <3B6939BA.30001@fugmann.dhs.org> <3B693D6F.AD0DB931@randomlogic.com> <3B6A8CEC.1010401@fugmann.dhs.org>

Anders Peter Fugmann wrote:
> 
> Paul G. Allen wrote:
> 
> > Anders Peter Fugmann wrote:
> [SNIP]
> >>I have an UP system with the AMD761 chipset.
> >>
> >
> > The AMD762 has a different ID and is not recognized (the 761 is 7006,
> > and 762 is 700c), which throws a small wrench into things.
> 
> I'm not shure why. You stated that AGPGART worked with the
> try_unsopported=1 parameter (and that you had hacked the code to accept
> it anyways).

It's better (to me) to have it in the code than to have to add it at module load time. Also, I compiled agpgart into the kernel, not as a module.

> 
> >>
> >>(try look in NVIDIA_kernel-1.0-1251/os-registry.c for more parameters)
> >>
> >
> > I'll take a look, again after the project Database is rebuilt. (Without
> > "Understand for C++" I'd still be quite lost looking through all this
> > code!)
> 
> You do not need C experience to look at that code. It just states all
> possible module parameters in C form, and has a comment to them all.

Sorry for the confusion.

I have plenty of C/C++ experience, but anyone looking at 2M+ lines of sparsely commented source code and trying to get a quick understanding of how things work
needs help.

Understand for C++ is a C/C++ source code browser. It parses a C/C++ source tree and creates documentation that allows easy browsing of call trees, include
trees, declarations, global object usage, and more. It allowed me to quickly find the applicable code and see what was happening. I can even show you a complete
graphic of the entire kernel start sequence from (I hope I remember the function name here) start_kernel to nearly any function thereafter.

The only caveat is sometimes in order to create all this you have to tell Understand which directory to find a header/include file in, and if you're not sure
which is the correct one (in the case of multiple headers of the same name) you could get a little lost when looking at the resulting documentation.

In the case of the above - PCI IDs, AGP support, etc. - I have never looked at any kernel source before and I had no idea even where to start. After running it
through Understand, a couple clicks of a mouse and I can find nearl any object I want and know where it's used and why.


> 
> >
> >
> >>It works like a charm on my machine.
> >>
> >>Btw, if you want to make the NVidia module devfs aware please let me
> >>know and I'll send you a patch.
> >>
> >
> >
> > Hmmm, it might be nice.
> >

> 
> Ill create a patch for it this weekend.
> 

Thanks,

PGA

-- 
Paul G. Allen
UNIX Admin II/Programmer
Akamai Technologies, Inc.
www.akamai.com
Work: (858)909-3630
Cell: (858)395-5043

  reply	other threads:[~2001-08-04  0:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-02  9:21 Dual Athlon, AGP, and PCI Paul G. Allen
2001-08-02 13:15 ` Joshua M. Thompson
2001-08-03  4:42 ` Agus Budy Wuysang
2001-08-03 10:02   ` load balancing on more than 1 default routes rtviado
2001-08-03  9:58     ` michael chen
2001-08-06 14:12     ` Andi Kleen
     [not found] ` <3B6939BA.30001@fugmann.dhs.org>
     [not found]   ` <3B693D6F.AD0DB931@randomlogic.com>
2001-08-03 11:37     ` Dual Athlon, AGP, and PCI Anders Peter Fugmann
2001-08-04  0:12       ` Paul G. Allen [this message]
2001-08-03 12:19   ` Paul G. Allen
2001-08-04 10:42     ` Vojtech Pavlik
2001-08-04 20:20       ` Paul G. Allen
  -- strict thread matches above, loose matches on Subject: below --
2001-08-05  3:52 Paul G. Allen
     [not found] <200108050019.f750J6t24095@antimatter.net>
2001-08-05 10:42 ` Paul G. Allen
     [not found]   ` <20010805095853.04315de4.dlooney1@home.com>
2001-08-06  0:15     ` Paul G. Allen

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=3B6B3DE3.CEB608FD@randomlogic.com \
    --to=pgallen@randomlogic.com \
    --cc=linux-kernel@vger.kernel.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