From: unobe@cpan.org
To: 9front@9front.org
Subject: Re: [9front] MB Pro early-2011 support status
Date: Tue, 20 Apr 2021 12:20:48 -0700 [thread overview]
Message-ID: <572FED29D56F3524094F7CBC9109F9AD@smtp.pobox.com> (raw)
In-Reply-To: <17CFECB7536A5F4595061DCEA7F4E4AE@smtp.pobox.com>
Quoth unobe@cpan.org:
> Do you know if that means vga commands for blanking could then be
> supported, something like what's tried in
> /sys/src/9/pc/vga.c:/^vgablank ?
Okay, so I found the problem by (surprise, surprise!) looking at the
code, and what calls what. I'll try to post more details later
tonight. But it appears to be a config issue.
In plan9.ini I set $monitor to 'vga', which then sets my native
resolution to 1280x800x32. $vgasize is not set, and if I did try to
set it to that using 'aux/vga -l' it would fail because that
resolution isn't in vgadb (I think I'd have to have the timing info,
which I don't have--but maybe that can be introspected or there's a
simple fix? It'd be nice to be able to switch to other other
(purported) native resolutions). So when I call /bin/screenrc (before
starting rio), there's no $vgasize so aux/vga -l $vgasize doesn't get
loaded, so drawinit is never called for igfx, so screen blanking is
never set. I manually did: 'echo drawinit >/dev/vgactl' then when I
did 'echo blank >/dev/mousectl' I saw a flicker. Doing a 'sleep 1;
echo blank >/dev/mousectl' works and now I have screen blanking.
Huzzah.
next prev parent reply other threads:[~2021-04-20 19:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 5:36 unobe
2021-04-19 10:40 ` [9front] " Anthony Martin
2021-04-19 16:14 ` unobe
2021-04-19 19:00 ` [9front] " Nick Owens
2021-04-20 15:59 ` unobe
2021-04-20 19:20 ` unobe [this message]
2021-04-21 4:29 ` unobe
2021-04-21 15:01 ` cinap_lenrek
2021-04-22 17:50 ` unobe
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=572FED29D56F3524094F7CBC9109F9AD@smtp.pobox.com \
--to=unobe@cpan.org \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).