From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.236.189.66 with SMTP id b42csp115511yhn; Wed, 11 Jul 2012 11:01:39 -0700 (PDT) Return-Path: <9front+bncCPTY2Ox2EIL_9v8EGgSeaxot@googlegroups.com> Received-SPF: pass (google.com: domain of 9front+bncCPTY2Ox2EIL_9v8EGgSeaxot@googlegroups.com designates 10.68.134.71 as permitted sender) client-ip=10.68.134.71; Authentication-Results: mr.google.com; spf=pass (google.com: domain of 9front+bncCPTY2Ox2EIL_9v8EGgSeaxot@googlegroups.com designates 10.68.134.71 as permitted sender) smtp.mail=9front+bncCPTY2Ox2EIL_9v8EGgSeaxot@googlegroups.com; dkim=pass header.i=9front+bncCPTY2Ox2EIL_9v8EGgSeaxot@googlegroups.com Received: from mr.google.com ([10.68.134.71]) by 10.68.134.71 with SMTP id pi7mr5467711pbb.19.1342029698991 (num_hops = 1); Wed, 11 Jul 2012 11:01:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:x-authenticated:x-provags-id:message-id :date:from:to:subject:in-reply-to:mime-version:x-y-gmx-trusted :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:x-google-group-id:list-post :list-help:list-archive:sender:list-subscribe:list-unsubscribe :content-type:content-transfer-encoding; bh=yRFmM+MdU+pD4f2EX75nBi+ML+XD3+W5XVVVpLGAfZg=; b=kCHSKd0isOifhFzPVij3ssOAZAAybSzXL4GmKPIsj4CaLrIV52yDgue8PS+Bp3eFq0 tOz2jHvi58mHXOCZLLKMG4zbmCGjZpjUIeQOxgOl8ctd3cnc3Cpzl392wYwSo4Cjq7bC rPBFgLl1bW5BtkR2CCY4Oqt1Ez2AYWH+lw2F4= Received: by 10.68.134.71 with SMTP id pi7mr1358602pbb.19.1342029698884; Wed, 11 Jul 2012 11:01:38 -0700 (PDT) X-BeenThere: 9front@googlegroups.com Received: by 10.68.233.198 with SMTP id ty6ls2741449pbc.2.gmail; Wed, 11 Jul 2012 11:01:38 -0700 (PDT) Received: by 10.68.220.230 with SMTP id pz6mr29160775pbc.3.1342029697645; Wed, 11 Jul 2012 11:01:37 -0700 (PDT) Received: by 10.68.220.230 with SMTP id pz6mr29160774pbc.3.1342029697636; Wed, 11 Jul 2012 11:01:37 -0700 (PDT) Received: from mailout-de.gmx.net (mailout-de.gmx.net. [213.165.64.23]) by gmr-mx.google.com with SMTP id gg7si755633pbc.0.2012.07.11.11.01.36; Wed, 11 Jul 2012 11:01:37 -0700 (PDT) Received-SPF: pass (google.com: domain of cinap_lenrek@gmx.de designates 213.165.64.23 as permitted sender) client-ip=213.165.64.23; Received: (qmail invoked by alias); 11 Jul 2012 18:01:35 -0000 Received: from i5E878172.versanet.de (EHLO rei2.9hal) [94.135.129.114] by mail.gmx.net (mp019) with SMTP; 11 Jul 2012 20:01:35 +0200 X-Authenticated: #10700799 X-Provags-ID: V01U2FsdGVkX18QA9IpqtAQj4WxY3X3u2AU4fVzdwrKK3jE4+7ZB+ DzlcQKq+P6GfHY Message-ID: <8995d16287a898fedf93707fe2eb4455@rei2.9hal> Date: Wed, 11 Jul 2012 19:59:26 +0200 From: cinap_lenrek@gmx.de To: 9front@googlegroups.com Subject: Re: vga In-Reply-To: MIME-Version: 1.0 X-Y-GMX-Trusted: 0 X-Original-Sender: cinap_lenrek@gmx.de X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of cinap_lenrek@gmx.de designates 213.165.64.23 as permitted sender) smtp.mail=cinap_lenrek@gmx.de Reply-To: 9front@googlegroups.com Precedence: list Mailing-list: list 9front@googlegroups.com; contact 9front+owners@googlegroups.com List-ID: <9front.googlegroups.com> X-Google-Group-Id: 831096995978 List-Post: , List-Help: , List-Archive: Sender: 9front@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit -m vesa is just a hack to force the vesa driver. -m is really the monitor to use from vgadb. normally, aux/vga will try to determine the type of graphics card from snooping the vga bios (looked up in vgadb) and then run device specific driver code to set the desired video mode. vgadb basicly matches some strings in the vga bios and lets you coose and you parametrize the driver. realemu is only used for vesa. native graphics driver doesnt need to run vga bios code. native driver just programs the various hardware registers to set the desired video mode and then activates the kernel part of the video driver for stuff like hardware bliting (acceleration), hardware cursors ect... (if the driver supports that) so using video without vesa means you need a graphics card that plan9 has native drivers for (and some plumbing in vgadb so it gets activated for your specific card... or you need to port / write a driver for it. vesa is kind of a universal driver that doesnt know at all how to program the hardware, but just runs some code stored in the vga bios under the supervision of realemu passing thru memory and register reads/writes to the real hardware. -- cinap