I have attached a patch that enables support for direct use of Intel GPUs in
QEMU. With this you can build the libdrm and mesa on for instance an AArch64
emulated system and have native OpenGL support inside QEMU.
The code has been sitting around on my drive for a year, and isn't quite as
polis
On Fri, Sep 22, 2017 at 8:14 AM, Peter Maydell wrote:
> On 22 September 2017 at 16:11, Abhijit Ray Chaudhury
> wrote:
>> Hi Peter,
>>
>> Thanks for your prompt response. I have gone through target
>> description xml format for gdb
>> (https://sourceware.org/gdb//onlinedocs/gdb/ARM-Features.html#A
On 22 September 2017 at 16:11, Abhijit Ray Chaudhury
wrote:
> Hi Peter,
>
> Thanks for your prompt response. I have gone through target
> description xml format for gdb
> (https://sourceware.org/gdb//onlinedocs/gdb/ARM-Features.html#ARM-Features)
> . I could not find a feature description matching
Hi Peter,
Thanks for your prompt response. I have gone through target
description xml format for gdb
(https://sourceware.org/gdb//onlinedocs/gdb/ARM-Features.html#ARM-Features)
. I could not find a feature description matching cp15 registers.So
even if I implement some subset of it would gdb under
On 22 September 2017 at 11:39, Abhijit Ray Chaudhury
wrote:
> I want to view ARM CP15 register sets via gdb when I am emulating arm.
> However I only see ARM Core Register Sets and NEON registers through
> gdb interface.
>
> Can you please let me know how to add cp15 register set support using
> g
Hi,
I want to view ARM CP15 register sets via gdb when I am emulating arm.
However I only see ARM Core Register Sets and NEON registers through
gdb interface.
Can you please let me know how to add cp15 register set support using
gdb interface in qemu.
Thanks in advance,
-Abhijit
> On 2 Dec 2016, at 12:24, Peter Maydell wrote:
>
> Right, but if you have a bug which requires your application to
> sit there processing for half an hour (or even five minutes)
> before it appears, it's nice not to spend that time.
fully agree. for physical targets, the GNU ARM Eclipse debugg
On 2 December 2016 at 10:12, Liviu Ionescu wrote:
> I see your point, and I'm convinced that for your use cases booting
> linux and starting applications is a big deal of effort.
>
> for the bare metal use cases, "going through the bootup process"
> is quite lightwheight, setting a few registers a
> On 2 Dec 2016, at 11:40, Peter Maydell wrote:
>
>> ... integrate this feature in the usual debugging workflow.
>
> The most useful approach is that you can set up a complicated
> situation (eg "boot my embedded RTOS, start application"),
> snapshot at that point, and then you can repeatedly r
On 1 December 2016 at 19:45, Liviu Ionescu wrote:
>
>> On 1 Dec 2016, at 21:13, Peter Maydell wrote:
>>
>> You need a QCOW2 disk to store the snapshots on, ...
>> Taking savevm snapshots doesn't need any cooperation
>> from the guest OS ..
>> I don't know whether anybody's tested this with M prof
> On 1 Dec 2016, at 21:13, Peter Maydell wrote:
>
> You need a QCOW2 disk to store the snapshots on, ...
> Taking savevm snapshots doesn't need any cooperation
> from the guest OS ..
> I don't know whether anybody's tested this with M profile:
does your Stellaris board support this?
assuming I
On 1 December 2016 at 18:39, Liviu Ionescu wrote:
> as for snapshotting, I'm not sure how I can use this for bare
> metal devices (hints highly appreciated).
You need a QCOW2 disk to store the snapshots on, but it
doesn't actually need to be accessible to the guest system,
so it should work fine
> On 1 Dec 2016, at 16:38, Peter Maydell wrote:
> ... network device backends ... is a fair bit of work.
yes, that's a good point, and I also plan to add Ethernet support to some of my
boards, but I need first to fix some issues that I consider more important,
like Cortex-M system peripherals
On 1 December 2016 at 13:33, Liviu Ionescu wrote:
>> On 1 Dec 2016, at 14:38, Peter Maydell wrote:
>>
>> ... clean up QEMU's code so
>> that it is less interdependent ...
>
> that's a good idea anyway, but this does not address the current issue.
>
> if I'd have a separate library with ARM TCG, f
> On 1 Dec 2016, at 14:38, Peter Maydell wrote:
>
> ... clean up QEMU's code so
> that it is less interdependent ...
that's a good idea anyway, but this does not address the current issue.
if I'd have a separate library with ARM TCG, for Cortex-M emulation I'd
probably write a simple memory m
On 1 December 2016 at 11:54, Liviu Ionescu wrote:
>
>> On 1 Dec 2016, at 10:50, Paolo Bonzini wrote:
>>
>>> But why only linux-user and not full system emulation too?
>>
>> It would simplify the library. The front-end and helpers have some
>> differences
>> between usermode and softmmu, and the
> On 1 Dec 2016, at 10:50, Paolo Bonzini wrote:
>
>> But why only linux-user and not full system emulation too?
>
> It would simplify the library. The front-end and helpers have some
> differences
> between usermode and softmmu, and the latter is much more intertwined with
> the rest of the Q
- Original Message -
> From: "Alessandro Di Federico"
> To: "Paolo Bonzini" , "Liviu Ionescu"
> Cc: "qemu-devel"
> Sent: Thursday, December 1, 2016 12:01:12 AM
> Subject: Re: [Qemu-devel] Support for using TCG frontend as a
On Tue, 29 Nov 2016 17:26:59 +0100
Paolo Bonzini wrote:
> It's pretty clean! I would rather avoid the duplicate enums, possibly
> by automatically generating large parts of ptc.h, but that's pretty
> much it. I see that you check that the constants match (that cpp
> stuff is disgusting :)), and
> On 29 Nov 2016, at 18:26, Paolo Bonzini wrote:
>
> ... It's pretty clean! ...
if you manage to make the TCG frontend as a library, it would be great to check
that it can also be used from C++.
the current QEMU headers prevent this, by using C++ reserved words (like
`class`), which is a re
On 27/11/2016 20:32, Alessandro Di Federico wrote:
>
> I've been investigating the needs of the various projects that might be
> interested in using it and they sum up to the following:
>
> * Be able to load in the same process multiple libtcg-$ARCH.so for
> different architectures.
> * Obtai
Hi all,
QEMU is a great emulator, but in recent years it has also been used
for instrumentation purposes [QIRA,AFL] or as a lifter for static
analysis purposes [rev.ng,angr,libqemu,S²E]. I'd like to hear your
take on the second use case, and the possibility of offering upstream
support for it.
T
hi !
Do you have an emailadress where I can send questions to about qemu ?
I have some questions about the stealth abilities of qemu
Stephan
On Thursday 26 March 2015 09:34:14 James Hogan wrote:
> On 26/03/15 09:29, Leon Alrae wrote:
> > Hi Duarte,
> >
> > On 25/03/2015 23:54, Duarte Silva wrote:
> >> On Wednesday 25 March 2015 17:33:59 Leon Alrae wrote:
> >>> On 25/03/2015 15:38, Duarte Silva wrote:
> On Wednesday 25 March 2015 1
On 26/03/15 09:29, Leon Alrae wrote:
> Hi Duarte,
>
> On 25/03/2015 23:54, Duarte Silva wrote:
>> On Wednesday 25 March 2015 17:33:59 Leon Alrae wrote:
>>> On 25/03/2015 15:38, Duarte Silva wrote:
On Wednesday 25 March 2015 14:54:41 Leon Alrae wrote:
> On 25/03/2015 14:44, Leon Alrae wrot
Hi Duarte,
On 25/03/2015 23:54, Duarte Silva wrote:
> On Wednesday 25 March 2015 17:33:59 Leon Alrae wrote:
>> On 25/03/2015 15:38, Duarte Silva wrote:
>>> On Wednesday 25 March 2015 14:54:41 Leon Alrae wrote:
On 25/03/2015 14:44, Leon Alrae wrote:
> Hi Duarte,
>
> On 25/03/2015 1
On Wednesday 25 March 2015 17:33:59 Leon Alrae wrote:
> On 25/03/2015 15:38, Duarte Silva wrote:
> > On Wednesday 25 March 2015 14:54:41 Leon Alrae wrote:
> >> On 25/03/2015 14:44, Leon Alrae wrote:
> >>> Hi Duarte,
> >>>
> >>> On 25/03/2015 14:20, Duarte Silva wrote:
> On Wednesday 25 March
On 25/03/2015 15:38, Duarte Silva wrote:
> On Wednesday 25 March 2015 14:54:41 Leon Alrae wrote:
>> On 25/03/2015 14:44, Leon Alrae wrote:
>>> Hi Duarte,
>>>
>>> On 25/03/2015 14:20, Duarte Silva wrote:
On Wednesday 25 March 2015 13:13:14 James Hogan wrote:
> Hi Duarte,
>
> On 22/0
On Wednesday 25 March 2015 14:54:41 Leon Alrae wrote:
> On 25/03/2015 14:44, Leon Alrae wrote:
> > Hi Duarte,
> >
> > On 25/03/2015 14:20, Duarte Silva wrote:
> >> On Wednesday 25 March 2015 13:13:14 James Hogan wrote:
> >>> Hi Duarte,
> >>>
> >>> On 22/03/15 11:13, Duarte Silva wrote:
> Hi
On 25/03/2015 14:44, Leon Alrae wrote:
> Hi Duarte,
>
> On 25/03/2015 14:20, Duarte Silva wrote:
>> On Wednesday 25 March 2015 13:13:14 James Hogan wrote:
>>> Hi Duarte,
>>>
>>> On 22/03/15 11:13, Duarte Silva wrote:
Hi guys,
I have been struggling to get some binaries compiled for
Hi Duarte,
On 25/03/2015 14:20, Duarte Silva wrote:
> On Wednesday 25 March 2015 13:13:14 James Hogan wrote:
>> Hi Duarte,
>>
>> On 22/03/15 11:13, Duarte Silva wrote:
>>> Hi guys,
>>>
>>> I have been struggling to get some binaries compiled for NetLogic XLP
>>> processor to run under QEMU. I have
On Wednesday 25 March 2015 13:13:14 James Hogan wrote:
> Hi Duarte,
>
> On 22/03/15 11:13, Duarte Silva wrote:
> > Hi guys,
> >
> > I have been struggling to get some binaries compiled for NetLogic XLP
> > processor to run under QEMU. I have tried a bunch of things (most going
> > back and forth)
Hi Duarte,
On 22/03/15 11:13, Duarte Silva wrote:
> Hi guys,
>
> I have been struggling to get some binaries compiled for NetLogic XLP
> processor to run under QEMU. I have tried a bunch of things (most going back
> and forth) and always get the following error message:
>
> qemu: uncaught targ
Hi guys,
could anybody help out? Is there a guide on how to implement new CPU's in QEMU
(or that at least helps in that task) or on how to debug this kind of stuff?
Cheers,
Duarte
On Sunday 22 March 2015 11:13:37 Duarte Silva wrote:
> Hi guys,
>
> I have been struggling to get some binaries co
Hi guys,
I have been struggling to get some binaries compiled for NetLogic XLP
processor to run under QEMU. I have tried a bunch of things (most going back
and forth) and always get the following error message:
qemu: uncaught target signal 4 (Illegal instruction) - core dumped
Illegal instructi
On Tue, Jan 28, 2014 at 7:40 AM, Peter Maydell wrote:
> On 27 January 2014 21:05, Romanic Dean wrote:
>> Just a small a query here,Can we call different Ethernet Controllers like
>> Broadcom or e1000 from VersatilePB board.
>>
>> Is VersatilePB board only supports SMSC series of controllers?
>
>
On 27 January 2014 21:05, Romanic Dean wrote:
> Just a small a query here,Can we call different Ethernet Controllers like
> Broadcom or e1000 from VersatilePB board.
>
> Is VersatilePB board only supports SMSC series of controllers?
You need to distinguish:
* what does the real hardware do?
*
Thanks Peter for your thoughts.
We are able to call lan9118 controller from VersatilePB board. We made
little modification to our guest OS.
Just a small a query here,Can we call different Ethernet Controllers like
Broadcom or e1000 from VersatilePB board.
Is VersatilePB board only supports SMSC
On 27 January 2014 16:55, Romanic Dean wrote:
> We are trying to provide support for Emulated SMSC911X Ethernet
> controller.Current Qemu already had support for SMSC91X controller which
> looks near SMSC91X controller.
We already support the SMSC 9118 (see hw/net/lan9118.c).
What do you need tha
We are trying to provide support for Emulated SMSC911X Ethernet
controller.Current Qemu already had support for SMSC91X controller which
looks near SMSC91X controller.
For providing support to SMSC911x we have done the following modifications
related to kernel changes :
1. modified the versatile
On Thu, Jul 18, 2013 at 5:05 AM, Hannes Reinecke wrote:
> On 07/15/2013 03:21 PM, Oleksii Shevchuk wrote:
>> I tried do run QEMU with OVMF UEFI bios (QEMU and EDK2 trunk). It hangs
>> while booting:
>>
>> qemu-kvm -L . -bios OVMF.fd --enable-kvm -debugcon file:/tmp/debug
>> -global isa-debugcon.
On 07/15/2013 03:21 PM, Oleksii Shevchuk wrote:
I tried do run QEMU with OVMF UEFI bios (QEMU and EDK2 trunk). It hangs
while booting:
qemu-kvm -L . -bios OVMF.fd --enable-kvm -debugcon file:/tmp/debug
-global isa-debugcon.iobase=0x402 -global PIIX4_PM.disable_s3=0 -global
PIIX4_PM.disable_
I tried do run QEMU with OVMF UEFI bios (QEMU and EDK2 trunk). It hangs
while booting:
qemu-kvm -L . -bios OVMF.fd --enable-kvm -debugcon file:/tmp/debug
-global isa-debugcon.iobase=0x402 -global PIIX4_PM.disable_s3=0 -global
PIIX4_PM.disable_s4=0
SecCoreStartupWithStack(0xFFFE6000, 0x8)
F
I tried do run QEMU with OVMF UEFI bios (QEMU and EDK2 trunk). It hangs
while booting:
qemu-kvm -L . -bios OVMF.fd --enable-kvm -debugcon file:/tmp/debug
-global isa-debugcon.iobase=0x402 -global PIIX4_PM.disable_s3=0 -global
PIIX4_PM.disable_s4=0
SecCoreStartupWithStack(0xFFFE6000, 0x8)
F
Josh,
Somehow missed this message going by. Sorry about that.
The 720p support patch (and variable VRAM size) slipped off my radar.
I'm going to try and get another batch of interesting patches from the
XenClient Enterprise device model ready to submit in the coming weeks,
and I'll add that o
Thanks!
- Josh Triplett
On Fri, May 03, 2013 at 04:41:51PM -0400, John Baboval wrote:
> Josh,
>
> Somehow missed this message going by. Sorry about that.
>
> The 720p support patch (and variable VRAM size) slipped off my
> radar. I'm going to try and get another batch of interesting patches
> f
Gerd Hoffmann writes:
> Hi,
>
>>> What is your vnc client? Does it support VNC_ENCODING_EXT_KEY_EVENT?
>>
>> It's uses gvnc as a protocol library and renders via fbdev. It reads
>> keyboard events by putting /dev/tty into mediumraw mode and uses ext key
>> events exclusively. It has no know
Hi,
>> What is your vnc client? Does it support VNC_ENCODING_EXT_KEY_EVENT?
>
> It's uses gvnc as a protocol library and renders via fbdev. It reads
> keyboard events by putting /dev/tty into mediumraw mode and uses ext key
> events exclusively. It has no knowledge of the guest keymap.
Neat
Gerd Hoffmann writes:
> On 04/15/13 16:41, Anthony Liguori wrote:
>> Gerd Hoffmann writes:
>>
>>> Hi,
>>>
When access a guest by console through VNC, there might be
mismatch between the lock keys notification LED on the computer
running the VNC client session and the current st
On 04/15/13 16:41, Anthony Liguori wrote:
> Gerd Hoffmann writes:
>
>> Hi,
>>
>>> When access a guest by console through VNC, there might be
>>> mismatch between the lock keys notification LED on the computer
>>> running the VNC client session and the current status of the lock
>>> keys on the
Gerd Hoffmann writes:
> Hi,
>
>> When access a guest by console through VNC, there might be
>> mismatch between the lock keys notification LED on the computer
>> running the VNC client session and the current status of the lock
>> keys on the guest machine. This happens because the VNC protocol
Hi,
> When access a guest by console through VNC, there might be
> mismatch between the lock keys notification LED on the computer
> running the VNC client session and the current status of the lock
> keys on the guest machine. This happens because the VNC protocol
> does not have any support to
Hi,
This proposal aims to add support for VNC LED state extension to
Qemu VNC server. It also contains the proposal of this VNC extension,
althrough it should be sent to some other mailing, but we'd like to
send to Qemu mailing list first to have your suggestion. Please
let me know your ideas and
Late last year, I saw a patch go by adding support for the unfortunately
common 1366x768 resolution. Some discussion in the resulting thread
suggested some possible improvements to the patch that needed to occur
before merging; however, I haven't seen a newer version go by. Just
wanted to check b
On Sun, Jul 29, 2012 at 9:46 AM, potworyk wrote:
> All,
>
> I woudl like to make it possible to compile devices (hw/*) as shared
> libraries and load them dynamicaly. This would make it easier to
> develop emulators for new hardware.
>
> I am completly new to QEMU develpment so i would like to ask
All,
I woudl like to make it possible to compile devices (hw/*) as shared
libraries and load them dynamicaly. This would make it easier to
develop emulators for new hardware.
I am completly new to QEMU develpment so i would like to ask you guys,
QEMU Architects if you have any idea how it could b
On Sun, Mar 04, 2012 at 01:28:04AM +0800, 陳韋任 wrote:
> > Also I am trying to understand the QEMU source with an objective of
> > participating in the Google Summer of Code and contributing to QEMU. I have
> > tried tracing through the code but seems this link
> > http://repo.or.cz/w/qemu/stefanh
On Sat, Mar 10, 2012 at 04:44:27PM -0500, Ankur Agrawal wrote:
> I am a graduate student at Stony Brook University and am working on design
> and implementation of hypervisors for OSCAR lab (
> http://oscar.cs.stonybrook.edu/). Currently I am working on implementing
> emulation of Nested Page Table
Hi,
Thanks for your reply.
I am a graduate student at Stony Brook University and am working on design
and implementation of hypervisors for OSCAR lab (
http://oscar.cs.stonybrook.edu/). Currently I am working on implementing
emulation of Nested Page Tables in QEMU as present in AMD-V architecture
> Does QEMU emulate the Nested Page Tables implemented by AMD-V architecture or
> the Intel VT?
I think the answer is no.
> Also I am trying to understand the QEMU source with an objective of
> participating in the Google Summer of Code and contributing to QEMU. I have
> tried tracing throu
Hi,
I am a student currently working on development of a Hypervisor for JOS
Operating System.
I run JOS over QEMU's emulation of x86 architecture. Currently I am planning to
add Nested Page Table support to JOS.
Does QEMU emulate the Nested Page Tables implemented by AMD-V architecture or
the
> > "objcopy -I elf64-x86-64 -O elf32-i386 64.elf 32.elf" worked for me.
> > Relocations get a bit confused, but you shouldn't have relocations in
> > your multiboot images to start with.
>
> Why no relocations? Isn't exactly that the advantage of building an elf
> image, that you can build a relo
Paul Brook writes:
>> Paul Brook writes:
>> >> > starting your own toy kernel is a fun thing to do and there are many
>> >> > tutorials out there on how to do it. Unfortunately when one wants to
>> >> > write a kernel in 64bit it becomes much harder because one can't
>> >> > compile 64bit code a
> Paul Brook writes:
> >> > starting your own toy kernel is a fun thing to do and there are many
> >> > tutorials out there on how to do it. Unfortunately when one wants to
> >> > write a kernel in 64bit it becomes much harder because one can't
> >> > compile 64bit code as elf32 image and converti
Paul Brook writes:
>> > starting your own toy kernel is a fun thing to do and there are many
>> > tutorials out there on how to do it. Unfortunately when one wants to
>> > write a kernel in 64bit it becomes much harder because one can't
>> > compile 64bit code as elf32 image and converting a elf6
> > starting your own toy kernel is a fun thing to do and there are many
> > tutorials out there on how to do it. Unfortunately when one wants to
> > write a kernel in 64bit it becomes much harder because one can't
> > compile 64bit code as elf32 image and converting a elf64 image to
> > elf32 form
On Wed, Feb 8, 2012 at 9:53 AM, Goswin von Brederlow wrote:
> Stefan Hajnoczi writes:
>
>> On Sat, Feb 4, 2012 at 5:38 PM, Goswin von Brederlow
>> wrote:
>>> Description: Allow 64bit elf binaries in multiboot format
>>> This patch allows 64bit elf files with multiboot header to be loaded.
>>>
Am 08.02.2012 10:53, schrieb Goswin von Brederlow:
> Stefan Hajnoczi writes:
>
>> On Sat, Feb 4, 2012 at 5:38 PM, Goswin von Brederlow
>> wrote:
>>> Description: Allow 64bit elf binaries in multiboot format
>>> This patch allows 64bit elf files with multiboot header to be loaded.
>>> The entr
Stefan Hajnoczi writes:
> On Sat, Feb 4, 2012 at 5:38 PM, Goswin von Brederlow
> wrote:
>> Description: Allow 64bit elf binaries in multiboot format
>> This patch allows 64bit elf files with multiboot header to be loaded.
>> The entry point will still be called in 32bit mode and the kernel
>>
On Sat, Feb 4, 2012 at 5:38 PM, Goswin von Brederlow wrote:
> Description: Allow 64bit elf binaries in multiboot format
> This patch allows 64bit elf files with multiboot header to be loaded.
> The entry point will still be called in 32bit mode and the kernel
> must switch to 64bit mode on its
Hi,
starting your own toy kernel is a fun thing to do and there are many
tutorials out there on how to do it. Unfortunately when one wants to
write a kernel in 64bit it becomes much harder because one can't
compile 64bit code as elf32 image and converting a elf64 image to
elf32 format is a maj
On 9/08/11 12:12 AM, Benjamin Herrenschmidt wrote:
> On Mon, 2011-08-08 at 15:57 +0200, Alexander Graf wrote:
>>> Anyone working on Freescale MPC8xx (embedded PowerPC) processors ??
>>>
>>> I'm trying to ascertain if the MPC8xx (MPC850) processors are
>>> supported, and if not, how much effort woul
On Mon, 2011-08-08 at 15:57 +0200, Alexander Graf wrote:
> > Hi,
> >
> > Anyone working on Freescale MPC8xx (embedded PowerPC) processors ??
> >
> > I'm trying to ascertain if the MPC8xx (MPC850) processors are
> > supported, and if not, how much effort would be required to get it
> > working.
>
On 08.08.2011, at 03:36, Brendan Simon (eTRIX) wrote:
> Hi,
>
> Anyone working on Freescale MPC8xx (embedded PowerPC) processors ??
>
> I'm trying to ascertain if the MPC8xx (MPC850) processors are supported, and
> if not, how much effort would be required to get it working.
I'm not aware of
Hi,
Anyone working on Freescale MPC8xx (embedded PowerPC) processors ??
I'm trying to ascertain if the MPC8xx (MPC850) processors are supported,
and if not, how much effort would be required to get it working.
Thanks for any help.
Brendan.
On 5/08/11 9:31 PM, Brendan Simon (eTRIX) wrote:
> Hel
Hello,
Does QEMU support the Freescale MPC8xx (MPC850) processors or platforms
(e.g FADS860) ??
Googling shows some code that suggests that it is not supported.
> cpu_abort(env, "/MPC8xx/ MMU model is not implemented\n");
If not supported, does anyone have any idea how much work there woul
Hi,
I've been looking into the multiboot2 specs and started to implement
them for kvm for Debian. If anyone wants to try them out or help
complete support for them I've uploaded a first patch and example kernel
to the Debian BTS [1]. The kernel boots but only the essential features
are there yet.
On Fri, 4 Feb 2011, Aurelien Jarno wrote:
On Thu, Feb 03, 2011 at 10:05:36AM +0100, xeros wrote:
Hi,
Hi,
I'd like to ask about support for newer CPUs in QEMU, like this one:
system type : BCM3556C0 DTV platform
processor : 0
cpu model : Broadcom BMIPS
On Sun, Feb 06, 2011 at 05:20:54PM +0100, xeros wrote:
> On Fri, 4 Feb 2011, Aurelien Jarno wrote:
>
>> On Thu, Feb 03, 2011 at 10:05:36AM +0100, xeros wrote:
>>> Hi,
>>
>> Hi,
>>
>>> I'd like to ask about support for newer CPUs in QEMU, like this one:
>>> system type : BCM3556C0 DTV pl
On Thu, Feb 03, 2011 at 10:05:36AM +0100, xeros wrote:
> Hi,
Hi,
> I'd like to ask about support for newer CPUs in QEMU, like this one:
> system type : BCM3556C0 DTV platform
> processor : 0
> cpu model : Broadcom BMIPS4380 V4.4 FPU V0.1
> BogoMIPS
Hi,
I'd like to ask about support for newer CPUs in QEMU, like this one:
system type : BCM3556C0 DTV platform
processor : 0
cpu model : Broadcom BMIPS4380 V4.4 FPU V0.1
BogoMIPS: 403.45
wait instruction: yes
microsecond timers :
> -Original Message-
> From: Rabin Vincent [mailto:rabin.vinc...@gmail.com] On Behalf Of Rabin
> Vincent
Hello Rabin,
> I've put up the current source at http://repo.or.cz/w/qemu/avr32.git,
> and a small README and some prebuilt kernel and busybox binaries to play
> with at http://rab.i
Boyapati, Anitha schrieb:
> Hello,
>
> We have a proposal to add support for AVR32 target emulation in Qemu. So far,
> we are able to build qemu from sources on windows using Mingw.
>
> Besides looking at sources for other targets in qemu tar ball, I have gone
> through docs for information on ho
> -Original Message-
> From: Rabin Vincent [mailto:rabin.vinc...@gmail.com] On Behalf Of Rabin
> Vincent
> Sent: Tuesday, October 27, 2009 9:33 PM
> To: Boyapati, Anitha
> Cc: qemu-devel@nongnu.org
> Subject: Re: [Qemu-devel] Support for new target emulator
>
&
On Fri, Oct 23, 2009 at 12:50:03PM +0200, Boyapati, Anitha wrote:
> We have a proposal to add support for AVR32 target emulation in Qemu.
I've been working on and off on AVR32 target support for a little while
now. It's still far from being complete or mergeable, but enough of the
architecture ha
>
> Btw now that I have someone from Atmel who apparently knows the
> architecture:
>
> Would virtualization work on AVR32? I mean, is there anything that
> would keep you from running kernel code in user mode and just trap
> everything?
Some attempts are going on with AP7 series. It is not th
On 23.10.2009, at 14:20, Boyapati, Anitha wrote:
It's great to see someone from Atmel actually taking on the
challenge!
I'd love to see AVR32 support in Qemu. It's FWIW the only completely
missing major target.
It was in queue for sometime now. As there is very little support
for AVR32 em
> On 23.10.2009, at 12:50, Boyapati, Anitha wrote:
>
>
> Luckily Uli just added support for s390x, so you can take a look at
> his patchset and see what needs to be done.
>
Yes. Recent S390x support should give us a good idea.
> The reason you should try to do things on Linux is that it's a
On 23.10.2009, at 13:44, Laurent Desnogues wrote:
On Fri, Oct 23, 2009 at 1:18 PM, Christoph Egger
wrote:
On Friday 23 October 2009 13:03:54 Alexander Graf wrote:
On 23.10.2009, at 12:50, Boyapati, Anitha wrote:
Hello,
We have a proposal to add support for AVR32 target emulation in
Qemu. S
On Fri, Oct 23, 2009 at 1:18 PM, Christoph Egger
wrote:
> On Friday 23 October 2009 13:03:54 Alexander Graf wrote:
>> On 23.10.2009, at 12:50, Boyapati, Anitha wrote:
>> > Hello,
>> >
>> > We have a proposal to add support for AVR32 target emulation in
>> > Qemu. So far, we are able to build qemu
On 23.10.2009, at 13:18, Christoph Egger wrote:
On Friday 23 October 2009 13:03:54 Alexander Graf wrote:
On 23.10.2009, at 12:50, Boyapati, Anitha wrote:
Hello,
We have a proposal to add support for AVR32 target emulation in
Qemu. So far, we are able to build qemu from sources on windows
usi
On Friday 23 October 2009 13:03:54 Alexander Graf wrote:
> On 23.10.2009, at 12:50, Boyapati, Anitha wrote:
> > Hello,
> >
> > We have a proposal to add support for AVR32 target emulation in
> > Qemu. So far, we are able to build qemu from sources on windows
> > using Mingw.
>
> I would suggest you
Boyapati, Anitha kirjoitti:
Hello,
We have a proposal to add support for AVR32 target emulation in Qemu. So far,
we are able to build qemu from sources on windows using Mingw.
Besides looking at sources for other targets in qemu tar ball, I have gone
through docs for information on how to sta
On 23.10.2009, at 12:50, Boyapati, Anitha wrote:
Hello,
We have a proposal to add support for AVR32 target emulation in
Qemu. So far, we are able to build qemu from sources on windows
using Mingw.
I would suggest you try and do this on Linux first. You'll see why
below.
Besides look
Hello,
We have a proposal to add support for AVR32 target emulation in Qemu. So far,
we are able to build qemu from sources on windows using Mingw.
Besides looking at sources for other targets in qemu tar ball, I have gone
through docs for information on how to start adding support for a new t
Hi,
I'm trying to get Juniper software running on QEMU. I've managed to get
it installed and operational however I can't setup a network interface
as the software is very specific about the type of network card it will
accept. In vmware you can do the following to have it emulate an intel
adapt
This set of patches allows 64-bit Solaris 10/11 X86 to compile qemu in a 64bit
environment. It requires a 64-bit libsdl, but has been tested with all the
tests
(sparc, arm, mips, mipsel, linux-i386, and DamnSmallLinux)
Ben
--- qemu.ORIG/Makefile.target 2007-05-16 07:59:39.0 -0400
+++ q
On Fri, Mar 16, 2007 at 04:31:36PM -0500, Todd T. Fries wrote:
> .. so now that aio is in, and whatever existed before is out, has anybody
> come up with a way to support host os's that do not have aio?
This is what I'm using.
Just manage to have '#define CONFIG_NO_AIO 1' in ./config-host.h.
Patc
.. so now that aio is in, and whatever existed before is out, has anybody
come up with a way to support host os's that do not have aio?
Thanks,
--
Todd Fries .. [EMAIL PROTECTED]
_
| \ 1.636.410.0632 (voice
Hello,
here is a little patch to add support for vga= when using -kernel.
Index: hw/pc.c
===
RCS file: /sources/qemu/qemu/hw/pc.c,v
retrieving revision 1.68
diff -u -r1.68 pc.c
--- hw/pc.c 10 Jan 2007 16:23:41 - 1.68
+++ hw/pc.c 1
1 - 100 of 109 matches
Mail list logo
