public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alfred E. Heggestad" <linuxedmund@home.no>
To: Florin Iucha <florin@iucha.net>
Cc: Dave Jones <davej@codemonkey.org.uk>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Next round of AGPGART fixes.
Date: 25 Dec 2002 19:21:24 +0100	[thread overview]
Message-ID: <1040840483.486.2.camel@io> (raw)
In-Reply-To: <20021222183657.GA1043@iucha.net>

On Sun, 2002-12-22 at 19:36, Florin Iucha wrote:
> On Sun, Dec 22, 2002 at 09:52:11AM -0600, Florin Iucha wrote:
> > On Fri, Dec 20, 2002 at 12:41:37PM +0000, Dave Jones wrote:
> > > Linus,
> > >  Please pull from bk://linux-dj.bkbits.net/agpgart to get at the
> > > following fixes..
> > [snip]
> > > GNU diff for those who care (against Linus' bk tree) is at
> > > ftp.kernel.org/pub/linux/kernel/people/davej/patches/2.5/2.5.52/agpgart-fixes-1.diff
> > 
> > I'm using bk7 which contains all your patch except via* stuff which I'm
> > not interested in.
> > Agpgart and sis-agp compiled as modules. Modprobe agpgart succeeds, 
> > modprobe sis-agp oopses:
> > 
> > agpgart: Detected SiS 735 chipset
> 
> [snip oops]
> 
> With agpgart and sis-agp built in the kernel (non-modular) it works
> fine - I have direct rendering enabled in X.
> 
> Cheers,
> florin

I also had this problem with 2.5.51 and 2.5.52. Just tried 2.5.53
last night and now /dev/agpgart works fine again (static kernel,
no modules). Thanks.

/alfred

-- 
/**
 * Alfred E. Heggestad - Coder
 */


      reply	other threads:[~2002-12-25 18:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-20 12:41 Next round of AGPGART fixes Dave Jones
2002-12-20 14:42 ` Felix Seeger
2002-12-20 16:41   ` Felix Seeger
2002-12-20 18:44     ` Dave Jones
2002-12-21  7:07 ` Linus Torvalds
2002-12-21 14:23   ` Dave Jones
2002-12-22 15:52 ` Florin Iucha
2002-12-22 18:36   ` Florin Iucha
2002-12-25 18:21     ` Alfred E. Heggestad [this message]

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=1040840483.486.2.camel@io \
    --to=linuxedmund@home.no \
    --cc=davej@codemonkey.org.uk \
    --cc=florin@iucha.net \
    --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