From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Smirl Subject: Re: vm86 - DCC probes don't work Date: Tue, 22 Feb 2005 18:38:38 -0500 Message-ID: <9e473391050222153862128de0@mail.gmail.com> References: Reply-To: Jon Smirl Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit In-Reply-To: Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Ian Pratt Cc: Rik van Riel , Stephan Diestelhorst , xen-devel@lists.sourceforge.net, ian.pratt@cl.cam.ac.uk List-Id: xen-devel@lists.xenproject.org vbetool uses the same lrmi library as ddcprobe it might be easier to debug. http://www.srcf.ucam.org/~mjg59/vbetool/ On Tue, 22 Feb 2005 22:59:19 -0000, Ian Pratt wrote: > > > I wonder if we're just not mapping certain physical addresses > > into vm86 mode (in domain 0) that the program expects there to > > be ... > > If ddcprobe is using vm86 mode shouldn't it be mapping the appropriate > section of /dev/mem that it expects the 16bit code to access? Its not > attempting BIOS calls is it? > > BTW, where are the 'moving parts' of ddcprobe? I can only find the > python wrapper. > > Ian > -- Jon Smirl jonsmirl@gmail.com ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click