Displaying 3 results from an estimated 3 matches for "outport".
2010 Nov 08
0
Re: What constitutes a good backtrace?
...gt;
> >
> >
> >
> > > When I get down around the failure this is what I see:
> > >
> > > 0015:Call winedos.inport(00000061,00000001) ret=7ee3f94e
> > > 0015:Ret winedos.inport() retval=00000020 ret=7ee3f94e
> > > 0015:Call winedos.outport(00000061,00000001,00000021) ret=7ee3f7c8
> > > 0015:Ret winedos.outport() retval=00000001 ret=7ee3f7c8
> > > 0015:Call winedos.outport(00000061,00000001,00000020) ret=7ee3f7c8
> > > 0015:Ret winedos.outport() retval=00000000 ret=7ee3f7c8
> > > 0015:Call winedos...
2008 Mar 07
9
What constitutes a good backtrace?
Hi all,
I did my first bug report in a while. Unfortunately the good folks
at wineHQ.org didn't like it much because Gentoo by default stripped
out much of the backtrace info. I've recompiled Wine with more
backtrace capabilities in it and am wondering what's considered good
enough.
Below are two backtraces. They may or may not be exactly the same
failure but they both come from
2012 Oct 08
21
[PATCH 00/14] Remove old_portio users for memory region PIO mapping
When running on PowerPC, we don''t have native PIO support. There are a few hacks
around to enable PIO access on PowerPC nevertheless.
The most typical one is the isa-mmio device. It takes MMIO requests and converts
them to PIO requests on the (QEMU internal) PIO bus.
This however is not how real hardware works and it limits us in the ability to
spawn eventfd''s on PIO ports