From mboxrd@z Thu Jan 1 00:00:00 1970 From: Antonino Daplas Subject: Re: Reading the EDID block for x86 machines Date: 13 Mar 2003 01:38:40 +0800 Sender: linux-fbdev-devel-admin@lists.sourceforge.net Message-ID: <1047490650.1030.31.camel@localhost.localdomain> References: <20030311234249.40244.qmail@web14914.mail.yahoo.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: Received: from pine.compass.com.ph ([202.70.96.37]) by sc8-sf-list1.sourceforge.net with smtp (Exim 3.31-VA-mm2 #1 (Debian)) id 18tAEO-0001Go-00 for ; Wed, 12 Mar 2003 09:41:33 -0800 In-Reply-To: <20030311234249.40244.qmail@web14914.mail.yahoo.com> Errors-To: linux-fbdev-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Content-Type: text/plain; charset="us-ascii" To: Jon Smirl Cc: James Simmons , Linux Fbdev development list On Wed, 2003-03-12 at 07:42, Jon Smirl wrote: > --- Antonino Daplas wrote: > > Yikes! No, it can't be done this way. During the > > early boot sequence, > > the kernel is not yet decompressed and loaded, so > > all the services the > > kernel provides are still unavailable. Unless you > > want to walk, detect, > > enable, etc the PCI subsystem in pure 16-bit > > assembly... > > You don't Linux to look at the PCI subsys you make > calls into the system BIOS to find the devices. That's not the only reason. The problem is in 16-bit mode, the code can only access an address range up to only 1MB. PCI resources are located above 16MB. So in order to copy the ROM, it might be necessary to switch to 32-bit mode, copy the ROM, switch back to 16-bit mode, etc. Unless I missed some imported BIOS calls or other methods to do this or something similar in real-mode... Tony ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en