Stefan Weil <[EMAIL PROTECTED]> wrote:
> Hi,
>
> File eepro100.tar.bz2 (added to this mail) contains everything
> needed to add 3 new PCI network device (all similar to EEPRO100):
>
> eepro100.patch:
> Makefile.target:
> added two binaries needed for EEPRO100
> split en
On Monday 26 March 2007 22:37, andrzej zaborowski wrote:
> On 26/03/07, Marc Lörner <[EMAIL PROTECTED]> wrote:
> > On Monday 26 March 2007 00:08, andrzej zaborowski wrote:
> > > On 26/03/07, andrzej zaborowski <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > > > > +# warning non-optimized CPU
> > > > >
Hi Paul,
On Tuesday 27 March 2007 00:53, Paul Brook wrote:
> > > I moved to helper2.c because AFAICT helper.c is compiled with the same
> > > sort of restrictions as op.c which leads to the compile failure.
> >
> > Yes, helper.c is compiled with the global register variables and the code
> > is cal
If you've been running QEMU on SPARC Solaris 10 and using it for anything
including RTEMS development, you can now upgrade to the latest, bleeding
edge build of QEMU 0.9.0
http://www.thoughtwave.com/downloads.html
Have fun!
Jonathan
--
--
Jonathan Kalbfeld
+1 323 620 6682
> > I moved to helper2.c because AFAICT helper.c is compiled with the same
> > sort of restrictions as op.c which leads to the compile failure.
>
> Yes, helper.c is compiled with the global register variables and the code
> is called directly from the op_xxx functions, but one needs the global
> re
Hi,
kqemu doesn't trap the "rdtsc" instruction for performance reasons.
This is mostly okay on a uniprocessor host, but on a dual core CPU
there are effectively two TSCs and there's no warranty that they are
in sync. On my Linux desktop there happens to be about 17 seconds
difference between the
I don't have the current source repository, I'm running off of the
0.9.0 source release. However, I felt that there was a bug with having
the VM in fullscreen mode and still allowing the ctrl-alt modifiers to
release the mouse. With SDL, this is rather useless and only requires
the user to grab th
On 26/03/07, Marc Lörner <[EMAIL PROTECTED]> wrote:
On Monday 26 March 2007 00:08, andrzej zaborowski wrote:
> On 26/03/07, andrzej zaborowski <[EMAIL PROTECTED]> wrote:
> > > +# warning non-optimized CPU
> > > +#include
> > > +#include
> > > +
> > > static inline int64_t cpu_get_real_ticks (
Hi,
File eepro100.tar.bz2 (added to this mail) contains everything
needed to add 3 new PCI network device (all similar to EEPRO100):
eepro100.patch:
Makefile.target:
added two binaries needed for EEPRO100
split entries for PCI network devices (1 line / entry, better
merging wi
Hi,
On 26/03/07, Anthony Liguori <[EMAIL PROTECTED]> wrote:
andrzej zaborowski wrote:
> Hi, sorry for late reply.
>
> On 21/03/07, Anthony Liguori <[EMAIL PROTECTED]> wrote:
>> Do you think using the SDL cursor is all that useful? As soon as gtk
>> widgets get involved, the cursor becomes ARGB
Hi
I intend to extract program counter streams from QEMU as a program executes.
Can you please point me to the hooks that I may have to insert into the QEMU
source code in order to extract the PC values?
Also, since I'm new to QEMU, I'd appreciate if somebody can point me to some
documents which
Hi Avi,
On Sunday 25 March 2007 15:40, Avi Kivity wrote:
> Axel Zeuner wrote:
> > A full featured converter (cvtasm) has a lot of dependencies: it has to
> > support all hosts (M) (with all assembler dialects M') and all targets N,
> > i.e. in the worst case one would end with M'x N variants of it,
By now (more than two months after I sent it) this patch is less relevant, as
it is already included in Anthony's updated qemu-live-migration patch.
Is live migration going to be accepted soon ?
Regards,
Uri.
-Original Message-
From: [EMAIL PROTECTED] on behalf of Uri Lublin
Sent: W
Hi all
I have added support for a quad word memory / io access in QEMU.
Is it intersting enough for other people also? If yes then I can contribute.
Infact I would love to contribute.
Please Guide,
Thanks and Regards,
--
Gaurav J Nolkha
Bangalore, India.
Contact Nos.
Web: http://gnolkh
On Mon, Mar 26, 2007 at 01:54:43PM +, Julian Seward wrote:
>
> Does this fix some specific bug you encountered?
I have some code here that runs on Qemu but not on real hardware
due to this missing check.
Bernhard
> On Monday 26 March 2007 14:53, Bernhard Kauer wrote:
> > The Intel man
Does this fix some specific bug you encountered?
J
On Monday 26 March 2007 14:53, Bernhard Kauer wrote:
> The Intel manual states for LTR and 64-Bit Exceptions:
>
> #GP(selector)
>If the descriptor type of the upper 8-byte of the 16-byte descriptor
>is non-zero.
>
> Qemu curr
The Intel manual states for LTR and 64-Bit Exceptions:
#GP(selector)
If the descriptor type of the upper 8-byte of the 16-byte descriptor
is non-zero.
Qemu currently does not check this. The attached patch fixes the bug.
Bernhard Kauer
--- helper.c.orig 2007-03-26 15
On Monday 26 March 2007 00:08, andrzej zaborowski wrote:
> On 26/03/07, andrzej zaborowski <[EMAIL PROTECTED]> wrote:
> > > +# warning non-optimized CPU
> > > +#include
> > > +#include
> > > +
> > > static inline int64_t cpu_get_real_ticks (void)
> > > {
> > > -static int64_t ticks = 0;
>
Am Sat, 24 Mar 2007 12:55:16 +
schrieb Julian Seward <[EMAIL PROTECTED]>:
> The problems of the gcc backend to qemu have already been discussed
> extensively on this list. Stealing 3+ registers from gcc on x86 really
> is asking for trouble, and I believe it is generally understood that the
To let the list know, I don't know if I follow this, but, it turns out
if I build vgabios 0.6a locally I can get this to work. I have to use
the "fbdev" device driver in XFree86, but it works.
Also, when I build the new vgabios.bin, it turns out I have to specify
the "-L" command line option for
On 3/26/07, Kyle Hubert <[EMAIL PROTECTED]> wrote:
I tried using the newer video appendage and it didn't seem to work. I
had to use the older vga=. I believe you are talking about the kernel
boot param, yes?
yes. normally the vesafb-tng is supposed to address missing functions
or resolutions of
J. Mayer wrote:
> It appears that some targets may need more than the 2 "standard"
> execution modes.
> For example, PowerPC 64 has 3 execution modes: hypervisor, supervisor
> and problem state.
> Another example is alpha which has 4 execution modes (even if Linux
> seems to use only two of them).
no obvious problem in the xf86config file.
when all fails, use the framebuffer :) and Xfbdev (fbdev driver instead
of vesa)
The framebuffer seems to miss every other vertical scan line. I'm not
sure if I make sense, but the video wraps around the screen onto
itself vertically. Thus rendering hal
23 matches
Mail list logo
