From: Jon Smirl <jonsmirl@gmail.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Rik van Riel <riel@redhat.com>,
Stephan Diestelhorst <sd386@cam.ac.uk>,
xen-devel@lists.sourceforge.net, ian.pratt@cl.cam.ac.uk
Subject: Re: vm86 - DCC probes don't work
Date: Tue, 22 Feb 2005 18:38:38 -0500 [thread overview]
Message-ID: <9e473391050222153862128de0@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D123A24@liverpoolst.ad.cl.cam.ac.uk>
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@cl.cam.ac.uk> 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
next prev parent reply other threads:[~2005-02-22 23:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 22:59 vm86 - DCC probes don't work Ian Pratt
2005-02-22 23:38 ` Jon Smirl [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-22 22:25 Ian Pratt
2005-02-22 22:31 ` Rik van Riel
2005-02-22 22:54 ` Jon Smirl
2005-02-22 18:45 Rik van Riel
2005-02-22 20:18 ` Jon Smirl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9e473391050222153862128de0@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=riel@redhat.com \
--cc=sd386@cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.