 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] vm86 - DCC probes don't work
| To: | Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] vm86 - DCC probes don't work |
| From: | Jon Smirl <jonsmirl@xxxxxxxxx> |
| Date: | Tue, 22 Feb 2005 18:38:38 -0500 |
| Cc: | Rik van Riel <riel@xxxxxxxxxx>, Stephan Diestelhorst <sd386@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx, ian.pratt@xxxxxxxxxxxx |
| Delivery-date: | Tue, 22 Feb 2005 23:39:31 +0000 |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=fkJ8GTVUcC7iD4JDKwfTHYG7dvbqVJq6g5iMtgfOiTPmO5VspIxjwDyzAcXGD0xj0NuMRZDsQYgnxPoo9e68/LUSsZZvKcw9Q/z8SZxB3c6XqABH1RMP4S6dmwRPnsHwMyfC6k6IpmykMqdEF3CmR2RC/nsiihJ/gzgZqsMLAmI= |
| Envelope-to: | xen+James.Bulpin@xxxxxxxxxxxx |
| In-reply-to: | <A95E2296287EAD4EB592B5DEEFCE0E9D123A24@xxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| List-archive: | <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel> |
| List-help: | <mailto:xen-devel-request@lists.sourceforge.net?subject=help> |
| List-id: | List for Xen developers <xen-devel.lists.sourceforge.net> |
| List-post: | <mailto:xen-devel@lists.sourceforge.net> |
| List-subscribe: | <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe> |
| List-unsubscribe: | <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe> |
| References: | <A95E2296287EAD4EB592B5DEEFCE0E9D123A24@xxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| Reply-to: | Jon Smirl <jonsmirl@xxxxxxxxx> |
| Sender: | xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx |
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 <m+Ian.Pratt@xxxxxxxxxxxx> 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@xxxxxxxxx ------------------------------------------------------- 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 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-devel] [PATCH] serial-split.c, Charles Coffing |
|---|---|
| Next by Date: | Re: [Xen-devel] Floating Point Exception when compiling w/ gcc, Keir Fraser |
| Previous by Thread: | RE: [Xen-devel] vm86 - DCC probes don't work, Ian Pratt |
| Next by Thread: | [Xen-devel] [PATCH] Add very verbose output to xcsdump, Anthony Liguori |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
