From: forsyth@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Where is vgactl?
Date: Fri, 26 Oct 2001 16:36:18 +0100 [thread overview]
Message-ID: <20011026153104.AC35119A2F@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 115 bytes --]
aux/vga doesn't serve it; #v/vgactl is the kernel's exposed interface
to its part of the vga graphics support.
[-- Attachment #2: Type: message/rfc822, Size: 2458 bytes --]
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Where is vgactl?
Date: Fri, 26 Oct 2001 14:06:42 +0200
Message-ID: <20011026140642.E19815@cackle.proxima.alt.za>
On Fri, Oct 26, 2001 at 12:35:03PM +0100, forsyth@vitanuova.com wrote:
>
> it isn't bound automatically so you need
> bind -b '#v' /dev
> to make it appear in /dev, or use
> echo -n 'size 800x600x8' >'#v/vgactl'
>
> that's probably still not what you intend, because VGA being what it is,
> a host of major and minor register values need to be adjusted in most cases,
> in a device-dependent way. use aux/vga, described by vga(8).
> read the manual page first, though. aux/vga eventually sets the
> using vgactl, but sets all those registers first, if it can.
> it needs to be done outside rio.
Wouldn't it make more sense for aux/vga to serve /dev/vga* after
initialising the environment? I suppose the right answer is "Try it",
or am I missing something?
++L
next reply other threads:[~2001-10-26 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-26 15:36 forsyth [this message]
2001-10-26 16:01 ` [9fans] charon / tcp pasthrough sniffing Matt
2001-11-06 10:32 ` Jonadab the Unsightly One
2001-10-26 16:43 ` [9fans] Where is vgactl? Lucio De Re
-- strict thread matches above, loose matches on Subject: below --
2001-10-26 15:09 Russ Cox
2001-10-26 16:38 ` Lucio De Re
2001-10-26 11:35 forsyth
2001-10-26 12:06 ` Lucio De Re
2001-10-26 14:06 ` Matt Senecal
2001-10-26 9:24 Matt Senecal
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=20011026153104.AC35119A2F@mail.cse.psu.edu \
--to=forsyth@vitanuova.com \
--cc=9fans@cse.psu.edu \
/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).