From: Steven Cole <elenstev@mesatop.com>
To: Gerd Knorr <kraxel@strusel007.de>, Steven Cole <elenstev@mesatop.com>
Cc: linux-kernel@vger.kernel.org,
Martin Dalecki <dalecki@evision-ventures.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] 2.5.5-pre1 fix build error in drivers/video/vesafb.c
Date: Thu, 14 Feb 2002 10:02:59 -0700 [thread overview]
Message-ID: <200202141618.JAA04629@tstac.esa.lanl.gov> (raw)
In-Reply-To: <200202141501.IAA04461@tstac.esa.lanl.gov> <20020214163705.GA2185@goldbach.in-berlin.de>
In-Reply-To: <20020214163705.GA2185@goldbach.in-berlin.de>
On Thursday 14 February 2002 09:37 am, Gerd Knorr wrote:
> > - pmi_base = (unsigned short*)bus_to_virt(((unsigned
> > long)screen_info.vesapm_seg << 4) + screen_info.vesapm_off); +
> > pmi_base = (unsigned short*)phys_to_virt(((unsigned
> > long)screen_info.vesapm_seg << 4) + screen_info.vesapm_off);
>
> Looks fine to me. While s/bus/phys/ isn't the approximate fix for many
> drivers, at this place it is correct. The address is a segment:offset
> pointer to a physical memory address somewhere in the VESA BIOS.
>
> Gerd
Thanks. Do to some cut-and-paste haste, my original patch converted tabs
to spaces, so that patch won't apply. Here is a correct version for anyone
wanting to use it. Also, my net connnection was down this morning, so I failed
to see the other recent thread about this subject, [PATCH} 2.5.5-pre1 VESA fb.
Adding those correspondents to the cc list.
Steven
--- linux-2.5.5-pre1/drivers/video/vesafb.c.orig Thu Feb 14 08:16:25 2002
+++ linux-2.5.5-pre1/drivers/video/vesafb.c Thu Feb 14 08:17:24 2002
@@ -550,7 +550,7 @@
ypan = pmi_setpal = 0; /* not available or some DOS TSR ... */
if (ypan || pmi_setpal) {
- pmi_base = (unsigned short*)bus_to_virt(((unsigned long)screen_info.vesapm_seg << 4) + screen_info.vesapm_off);
+ pmi_base = (unsigned short*)phys_to_virt(((unsigned long)screen_info.vesapm_seg << 4) + screen_info.vesapm_off);
pmi_start = (void*)((char*)pmi_base + pmi_base[1]);
pmi_pal = (void*)((char*)pmi_base + pmi_base[2]);
printk(KERN_INFO "vesafb: pmi: set display start = %p, set palette = %p\n",pmi_start,pmi_pal);
prev parent reply other threads:[~2002-02-14 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 15:47 Steven Cole
2002-02-14 16:37 ` Gerd Knorr
2002-02-14 17:02 ` Steven Cole [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=200202141618.JAA04629@tstac.esa.lanl.gov \
--to=elenstev@mesatop.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dalecki@evision-ventures.com \
--cc=kraxel@strusel007.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®