From: Dave Jones <davej@codemonkey.org.uk>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: framebuffer initialisation.
Date: Wed, 14 May 2003 00:08:36 +0100 [thread overview]
Message-ID: <20030513230836.GA15158@suse.de> (raw)
James,
The 2.5 agpgart code broke the i810fb a while back.
The reason behind this, is that previously (i.e. 2.4) agp_init()
would call the chipset specific backend init routines.
In 2.5, that stuff got pushed out into seperate modules,
so now i810fb does a (superflous) agp_init() which just
printk's the agpgart banner, and then calls the intel_agp_init()
function directly.
This *should* work, but doesn't.
The agpgart code *absolutely must* be set up before the framebuffer
code. Previously this was going to be solved with link order shuffling,
however that won't work, as the drivers/video stuff is initialised
from drivers/char/mem.c (Really non-intuitive place to hide fb init IMO)
mem.c gets linked before agp/ so we lose there.
Hence the explicit init in i810fb. I've tried to untangle this and
figure out why that isn't working, at a complete loss.
(The lack of hardware to test this on also doesn't help).
Any ideas ?
Dave
reply other threads:[~2003-05-13 22:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030513230836.GA15158@suse.de \
--to=davej@codemonkey.org.uk \
--cc=jsimmons@infradead.org \
--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