From: Pavel Machek <pavel@suse.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "David S. Miller" <davem@redhat.com>,
davej@suse.de, eike@bilbo.math.uni-mannheim.de,
linux-kernel@vger.kernel.org
Subject: Re: [2.5.4-pre3] link error in drivers/video/video.o
Date: Sun, 10 Feb 2002 00:05:54 +0100 [thread overview]
Message-ID: <20020209230554.GB1589@elf.ucw.cz> (raw)
In-Reply-To: <20020208.074857.88474129.davem@redhat.com> <E16ZDqh-0004AV-00@the-village.bc.nu>
In-Reply-To: <E16ZDqh-0004AV-00@the-village.bc.nu>
Hi!
> > That is incorrect. The warning occurs because someone made bogus changes to
> > the vesa driver without understanding what was going on. The vesa frame
> > buffer returned by the BIOS is a physical cpu address not a bus address
> > and nothing to do with magic PCI mappings.
> >
> > There were no changes made, in fact the VESA driver by your own
> > definition was buggy before my changes went in. :-) It was using
> > bus_to_virt and virt_to_bus all along Alan.
>
> My error then. That or someone broke it around 2.0 8). It should be using
> phys_to_virt. Its the usual weirdness of talking to the BIOS which talks in
> CPU physical addresses.
Hm, I wonder where it goes in /proc/driver hierarchy...? Probably
/proc/driver/legacy?
Pavel
--
(about SSSCA) "I don't say this lightly. However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa
next prev parent reply other threads:[~2002-02-10 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 14:22 Rolf Eike Beer
2002-02-08 14:57 ` Dave Jones
2002-02-08 15:48 ` David S. Miller
2002-02-08 16:26 ` Alan Cox
2002-02-09 23:05 ` Pavel Machek [this message]
2002-02-08 15:55 ` Alan Cox
2002-02-08 15:01 ` Alan Cox
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=20020209230554.GB1589@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@suse.de \
--cc=davem@redhat.com \
--cc=eike@bilbo.math.uni-mannheim.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
all inboxes | Powered by JetHome®