public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Antonino Daplas <adaplas@pol.net>
To: Dave Jones <davej@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG]: agpgart for i810 chipsets broken in 2.5.51
Date: 11 Dec 2002 00:36:47 +0500	[thread overview]
Message-ID: <1039548861.1086.42.camel@localhost.localdomain> (raw)
In-Reply-To: <20021210172320.A4586@suse.de>

On Tue, 2002-12-10 at 21:23, Dave Jones wrote:
> On Wed, Dec 11, 2002 at 12:08:22AM +0500, Antonino Daplas wrote:
>  > Tried it with framebuffer console off, same results. Moved agp before vt
>  > in char/Makefile, same. Even manually calling agp_init() doesn't work
>  > because what's really needed is agp_intel_init(). 
>  > 
>  > Anyway, I guess I'll stick to what I'm doing right now, periodically do
>  > an inter_module_get("drm_agp") until it becomes available.
> 
> That's really quite icky. Even putting an..
> 
> #ifdef CONFIG_FRAMEBUFFER_I810
>     dev = pci_find_blah..
>     agp_intel_init(dev);
> #endif
> 
> before console_init() call in init/main.c seems cleaner than that imo,
> (and this is still quite gross).
> 
That's fine by me.  It's basically what I'm doing in 2.4, except that I
call it directly from the driver.  I'm just not in the habit of touching
other people's code.  

agp_intel_init() will be called twice though, first by i810fb, then the
usual inits, so a flag has to be set once the function is called.

If it's okay with you, I'll do it that way (and save me some 100 lines
of code in the process :-), and submit a patch.

Tony 



  parent reply	other threads:[~2002-12-10 16:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10 12:21 [BUG]: agpgart for i810 chipsets broken in 2.5.51 Antonino Daplas
2002-12-10 13:11 ` Dave Jones
2002-12-10 16:47   ` Antonino Daplas
2002-12-10 14:03     ` Dave Jones
2002-12-10 17:34       ` Antonino Daplas
2002-12-10 19:08       ` Antonino Daplas
2002-12-10 16:23         ` Dave Jones
2002-12-10 17:06           ` Alan Cox
2002-12-10 17:05             ` Dave Jones
2002-12-10 21:00               ` Antonino Daplas
2002-12-10 18:21                 ` Dave Jones
2002-12-10 21:23                   ` Antonino Daplas
2002-12-10 19:36           ` Antonino Daplas [this message]
2002-12-10 14:48     ` Dave Jones
2002-12-10 19:07       ` Antonino Daplas
2002-12-10 16:17         ` Dave Jones
2002-12-10 19:37           ` Antonino Daplas
2002-12-10 21:01           ` Antonino Daplas

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=1039548861.1086.42.camel@localhost.localdomain \
    --to=adaplas@pol.net \
    --cc=davej@suse.de \
    --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