From: Daniel Lyons <fusion@storytotell.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Parallels Vesa driver question
Date: Tue, 4 Aug 2009 01:15:05 -0600 [thread overview]
Message-ID: <6B29A927-0CFC-49E3-A356-F9D2E46FE4D3@storytotell.org> (raw)
In-Reply-To: <13426df10908030930gf9a6639g5ace1ba59cb5a8b1@mail.gmail.com>
On Aug 3, 2009, at 10:30 AM, ron minnich wrote:
> Given these systems with mtrr issues.
>
> Would it be possible to get:
> - output from pci so we can see what memory ranges are in use on
> your machine
0.2.0: vid 03.00.00 1ab8/1131 11 0:00004001 256 1:c0000000 16777216
2:00004401 16
0.3.0: brg 06.80.00 1ab8/1112 9
0.30.0: brg 06.00.00 8086/1130 255
0.31.0: brg 06.01.00 8086/2440 255
0.31.1: disk 01.01.80 8086/244b 255 4:00005001 16
0.31.5: aud 04.01.00 8086/2445 9 0:00005401 256 1:00005801 64
0.5.0: net 02.00.00 10ec/8029 10 0:00004c01 32
> - how much memory
256 MB, but that's arbitrary; just the preference I have set in
Parallels.
> - what the mtrrs look like once set up
I don't know how to obtain this information, but would be glad to
supply it. Also, forgive my ignorance, but isn't there a chicken-and-
egg problem, since if the MTRRs are set up in vgavesa.c, my display is
unusable? Or is there a special way to bail out to the text mode when
the display is screwed up?
Thanks again,
—
Daniel Lyons
next prev parent reply other threads:[~2009-08-04 7:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 9:36 Daniel Lyons
2009-08-02 17:06 ` erik quanstrom
2009-08-02 19:14 ` Daniel Lyons
2009-08-02 20:41 ` Steve Simon
2009-08-02 21:41 ` erik quanstrom
2009-08-03 6:57 ` Daniel Lyons
2009-08-03 9:26 ` Richard Miller
2009-08-03 11:20 ` erik quanstrom
2009-08-04 2:36 ` geoff
2009-08-04 3:12 ` David Leimbach
2009-08-04 7:18 ` Daniel Lyons
2009-08-04 7:25 ` Bakul Shah
2009-08-04 12:47 ` David Leimbach
2009-08-04 15:20 ` Bakul Shah
2009-08-04 15:25 ` David Leimbach
2009-08-04 16:24 ` Bakul Shah
2009-08-04 17:46 ` erik quanstrom
2009-08-12 6:18 ` Bakul Shah
2009-08-04 8:54 ` Daniel Lyons
2009-08-04 9:04 ` erik quanstrom
2009-08-03 16:30 ` ron minnich
2009-08-04 7:15 ` Daniel Lyons [this message]
2009-08-04 15:26 ` ron minnich
2009-08-03 9:13 ` Balwinder S Dheeman
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=6B29A927-0CFC-49E3-A356-F9D2E46FE4D3@storytotell.org \
--to=fusion@storytotell.org \
--cc=9fans@9fans.net \
/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).