From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 30 14:14:16 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B93B316A407 for ; Fri, 30 Jun 2006 14:14:16 +0000 (UTC) (envelope-from tarc@tarc.po.cs.msu.su) Received: from tarc.po.cs.msu.su (tarc.po.cs.msu.su [158.250.16.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDBE143D46 for ; Fri, 30 Jun 2006 14:14:15 +0000 (GMT) (envelope-from tarc@tarc.po.cs.msu.su) Received: from tarc.po.cs.msu.su (localhost [127.0.0.1]) by tarc.po.cs.msu.su (8.13.4/8.13.4) with ESMTP id k5UEFklT096484; Fri, 30 Jun 2006 18:15:46 +0400 (MSD) (envelope-from tarc@tarc.po.cs.msu.su) Received: (from tarc@localhost) by tarc.po.cs.msu.su (8.13.4/8.13.4/Submit) id k5UEFjob096483; Fri, 30 Jun 2006 18:15:45 +0400 (MSD) (envelope-from tarc) Date: Fri, 30 Jun 2006 18:15:45 +0400 From: Arseny Nasokin To: Peter Jeremy Message-ID: <20060630141545.GI2475@tarc.po.cs.msu.su> References: <463aea570606240729u6b696c05vc1de0b1e03afae0f@mail.gmail.com> <20060624222706.GE747@turion.vk2pj.dyndns.org> <200606271242.50222.peter@wemm.org> <20060630032951.GR74776@tarc.po.cs.msu.su> <20060630033351.GA2475@tarc.po.cs.msu.su> <20060630090210.GD734@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20060630090210.GD734@turion.vk2pj.dyndns.org> User-Agent: mutt-ng/devel-r581 (FreeBSD) Cc: freebsd-amd64@freebsd.org Subject: Re: console in 1024x768 mode? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jun 2006 14:14:16 -0000 On Fri, Jun 30, 2006 at 07:02:10PM +1000, Peter Jeremy wrote: > On Fri, 2006-Jun-30 07:33:51 +0400, Arseny Nasokin wrote: > >On Fri, Jun 30, 2006 at 07:29:52AM +0400, Arseny Nasokin wrote: > >> Can it be needed for something else, not only for VESA videomode emulating? > > > >yes, it can: binary drivers, such N-Vidia =) > > Building a vm86 emulator that can handle occasional calls to VESA BIOS > to change screen configuration is relatively easy - efficiency is > irrelevant and you could adapt a x86 disassembler with minimal effort. > > Building a VM86 emulator that can usefully execute a binary driver - > especially a performance-critical one like a video driver - is a > totally different undertaking. > > -- > Peter Jeremy Understand, thanks -- Best regards, Arseny Nasokin