From: "H. Peter Anvin" <hpa@zytor.com>
To: Pascal Terjan <pterjan@mandriva.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: edd breaking vesafb
Date: Thu, 18 Sep 2008 09:26:03 -0700 [thread overview]
Message-ID: <48D2811B.8090602@zytor.com> (raw)
In-Reply-To: <1221751035.26693.8.camel@plop>
[-- Attachment #1: Type: text/plain, Size: 630 bytes --]
Pascal Terjan wrote:
> Hello
>
> I got a report of vesafb no longer working since edd is used on a
> machine (Shuttle FN41SP).
> It's a BIOS bug that was easily workarounded by calling set_video before
> query_edd.
> Does someone see some issue in doing that ?
>
Yes, it means that we won't get the status and error messages from
query_edd. In fact, we changed the ordering specifically for this reason.
The VESA code and EDD code both use the boot code heap. One could guess
that the problem is data left on the heap by the EDD code causing a
failure when combined with a bad BIOS.
Does this patch work for you?
-hpa
[-- Attachment #2: diff --]
[-- Type: text/plain, Size: 497 bytes --]
diff --git a/arch/x86/boot/boot.h b/arch/x86/boot/boot.h
index cc0ef13..f087238 100644
--- a/arch/x86/boot/boot.h
+++ b/arch/x86/boot/boot.h
@@ -205,7 +205,13 @@ static inline int isdigit(int ch)
extern char _end[];
extern char *HEAP;
extern char *heap_end;
-#define RESET_HEAP() ((void *)( HEAP = _end ))
+
+static inline void *RESET_HEAP(void)
+{
+ HEAP = _end;
+ memset(HEAP, 0, heap_end-HEAP);
+ return HEAP;
+}
static inline char *__get_heap(size_t s, size_t a, size_t n)
{
char *tmp;
next prev parent reply other threads:[~2008-09-18 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 15:17 edd breaking vesafb Pascal Terjan
2008-09-18 16:26 ` H. Peter Anvin [this message]
2008-09-18 17:10 ` Pascal Terjan
2008-09-18 18:43 ` H. Peter Anvin
2008-09-19 8:33 ` Pascal Terjan
-- strict thread matches above, loose matches on Subject: below --
2008-10-03 9:57 gettinther
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=48D2811B.8090602@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pterjan@mandriva.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;
as well as URLs for NNTP newsgroup(s).