From: Gerd Knorr <kraxel@bytesex.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Bryan Mayland <bmayland@leoninedev.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] VESA framebuffer w/ MTRR locks 2.4.0 on init
Date: Fri, 5 Jan 2001 18:33:44 +0100 [thread overview]
Message-ID: <20010105183344.A2445@goldbach.in-berlin.de> (raw)
In-Reply-To: <3A55FAC9.9EB4C967@leoninedev.com> <E14Ea7x-00081J-00@the-village.bc.nu>
In-Reply-To: <E14Ea7x-00081J-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Jan 05, 2001 at 04:54:03PM +0000
> yywrap is a hack rather than generally safe feature and its not guaranteed that
> your videoram wraps neatly. Really the driver should have spotted the hole I
> guess.
Well, vesafb really depends on what the vesa bios says...
That's why it has all may-have-problems features turned off by default:
no ywrap, no mtrr. At least it was this way last time I touched it.
Gerd
--
Get back there in front of the computer NOW. Christmas can wait.
-- Linus "the Grinch" Torvalds, 24 Dec 2000 on linux-kernel
-
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 18:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 15:54 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 [this message]
2001-01-05 21:40 ` Bryan Mayland
2001-01-05 21:48 ` Alan Cox
2001-01-05 22:01 ` Bryan Mayland
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=20010105183344.A2445@goldbach.in-berlin.de \
--to=kraxel@bytesex.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bmayland@leoninedev.com \
--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®