From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] installing 9front on Dell Optiplex 790
Date: Sun, 1 May 2016 00:39:51 +0200 [thread overview]
Message-ID: <2c9f355dcb44b4449880ce2e21543c68@felloff.net> (raw)
In-Reply-To: <CALCVq+F+TDTnyc-GVONCYNY=vxB02LjA4FqEOPUg0ucf=OHHvw@mail.gmail.com>
monitor=vesa implies that aux/vga is using the vesa driver and *not*
the igfx driver.
if you set monitor to a entry in vgadb or in case of igfx, you
can set it to "auto" as the driver should detect the attached
monitors itself.
dump the registers and dump edid info of attached monitors:
aux/vga -m auto -p
then load a mode like:
aux/vga -m auto -l 1280x800x32
for this to work, the driver and the vgadb need to know the pci id.
so you need to add ctlr entry in vgadb like
ctlr
vid=0x8086 did=0x0102 # Intel 2nd Gen Core
link=vga
ctlr=igfx linear=1
and in /sys/src/cmd/aux/vga/igfx.c:^devtype
static int
devtype(Igfx *igfx)
{
if(igfx->pci->vid != 0x8086)
return -1;
switch(igfx->pci->did){
case 0x0102: /* 2nd Gen Core */
return TypeSNB;
...
documentation on the card can be found here:
https://01.org/linuxgraphics/documentation/driver-documentation-prms/2011-intel-core-processor-family
--
cinap
next prev parent reply other threads:[~2016-04-30 22:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 21:49 James
2016-04-30 21:57 ` [9front] " Nicolas Owens
2016-04-30 22:15 ` James
2016-04-30 22:47 ` cinap_lenrek
2016-04-30 22:39 ` cinap_lenrek [this message]
2016-05-01 0:43 ` James
2016-05-01 4:05 ` cinap_lenrek
2016-05-01 4:41 ` Matthew Veety
2016-05-01 4:51 ` sl
2016-05-01 7:19 ` Matthew Veety
2016-05-01 20:02 ` sl
2016-05-05 7:47 ` kokamoto
2016-05-05 10:53 ` kokamoto
2016-05-05 23:33 ` kokamoto
2016-05-05 23:56 ` cinap_lenrek
2016-05-06 0:33 ` kokamoto
2016-05-06 1:06 ` kokamoto
2016-05-06 5:29 ` kokamoto
2016-05-06 5:33 ` cinap_lenrek
2016-05-06 5:34 ` kokamoto
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=2c9f355dcb44b4449880ce2e21543c68@felloff.net \
--to=cinap_lenrek@felloff.net \
--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).