9front - general discussion about 9front
 help / color / mirror / Atom feed
From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: Re: [9front] strange behaviour of igfx and vesa
Date: Sat, 18 Jun 2016 08:40:14 +0900	[thread overview]
Message-ID: <f4691f4927c2d517b5d1b702fc9d0c9f@titan.jitaku.localdomain> (raw)
In-Reply-To: <644ef2b1069fabf217cddbfd75b14cae@felloff.net>

> state. the vesa bios might initialze registers that the igfx
> driver misses.
> 
> http://felloff.net/usr/cinap_lenrek/igdump.tar

I'll try this.

However, I have a memory of ducument that says somthing about
the value which you use port# of "2" like:
		switch(x){
		case PortVGA:
			vga->edid[x] = snarfgmedid(igfx, 2, 0x50);
			break;
in snarf() function. 

The document has a table which says individual chip has a different 
port number for a same PortVGA...
My memory goes bad these days, however, I think you can find it
from Intel's support site which was a short paged one.

I may be wrong, however, the behaviour suggests it, I suppose.

Kenji



  reply	other threads:[~2016-06-17 23:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-17  6:48 kokamoto
2016-06-17 12:46 ` [9front] " cinap_lenrek
2016-06-17 23:40   ` kokamoto [this message]
2016-06-18  1:29   ` kokamoto
2016-06-18  7:45   ` kokamoto
2016-06-18 23:38   ` kokamoto
2016-06-19  5:58   ` kokamoto
2016-06-20  2:48   ` kokamoto
2016-06-20  4:14     ` kokamoto
2016-06-22  0:25   ` kokamoto
2016-06-22  7:26     ` cinap_lenrek
2016-06-23  6:43       ` kokamoto
2016-06-23 10:55         ` cinap_lenrek
2016-06-23 11:24           ` kokamoto
2016-06-25  1:50             ` kokamoto
2016-06-30  2:06               ` 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=f4691f4927c2d517b5d1b702fc9d0c9f@titan.jitaku.localdomain \
    --to=kokamoto@hera.eonet.ne.jp \
    --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).