From: Bryan Mayland <bmayland@leoninedev.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Gerd Knorr <kraxel@bytesex.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] VESA framebuffer w/ MTRR locks 2.4.0 on init
Date: Fri, 05 Jan 2001 17:01:21 -0500 [thread overview]
Message-ID: <3A564430.897167F3@leoninedev.com> (raw)
In-Reply-To: <E14EeiW-0008VW-00@the-village.bc.nu>
Alan Cox wrote:
> > So what do you say. Can we use my patch to allow the user to override the VESA
> > detected memory size... or does anyone else have a better plan?
>
> It seems a passable solution. The mtrr bug is real either way and wants a fix.
> If the 2Mb reporting is wrong perhaps they will fix the bios ;)
Hee hee. When I first saw this happening back in 1999, I tried to talk to Dell first but
after about an hour on the phone with the support guy trying to explain what VESA BIOS
Extensions were, and why running the Dell diagnostics disk would not solve my problem, I
decided I'd just fix it in software. Can I get an amen for an open source operating
system?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-05 22:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 15:54 [PATCH] VESA framebuffer w/ MTRR locks 2.4.0 on init Bryan Mayland
2001-01-05 16:05 ` Alan Cox
2001-01-05 16:31 ` Chris Kloiber
2001-01-05 21:16 ` Steven Walter
2001-01-06 1:12 ` David Wragg
2001-01-06 9:47 ` Gerd Knorr
2001-01-05 16:48 ` Bryan Mayland
2001-01-05 16:54 ` Alan Cox
2001-01-05 17:33 ` Gerd Knorr
2001-01-05 21:40 ` Bryan Mayland
2001-01-05 21:48 ` Alan Cox
2001-01-05 22:01 ` Bryan Mayland [this message]
2001-01-06 1:20 ` [PATCH] VESA framebuffer w/MTRR " David Wragg
2001-01-06 17:08 ` Bryan Mayland
2001-01-06 19:23 ` Alan Cox
2001-01-06 17:28 ` Framebuffer as a module Bryan Mayland
[not found] ` <002501c07819$21343900$fd1942c3@bluescreen>
2001-01-06 20:04 ` Bryan Mayland
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=3A564430.897167F3@leoninedev.com \
--to=bmayland@leoninedev.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kraxel@bytesex.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