This patch make it aviable to save cpu runstate when do savevm,
and restore it when do loadvm, correspondingly. If qemu is started
with -S, then the saved runstate is ignored.
WARNING: this patch breaks backward migration compatibility, Paolo
thinks it's not worth it. But I'm still posting it for
On 15.03.2013 00:04, Davide Guerri wrote:
Yes this is definitely an option :)
Just for curiosity, what is the effect of "in-kernel irqchip"?
it emulates the irqchip in-kernel (in the KVM kernel module) which
avoids userspace exits to qemu. in your particular case I remember
that it made all IR
Hi, Juan and guys,
I'd like to add a new way to save vmstate, which will based on the
migration thread, but will write contents to block images, instead
of fd as stream. Following is the method to add API:
1 add parameters to migrate interface, and a new type of uri:
image:[VMSATE_SAVE_IMAGE]
#
I missed this one, because it wasn't cc'ed to QMP maintainers, the
subject mentions only command line, not QMP, and even the body talks
only about the human monitor command, not QMP. Noticed it only when
git-pull touched qapi-schema.json. Please try harder to help Luiz and
me keep track of QMP ch
Hu Tao writes:
> This patch make it aviable to save cpu runstate when do savevm,
> and restore it when do loadvm, correspondingly. If qemu is started
> with -S, then the saved runstate is ignored.
Why is saving runstate useful?
> WARNING: this patch breaks backward migration compatibility, Paol
This fix my problem in moving code to block/snapshot.c.
Reviewed-by: Wenchao Xia
--
Best Regards
Wenchao Xia
Am 15.03.2013 um 07:07 hat Wenchao Xia geschrieben:
> 于 2013-3-13 20:40, Stefan Hajnoczi 写道:
> >The same applies for VMDK where one .vmdk can reference multiple extent
> >files.
> >
> I'd like to confirm: This means a block device can have multiple
> images at top level, but one image can still h
Il 14/03/2013 18:57, Peter Maydell ha scritto:
> The main aim of this patchset is patch 2, which changes the coroutine
> backend selection logic so that it goes 'ucontext -> sigaltstack'
> rather than 'ucontext -> gthread', since the gthread backend is
> broken. To do this properly on all platforms
Il 15/03/2013 02:45, Asias He ha scritto:
> Device needs the exact size of these data structure. Prevent padding.
>
> This fixes guest hang when booting seabios + tcm_vhost.
>
> Signed-off-by: Asias He
> ---
> src/virtio-scsi.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> di
Am 15.03.2013 um 07:23 hat Wenchao Xia geschrieben:
> 于 2013-3-14 20:53, Kevin Wolf 写道:
> >Am 14.03.2013 um 13:10 hat Markus Armbruster geschrieben:
> >>Kevin Wolf writes:
> >>>But you have to do it right. This specific patch would introduce a
> >>>copyright violation. It's really not that hard to
Am 14.03.2013 um 17:06 hat Stefan Hajnoczi geschrieben:
> A comment explains that -nographic hangs test case 007. This is no
> longer the case so add -nographic. This makes the test suite faster and
> more pleasant to run since no windows pop up.
>
> I am not sure exactly when -nographic startin
Am 14.03.2013 um 16:52 hat Laszlo Ersek geschrieben:
> On 03/14/13 15:57, Kevin Wolf wrote:
> > Signed-off-by: Kevin Wolf
> > ---
> > After rebasing this I saw that Anthony already committed a fix that is
> > very close to my v1. I don't intend to actually change that code, but as
> > I've already
On Thu, Mar 14, 2013 at 03:52:16PM -0600, Eric Blake wrote:
> On 03/09/2013 03:22 PM, Stefan Hajnoczi wrote:
> > @block-backup
> >
> > Start a point-in-time copy of a block device to a new destination.
> >
>
> I'm trying to figure out how this is different from drive-mirror. If I
> understand c
On Fri, Mar 15, 2013 at 02:07:01PM +0800, Wenchao Xia wrote:
> 于 2013-3-13 20:40, Stefan Hajnoczi 写道:
> >This is why I asked about the array. A dict of ImageInfos is needed,
> >they can refer to each other by key.
> >
> >If we go with an array we're painting ourselves into a corner.
> >
> >If we g
On Thu, Mar 14, 2013 at 10:04:23AM +, Peter Maydell wrote:
> On 13 March 2013 12:34, Anthony Liguori wrote:
> > AioContext is necessary for the block layer because the block layer
> > still has synchronous I/O. I think we should aim to replace all sync
> > I/O in the long term with coroutine
From: KONRAD Frederic
This is the next part of virtio-refactoring.
Basically it creates virtio-blk device which extends virtio-device.
Then a virtio-blk can be connected on a virtio-bus.
virtio-blk-pci, virtio-blk-s390x, virtio-blk-ccw are created too, they extend
respectively virtio-pci, virtio
From: KONRAD Frederic
The configuration field must not be a pointer as it will be used for virtio-blk
properties. So *blk is replaced by blk in VirtIOBlock structure.
Signed-off-by: KONRAD Frederic
Reviewed-by: Peter Maydell
---
hw/virtio-blk.c | 8
hw/virtio-blk.h | 2 +-
2 files ch
From: KONRAD Frederic
These structures must be made public to avoid two memory allocations for
refactored virtio devices.
Signed-off-by: KONRAD Frederic
Reviewed-by: Andreas Färber
Reviewed-by: Peter Maydell
Changes V4 <- V3:
* Rebased on current git.
Changes V3 <- V2:
* Style correc
From: KONRAD Frederic
This set allow_hotplug for each existing virtio-x-bus, allowing the
refactored devices to be hot pluggable.
Signed-off-by: KONRAD Frederic
---
hw/s390x/s390-virtio-bus.c | 2 +-
hw/s390x/virtio-ccw.c | 2 +-
hw/virtio-pci.c| 2 +-
3 files changed, 3 inser
From: KONRAD Frederic
Here the virtio-blk-s390 is modified for the new API. The device
virtio-blk-s390 extends virtio-s390-device as before. It creates and
connects a virtio-blk during the init. The properties are not modified.
Signed-off-by: KONRAD Frederic
Reviewed-by: Peter Maydell
---
hw/
From: KONRAD Frederic
Here the virtio-blk-pci is modified for the new API. The device
virtio-blk-pci extends virtio-pci. It creates and connects a virtio-blk
during the init. The properties are not changed.
Signed-off-by: KONRAD Frederic
Reviewed-by: Peter Maydell
---
hw/virtio-pci.c | 121 ++
From: KONRAD Frederic
Here the virtio-ccw-s390 is modified for the new API. The device
virtio-ccw-s390 extends virtio-ccw-device as before. It creates and
connects a virtio-ccw during the init. The properties are not modified.
Signed-off-by: KONRAD Frederic
Reviewed-by: Peter Maydell
---
hw/s
From: KONRAD Frederic
Use QOM casts inside virtio-blk.
Signed-off-by: KONRAD Frederic
Reviewed-by: Peter Maydell
---
hw/virtio-blk.c | 33 ++---
hw/virtio-blk.h | 2 +-
2 files changed, 15 insertions(+), 20 deletions(-)
diff --git a/hw/virtio-blk.c b/hw/virtio-bl
From: KONRAD Frederic
Create virtio-blk which extends virtio-device, so it can be connected on
virtio-bus.
Signed-off-by: KONRAD Frederic
Reviewed-by: Peter Maydell
---
hw/virtio-blk.c | 98 ++---
hw/virtio-blk.h | 21 +
hw/virti
From: KONRAD Frederic
As all virtio-blk-* are switched to the new API, we can remove the separate
init/exit for the old API.
Signed-off-by: KONRAD Frederic
Reviewed-by: Peter Maydell
---
hw/virtio-blk.c | 85 ++---
hw/virtio.h | 2 --
2
From: KONRAD Frederic
The qdev field is no longer needed, just drop it.
Signed-off-by: KONRAD Frederic
Reviewed-by: Peter Maydell
---
hw/virtio-blk.c | 3 +--
hw/virtio-blk.h | 1 -
2 files changed, 1 insertion(+), 3 deletions(-)
diff --git a/hw/virtio-blk.c b/hw/virtio-blk.c
index 663edcd..
On 15/03/2013 10:16, fred.kon...@greensocs.com wrote:
From: KONRAD Frederic
This is the next part of virtio-refactoring.
Basically it creates virtio-blk device which extends virtio-device.
Then a virtio-blk can be connected on a virtio-bus.
virtio-blk-pci, virtio-blk-s390x, virtio-blk-ccw are
Signed-off-by: Lei Li
---
qga/commands-win32.c | 27 +--
1 file changed, 25 insertions(+), 2 deletions(-)
diff --git a/qga/commands-win32.c b/qga/commands-win32.c
index b19be9d..d98e3ee 100644
--- a/qga/commands-win32.c
+++ b/qga/commands-win32.c
@@ -22,6 +22,12 @@
#defi
This patch series attempts to add Windows implementation
for qemu-ga commands guest-get-time and guest-set-time.
The previous thread about the interfaces introduced and
the POSIX-specific command implementation has already
been accepted, the reference link:
http://article.gmane.org/gmane.comp.em
Signed-off-by: Lei Li
---
qga/commands-win32.c | 29 -
1 file changed, 28 insertions(+), 1 deletion(-)
diff --git a/qga/commands-win32.c b/qga/commands-win32.c
index d98e3ee..24e4ad0 100644
--- a/qga/commands-win32.c
+++ b/qga/commands-win32.c
@@ -309,7 +309,34 @@ int
v2:
- Fixed use after free for serial number
- Fixed id=... handling
- Fixed if=virtio overwriting opts
Kevin Wolf (8):
block: Add options QDict to .bdrv_open()
block: Add options QDict to bdrv_open() prototype
Add qdict_clone_shallow()
block: Add options QDict to bdrv_open_common()
qemu
Signed-off-by: Kevin Wolf
Reviewed-by: Eric Blake
Reviewed-by: Stefan Hajnoczi
---
include/qapi/qmp/qdict.h | 2 ++
qobject/qdict.c | 22 ++
2 files changed, 24 insertions(+)
diff --git a/include/qapi/qmp/qdict.h b/include/qapi/qmp/qdict.h
index 6d9a4be..685b2e3 1
Signed-off-by: Kevin Wolf
Reviewed-by: Eric Blake
Reviewed-by: Stefan Hajnoczi
---
block.c | 4 ++--
block/bochs.c | 2 +-
block/cloop.c | 2 +-
block/cow.c | 2 +-
block/dmg.c | 2 +-
block/parallels.c | 2 +-
block/
It doesn't do anything yet except storing the options QDict in the
BlockDriverState.
Signed-off-by: Kevin Wolf
Reviewed-by: Eric Blake
Reviewed-by: Stefan Hajnoczi
---
block.c | 47 +++
block/blkverify.c | 2 +-
block/qcow2
qcow2 images now accept a boolean lazy_refcounts options. Use it like
this:
-drive file=test.qcow2,lazy_refcounts=on
If the option is specified on the command line, it overrides the default
specified by the qcow2 header flags that were set when creating the
image.
Signed-off-by: Kevin Wolf
Re
Pointing to a QemuOpts element is surprising and can lead to subtle
use-after-free errors when the QemuOpts is freed after all options are
parsed.
Signed-off-by: Kevin Wolf
---
blockdev.c| 5 -
include/sysemu/blockdev.h | 2 +-
2 files changed, 5 insertions(+), 2 deletions(-)
Commit 259186a7 "cpu: Move halted and interrupt_request fields to CPUState"
seems to have missed one instance in target-s390x/kvm.c:
/home/cohuck/git/qemu/target-s390x/kvm.c: In function
‘kvm_arch_process_async_events’:
/home/cohuck/git/qemu/target-s390x/kvm.c:319: error: ‘CPUS390XState’ has no
On Thu, Mar 14, 2013 at 01:59:53PM +0100, Markus Armbruster wrote:
> Screwed up in commit 666daa68. Thanks to Kevin Wolf for reminding me
> to fix this.
>
> Signed-off-by: Markus Armbruster
> ---
> blockdev.c | 23 +++
> 1 file changed, 23 insertions(+)
Thanks, applied to m
On Thu, Mar 14, 2013 at 05:06:55PM +0100, Stefan Hajnoczi wrote:
> A comment explains that -nographic hangs test case 007. This is no
> longer the case so add -nographic. This makes the test suite faster and
> more pleasant to run since no windows pop up.
>
> I am not sure exactly when -nographi
Any non-default -drive options are now passed down to the block drivers.
Signed-off-by: Kevin Wolf
Reviewed-by: Eric Blake
Reviewed-by: Stefan Hajnoczi
---
blockdev.c | 69 +-
1 file changed, 59 insertions(+), 10 deletions(-)
diff --
This adds a function that adds all entries of a QDict to a QemuOpts if
the keys are known, and leaves only the rest in the QDict.
This way a single QDict of -drive options can be processed in multiple
places (generic block layer, block driver, backing file block driver,
etc.), where each part pick
The options are passed down to the block drivers, which are supposed to
remove all options they have processed. Anything that is left over in
the end is an unknown option and results in an error.
Signed-off-by: Kevin Wolf
Reviewed-by: Eric Blake
Reviewed-by: Stefan Hajnoczi
---
block.c | 32 ++
If no client is connected on the src side, then we won't receive a
parser during migrate, in this case usbredir_post_load() should be a nop,
rather then to try to derefefence the NULL dev->parser pointer.
Signed-off-by: Hans de Goede
---
hw/usb/redirect.c | 4
1 file changed, 4 insertions(+
On Thu, Mar 14, 2013 at 05:13:54PM +0100, Paolo Bonzini wrote:
> Il 14/03/2013 16:59, Gleb Natapov ha scritto:
> > On Thu, Mar 14, 2013 at 04:50:40PM +0100, Paolo Bonzini wrote:
> >> Il 14/03/2013 15:23, Gleb Natapov ha scritto:
> >>> On Thu, Mar 14, 2013 at 03:05:22PM +0100, Paolo Bonzini wrote:
>
This patch let configure tool print out which library
is missing besides the qemu feature name when it fails.
CC: Blue Swirl
CC: Anthony Liguori
Signed-off-by: Qingtang Zhou
---
configure | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/configure b/configure
On 15 March 2013 11:46, Qingtang Zhou wrote:
> This patch let configure tool print out which library
> is missing besides the qemu feature name when it fails.
just fyi, this is going to clash badly with the patch I posted to
the list yesterday to abstract out error message printing better.
> @@
On 03/14/2013 10:07 PM, Jesse Larrew wrote:
> On 03/14/2013 02:51 PM, Jan Kiszka wrote:
>> With this patch QEMU handles qAttached request from gdb. When QEMU
>> replies 1, GDB sends a "detach" command at the end of a debugging
>> session otherwise GDB sends "kill".
>>
>> The default value for qAtta
On 15.03.2013, at 10:57, Cornelia Huck wrote:
> Commit 259186a7 "cpu: Move halted and interrupt_request fields to CPUState"
> seems to have missed one instance in target-s390x/kvm.c:
>
> /home/cohuck/git/qemu/target-s390x/kvm.c: In function
> ‘kvm_arch_process_async_events’:
> /home/cohuck/git/
On 14.03.2013, at 02:53, David Gibson wrote:
> For PAPR guests, KVM tracks the various areas registered with the
> H_REGISTER_VPA hypercall. For full emulation, of course, these are tracked
> within qemu. At present these values are not synchronized. This is a
> problem for reset (qemu's reset
On 14.03.2013, at 02:53, David Gibson wrote:
> PAPR requires that the device tree's CPU nodes have several properties
> with information about the L1 cache. We already create two of these
> properties, but with incorrect names - "[id]cache-block-size" instead
> of "[id]-cache-block-size" (note t
On 14.03.2013, at 02:53, David Gibson wrote:
> Currently, the pseries machine initializes the cpus, then the XICS
> interrupt controller. However, to support the upcoming in-kernel XICS
> implementation we will need to initialize the irq controller before the
> vcpus. This patch makes the neces
Ping!
Thanks,
AG
On Sun, Mar 10, 2013 at 10:07 AM, Anthony Green wrote:
> This version of the patch includes a bug fix and some formatting fixes
> identified by Blue Swirl here:
>
> http://lists.gnu.org/archive/html/qemu-devel/2013-03/msg01530.html
>
> Please consider applying this version of
On 15.03.2013, at 06:04, Peter Crosthwaite wrote:
> These functions don't exist until glib version 2.26. QEMU is currently only
> mandating glib 2.12.
>
> This patch replaces the functions with g_key_file_get/set_integer.
>
> Unbreaks the build on Ubuntu 10.04 and RHEL 5.6.
>
> Regression was
On 14.03.2013, at 02:53, David Gibson wrote:
> target-ppc/kvm.c has an #ifdef on CONFIG_PSERIES, for the handling of
> KVM exits due to a PAPR hypercall from the guest. However, since commit
> e4c8b28cde12d01ada8fe869567dc5717a2dfcb7 "ppc: express FDT dependency of
> pSeries and e500 boards via
On 14.03.2013, at 02:53, David Gibson wrote:
> Currently the "spapr-pci-host-bridge" device has a "busname" property which
> can be used to override the default assignment of qbus names for the bus
> subordinate to the PHB. We use that for the default primary PCI bus, to
> make libvirt happy, wh
On 15.03.2013, at 04:59, David Gibson wrote:
> Commit 259186a7d2f7184efc96ae99bc5658e6159f53ad "cpu: Move halted and
> interrupt_request fields to CPUState" broke the pseries machine. That's
> because it uses CPU() instead of ENV_GET_CPU() to convert from the global
> first_cpu pointer (still a
Hi ! i am emulating mips on Qemu and while the kernel is booting ,i am
getting irq no. 7 from Qemu.Can any one tell what is the source for irq
no. 7 and how can i disable that??
Thanks
Nouman
On Fri, 15 Mar 2013 10:19:50 +0100
KONRAD Frédéric wrote:
> On 15/03/2013 10:16, fred.kon...@greensocs.com wrote:
> > From: KONRAD Frederic
> >
> > This is the next part of virtio-refactoring.
> >
> > Basically it creates virtio-blk device which extends virtio-device.
> > Then a virtio-blk can b
From: Kuo-Jung Su
These patches introduce Faraday A369 SoC platform support.
Here are some public documents for your reference.
http://www.faraday-tech.com/html/documentation/index.html
The partial version of faraday cpu datasheet with only
the CP15 and MPU description are available at my Goog
From: Kuo-Jung Su
The FTINTC020 interrupt controller supports both FIQ and IRQ signals
to the microprocessor.
It can handle up to 64 configurable IRQ sources and 64 FIQ sources.
The output signals to the microprocessor can be configured as
level-high/low active or edge-rising/falling triggered.
From: Kuo-Jung Su
It provides separate second, minute, hour, and day counters. The second
counter is toggled each second, the minute counter is toggled each minute,
the hour counter is toggled each hour, and the day counter is toggled each day.
The FTRTC011 provides a programmable auto-alarm fun
From: Kuo-Jung Su
It's used to perform AHB remap and QEMU RAM initialization
when the SDRAM is initialized before AHB remap process activated.
Signed-off-by: Kuo-Jung Su
---
hw/arm/Makefile.objs |1 +
hw/arm/faraday_a369_soc.c | 10 +++
hw/arm/ftahbc020.c| 202 +
From: Kuo-Jung Su
This patch includes the single core support to FA606TE, FA626TE,
FA616TE and FA726TE with CP15 Faraday extensions (AUX and I/D-Scratchpad).
Signed-off-by: Kuo-Jung Su
---
target-arm/cpu.c | 52 +++
target-arm/cpu.h |6 +++-
target-arm
From: Kuo-Jung Su
The FTPWMTMR010 is an APB device which provides up to 8 independent timers.
Signed-off-by: Kuo-Jung Su
---
hw/arm/Makefile.objs |1 +
hw/arm/faraday_a369_soc.c | 10 ++
hw/arm/ftpwmtmr010.c | 258 +
hw/arm/ftpwmtmr0
From: Kuo-Jung Su
The FTWDT010 is used to prevent system from infinite loop
while software gets trapped in the deadlock.
Under the normal operation, users should restart FTWDT010
at the regular intervals before counter counts down to 0.
If the counter does reach 0, FTWDT010 will try to reset
th
From: Kuo-Jung Su
The Faraday A369 EVB is a Faraday SoC platform evalution board used for
Faraday IP functional verification based on the well-known ARM AMBA 2.0
architecture.
Signed-off-by: Kuo-Jung Su
---
hw/arm/Makefile.objs |3 +
hw/arm/faraday.h | 52 ++
hw/arm
From: Kuo-Jung Su
These patches introduce Faraday A369 SoC platform support.
Here are some public documents for your reference.
http://www.faraday-tech.com/html/documentation/index.html
The partial version of faraday cpu datasheet with only
the CP15 and MPU description are available at my Goog
From: Kuo-Jung Su
It's used to perform AHB remap and QEMU RAM initialization
when the SDRAM is initialized before AHB remap process activated.
Signed-off-by: Kuo-Jung Su
---
hw/arm/Makefile.objs |1 +
hw/arm/faraday_a369_soc.c | 10 +++
hw/arm/ftahbc020.c| 202 +
From: Kuo-Jung Su
The FTDDRII030 is a DDRII SDRAM controller which is responsible for
SDRAM initialization.
In QEMU we emulate only the SDRAM enable function.
Signed-off-by: Kuo-Jung Su
---
hw/arm/Makefile.objs |1 +
hw/arm/faraday_a369_soc.c |9 +++
hw/arm/ftddrii030.c | 1
From: Kuo-Jung Su
The FTWDT010 is used to prevent system from infinite loop
while software gets trapped in the deadlock.
Under the normal operation, users should restart FTWDT010
at the regular intervals before counter counts down to 0.
If the counter does reach 0, FTWDT010 will try to reset
th
From: Kuo-Jung Su
The FTINTC020 interrupt controller supports both FIQ and IRQ signals
to the microprocessor.
It can handle up to 64 configurable IRQ sources and 64 FIQ sources.
The output signals to the microprocessor can be configured as
level-high/low active or edge-rising/falling triggered.
From: Kuo-Jung Su
It provides separate second, minute, hour, and day counters. The second
counter is toggled each second, the minute counter is toggled each minute,
the hour counter is toggled each hour, and the day counter is toggled each day.
The FTRTC011 provides a programmable auto-alarm fun
From: Kuo-Jung Su
Wolfson WM8731 is a simple audio codec for embedded systems.
It has 2 input and 1 output ports:
** Input **
1. Linue-In
2. Microphone
** Output **
1. Headphone out
BTW it's based on hw/wm8750.c with 16-bit I2S support by default.
Signed-off-by: Kuo-Jung Su
---
From: Kuo-Jung Su
The FTPWMTMR010 is an APB device which provides up to 8 independent timers.
Signed-off-by: Kuo-Jung Su
---
hw/arm/Makefile.objs |1 +
hw/arm/faraday_a369_soc.c | 10 ++
hw/arm/ftpwmtmr010.c | 258 +
hw/arm/ftpwmtmr0
From: Kuo-Jung Su
The FTMAC110 is an Ethernet controller that provides AHB master capability
and is in full compliance with the IEEE 802.3 10/100 Mbps specifications.
Its DMA controller handles all data transfers between system memory
and on-chip memories.
It supports half-word data transfer for
From: Kuo-Jung Su
The FTRTC011 QEMU model is implemented without calender functions.
It acts in counter mode only, all the time & timezone conversion
relies on the c runtime library. (i.e. mktime(), localtime() ...etc)
Signed-off-by: Kuo-Jung Su
---
tests/Makefile|3 +
tests/ftrtc0
From: Kuo-Jung Su
The FTTMR010 provides three independent sets of sub-timers.
Two match registers are provided for each sub-timer, whenever
the value of the match registers equals any one value of the
sub-timers, the timer interrupt will be immediately triggered.
And it would also issue an interr
From: Kuo-Jung Su
The Faraday FTDMAC020 provides eight configurable
channels for the memory-to-memory, memory-to-peripheral,
peripheral-to-peripheral, and peripheral-to-memory transfers.
Each DMA channel supports chain transfer and can be programmed
to one of the 16 handshaking channels in the h
From: Kuo-Jung Su
The FTAPBBRG020 supports the DMA functions for the AHB-to-AHB,
AHB-to-APB, APB-to-AHB, and APB-to-APB transactions.
The DMA engine can support up to 4 DMA channels (A, B, C, and D)
and 15 handshaking channels. A DMA channel granted by the arbiter
block is the only channel start
From: Kuo-Jung Su
Signed-off-by: Kuo-Jung Su
---
hw/Makefile.objs |1 +
hw/arm/spitz.c |9 +++--
hw/arm/z2.c|9 +++--
hw/audio_codec.c | 81 +++
hw/audio_codec.h | 56 ++
From: Kuo-Jung Su
The FTI2C010 is a simple I2C master controller.
Signed-off-by: Kuo-Jung Su
---
hw/arm/Makefile.objs |1 +
hw/arm/faraday_a369_soc.c |6 ++
hw/arm/fti2c010.c | 212 +
hw/arm/fti2c010.h | 71 +++
From: Kuo-Jung Su
The FTNANDC021 is an integrated NAND flash controller which
re-pack the NAND flash command set with a shorter built-in opcode.
It also provides a register base interface for user to easily
access the underlying NAND flash chips, and also supports HW ECC.
However the optional ha
From: Kuo-Jung Su
The FTSSP010 is a multi-function synchronous serial port interface
controller which supports SSP, SPI, I2S, AC97 and SPDIF.
Only I2S and SPI protocol have been implemented in this patch.
Signed-off-by: Kuo-Jung Su
---
hw/arm/Makefile.objs |1 +
hw/arm/faraday.h
From: Kuo-Jung Su
Signed-off-by: Kuo-Jung Su
---
include/qemu/bitops.h | 59 -
1 file changed, 58 insertions(+), 1 deletion(-)
diff --git a/include/qemu/bitops.h b/include/qemu/bitops.h
index affcc96..64cbb04 100644
--- a/include/qemu/bitops.h
From: Kuo-Jung Su
The FTLCDC200 Color LCD controller performs translation of
pixel-coded data into the required formats and timings to
drive a variety of single/dual mono and color LCDs.
Depending on the LCD type and mode, the unpacked data can represent:
1. an actual true display gray or col
From: Kuo-Jung Su
The FTTSC010 provides two operation modes to sample
the analog input voltage.
1. The manual operation mode needs to program
and control the panel drivers by software
step-by-step for the x-y position measurement.
2. The auto-scan mode provides a periodic sampling
From: Kuo-Jung Su
The FTSDC010 is a simple MMC/SD host controller and
many of its registers are similar to Arm PrimeCell PL181.
Signed-off-by: Kuo-Jung Su
---
hw/arm/Makefile.objs |1 +
hw/arm/faraday_a369_soc.c |7 +
hw/arm/ftsdc010.c | 354 ++
On 03/15/2013 03:36 AM, Markus Armbruster wrote:
I missed this one, because it wasn't cc'ed to QMP maintainers, the
subject mentions only command line, not QMP, and even the body talks
only about the human monitor command, not QMP. Noticed it only when
git-pull touched qapi-schema.json. Please
From: Kuo-Jung Su
The FTGMAC100 Ethernet controller has a DMA engine which handles
all data transfers between the system memory and on-chip memories.
Its DMA engine supports both 16-bits and 32-bits alignment,
and thus make it possible to support zero-copy transfer at both
Linux and WINCE.
It al
From: Kuo-Jung Su
The Faraday A369 EVB is a Faraday SoC platform evalution board used for
Faraday IP functional verification based on the well-known ARM AMBA 2.0
architecture.
Signed-off-by: Kuo-Jung Su
---
hw/arm/Makefile.objs |3 +
hw/arm/faraday.h | 52 ++
hw/arm
From: Kuo-Jung Su
The FTSPI020 is an integrated SPI Flash controller
which supports up to 4 flash chips.
Signed-off-by: Kuo-Jung Su
---
hw/arm/Makefile.objs |1 +
hw/arm/faraday_a369.c | 16 +++
hw/arm/ftspi020.c | 337 +
hw/arm/ftspi
From: Kuo-Jung Su
This patch includes the single core support to FA606TE, FA626TE,
FA616TE and FA726TE with CP15 Faraday extensions (AUX and I/D-Scratchpad).
Signed-off-by: Kuo-Jung Su
---
target-arm/cpu.c | 52 +++
target-arm/cpu.h |6 +++-
target-arm
From: Kuo-Jung Su
The FTDDRII030 is a DDRII SDRAM controller which is responsible for
SDRAM initialization.
In QEMU we emulate only the SDRAM enable function.
Signed-off-by: Kuo-Jung Su
---
hw/arm/Makefile.objs |1 +
hw/arm/faraday_a369_soc.c |9 +++
hw/arm/ftddrii030.c | 1
On 15 March 2013 13:15, Kuo-Jung Su wrote:
> default-configs/arm-softmmu.mak |1 +
> hw/Makefile.objs|2 +
> hw/arm/Makefile.objs| 21 ++
> hw/arm/faraday.h| 61
> hw/arm/faraday_a369.c | 174 ++
> hw/arm/faraday_a369
On 15/03/2013 13:44, Cornelia Huck wrote:
On Fri, 15 Mar 2013 10:19:50 +0100
KONRAD Frédéric wrote:
On 15/03/2013 10:16, fred.kon...@greensocs.com wrote:
From: KONRAD Frederic
This is the next part of virtio-refactoring.
Basically it creates virtio-blk device which extends virtio-device.
T
On Fri, Mar 15, 2013 at 12:04 AM, Peter Crosthwaite
wrote:
> These functions don't exist until glib version 2.26. QEMU is currently only
> mandating glib 2.12.
>
> This patch replaces the functions with g_key_file_get/set_integer.
>
> Unbreaks the build on Ubuntu 10.04 and RHEL 5.6.
>
> Regression
Make the SysBusDeviceClass::init optional, for devices which
genuinely don't need to do anything here. In particular, simple
devices which can do all their initialization in their
instance_init method don't need either a DeviceClass::realize
or SysBusDeviceClass::init method.
Signed-off-by: Peter
Don't map the pmem and dmem RAM memory regions in the milkymist-softusb
device itself. Instead just expose them as sysbus mmio regions which
the device creator can map appropriately. This allows us to drop the
pmem_base and dmem_base properties. Instead of going via
cpu_physical_memory_read/_write
The functions sysbus_add_memory and sysbus_del_memory are odd wrappers
around around memory_region_add/del_subregion, and their presence
is an encouragement to devices to try to map their own memory
regions into the system address space.
Since they're only used in a couple of places in the milkymi
Remove the sysbus_add_memory and sysbus_del_memory functions. These
are trivial wrappers for mapping a memory region into the system
memory space, and have no users now. Sysbus devices should never map
their own memory regions anyway; the correct API for mapping an mmio
region is for the creator o
1 - 100 of 258 matches
Mail list logo
