From owner-freebsd-mobile@FreeBSD.ORG Sat Jul 26 01:43:39 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 410BF37B404 for ; Sat, 26 Jul 2003 01:43:39 -0700 (PDT) Received: from hysteria.spc.org (hysteria.spc.org [195.206.69.234]) by mx1.FreeBSD.org (Postfix) with SMTP id 2A55843F93 for ; Sat, 26 Jul 2003 01:43:37 -0700 (PDT) (envelope-from bms@hysteria.spc.org) Received: (qmail 14793 invoked by uid 5013); 26 Jul 2003 08:41:14 -0000 Date: Sat, 26 Jul 2003 09:41:14 +0100 From: Bruce M Simpson To: Greg 'groggy' Lehey Message-ID: <20030726084114.GD27921@spc.org> Mail-Followup-To: Bruce M Simpson , Greg 'groggy' Lehey , FreeBSD current users , FreeBSD mobile Mailing List References: <20030726080217.GB45069@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030726080217.GB45069@wantadilla.lemis.com> User-Agent: Mutt/1.4.1i Organization: SPC cc: FreeBSD current users cc: FreeBSD mobile Mailing List Subject: Re: Mapping Video BIOS? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jul 2003 08:43:39 -0000 On Sat, Jul 26, 2003 at 05:32:17PM +0930, Greg 'groggy' Lehey wrote: > Can anybody point me in the right direction? Where should I be > looking for this? Is this memory mapped permanently, or is it only > during X startup? The video BIOS is usually mapped by system BIOS into real memory to begin with, so it should be just sitting there. There are usually northbridge chipset registers for dealing with this sort of thing. The SMM mode might reuse that window, though, but generally this is hidden from non-SMM mode applications. You're in luck - been rebuilding X, so have xc tarballs handy. The XFree86 code responsible is: xc/programs/Xserver/hw/xfree86/int10 Some drivers like to call VBE via int10h, so this module acts as a bridge. It just memcpy()'s the ROM and uses various methods, depending on the compilation target, to call int10h. Is the onboard video AGP/PCI? It is possible that the device isn't reporting its memory window in the ROM BAR correctly. I've seen this happen with some low-end network cards before. Try my tools at this URL to check this: http://www.incunabulum.com/code/projects/pci/freebsd/ BMS