public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlo Wood <carlo@alinoe.com>
To: Dave Jones <davej@redhat.com>,
	linux-kernel@vger.kernel.org, eric@anholt.net,
	zhenyu.z.wang@intel.com
Subject: Re: [AGPGART] intel_agp: use table for device probe
Date: Sun, 17 Jun 2007 23:55:58 +0200	[thread overview]
Message-ID: <20070617215558.GB6207@alinoe.com> (raw)
In-Reply-To: <20070617213355.GC3430@redhat.com>

On Sun, Jun 17, 2007 at 05:33:55PM -0400, Dave Jones wrote:
>  > What would the name be of such module?
> 
> intel-agp
> 
> Though by the looks of things, with the working kernel, you don't have
> it loaded (it's dependant upon the 'agpgart' module, which prints the
> "Detected" line that was missing).

hikaru:~>lsmod | grep agp
intel_agp              31776  0

It's loaded right now... that is with 2.6.22-rc4-+something (one of the
working ones).  I don't know WHEN it was loaded though. Probably
not at the same time as the others. 

And

hikaru:~>dmesg | grep agpgart
Linux agpgart interface v0.102 (c) Dave Jones

No 'Detected' line :/

Also, I noted that this 'agpgart: Detected..' line is always(?) printed
right after (often even without THAT line having printed a newline yet!)
something like:

udev: Waiting for /dev to be fully populated...agpgart: Detected an Intel 965G Chipset.

And this 'udev: Waiting for /dev to be fully populated' (sorry, didn't
write down the exact phrase, this is from memory) is also not printed
by kernels that work.

-- 
Carlo Wood <carlo@alinoe.com>

PS I asked you move to the other thread - it's a bit annoying to have
two threads about this now.


  reply	other threads:[~2007-06-17 21:56 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-13  8:02 DRI/AGP on AMD64 based machine Alex Bennee
2007-06-13 16:29 ` Dave Jones
2007-06-14  1:15   ` Carlo Wood
2007-06-14  1:17     ` Dave Airlie
2007-06-14  4:36       ` Carlo Wood
2007-06-14  4:40         ` Dave Airlie
2007-06-17 16:22     ` [AGPGART] intel_agp: use table for device probe Carlo Wood
2007-06-17 19:07       ` Dave Jones
2007-06-17 19:59         ` Carlo Wood
2007-06-17 20:49           ` Dave Jones
2007-06-17 21:13             ` Carlo Wood
2007-06-17 21:33               ` Dave Jones
2007-06-17 21:55                 ` Carlo Wood [this message]
2007-06-17 22:19                 ` Carlo Wood
2007-06-17 22:36                 ` Carlo Wood
2007-06-17 22:49                   ` Dave Jones
2007-06-18  0:06                     ` Carlo Wood
2007-06-18  0:16                       ` Dave Jones
2007-06-18  0:57                         ` Dave Airlie
2007-06-18  1:56                           ` Carlo Wood
2007-06-18  2:18                             ` Dave Airlie
2007-06-18 17:37                               ` Carlo Wood
2007-06-18  2:37                             ` Wang Zhenyu
2007-06-18 17:42                               ` Chuck Ebbert
2007-06-18 18:06                                 ` Dave Jones
2007-06-18 20:13                                 ` Carlo Wood
2007-06-18 19:58                               ` Carlo Wood

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=20070617215558.GB6207@alinoe.com \
    --to=carlo@alinoe.com \
    --cc=davej@redhat.com \
    --cc=eric@anholt.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhenyu.z.wang@intel.com \
    /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