The delay slot exception flag is only set on the SR register during
exception. Previously it was being set on both the ESR and SR this
caused QEMU to differ from the spec. The was apparent as the linux
kernel had a bug where it could boot on QEMU but not on real hardware.
The fixed logic now mat
Le 28/06/2018 à 17:13, Peter Maydell a écrit :
On 26 June 2018 at 22:59, Jean-Christophe Dubois wrote:
Small fixes in the i.mx7d code.
Jean-Christophe Dubois (3):
i.mx7d: Remove unused header files
i.mx7d: Change SRC unimpleted device name from sdma to src
i.mx7d: Change IRQ number ty
Tested by booting linux 4.18 (built using imx_v6_v7_defconfig) on the
emulated board.
Signed-off-by: Jean-Christophe Dubois
---
hw/arm/Makefile.objs | 2 +-
hw/arm/mcimx6ul-evk.c | 86 +++
2 files changed, 87 insertions(+), 1 deletion(-)
create mode 100
Signed-off-by: Jean-Christophe Dubois
---
default-configs/arm-softmmu.mak | 1 +
hw/arm/Makefile.objs| 1 +
hw/arm/fsl-imx6ul.c | 649
include/hw/arm/fsl-imx6ul.h | 339 +
4 files changed, 990 insertions(+)
create m
This series adds the i.MX6UL SOC from NXP/Freescale and the reference
evaluation board.
This series as tested by booting linux 4.18 (built using imx_v6_v7_defconfig)
on the emulated board (with the appropriate device tree).
Jean-Christophe Dubois (3):
i.MX6UL: Add i.MX6UL specific CCM device
Signed-off-by: Jean-Christophe Dubois
---
hw/misc/Makefile.objs| 1 +
hw/misc/imx6ul_ccm.c | 887 +++
include/hw/misc/imx6ul_ccm.h | 228 +
3 files changed, 1116 insertions(+)
create mode 100644 hw/misc/imx6ul_ccm.c
create mode 100644 in
ble in the git repository at:
git://github.com/OSLL/qemu-xtensa.git tags/20180630-xtensa
for you to fetch changes up to 0f02251a30ea8c4ce64d9a240795e10bb3c5852c:
xtensa: Avoid calling get_page_addr_code() from helper function (2018-06-30
12:0
On Jun 30, 2018, at 11:43 AM, Richard Henderson wrote:
> On 06/29/2018 08:06 PM, John Arbuckle wrote:
>> When the fdiv instruction divides a finite number by zero,
>> the result actually depends on the FPSCR[ZE] bit. If this
>> bit is set, the return value is the value originally in
>> the desti
Oh hi!
Luckily gmail brought this to the top since I don’t pay attention to the
list. I’m away from my computer at the moment, but I had more than this
working, including interrupts, Ethernet, and SCSI for sure. (
https://i.imgur.com/Py0FO.png) I’d love to dive back into this now that
68040 suppor
On Tue, 26 Jun 2018, BALATON Zoltan wrote:
Version 2 of the sm501 changes with fixes that are needed to get
AmigaOS 4.1FE to boot and able to produce graphics.
The strange blue-white colors that first appear are actually correct
and because of AmigaOS selecting a low resolution PAL mode by defau
On Sat, Jun 30, 2018 at 1:10 PM, Peter Maydell wrote:
> On 30 June 2018 at 21:08, Peter Maydell wrote:
>> On 30 June 2018 at 20:42, Max Filippov wrote:
>>> On Sat, Jun 30, 2018 at 12:20 PM, Max Filippov wrote:
I'm observing the following failure with xtensa tests:
(qemu) qemu: fa
On 30 June 2018 at 21:08, Peter Maydell wrote:
> On 30 June 2018 at 20:42, Max Filippov wrote:
>> On Sat, Jun 30, 2018 at 12:20 PM, Max Filippov wrote:
>>> I'm observing the following failure with xtensa tests:
>>>
>>> (qemu) qemu: fatal: Unable to handle guest executing from RAM within a
>>> sm
Am Sat, 30 Jun 2018 12:07:01 -0500
schrieb Bryce Lanham :
> Oh hi!
>
> Luckily gmail brought this to the top since I don’t pay attention to
> the list. I’m away from my computer at the moment, but I had more
> than this working, including interrupts, Ethernet, and SCSI for sure.
> ( https://i.img
On 30 June 2018 at 20:42, Max Filippov wrote:
> On Sat, Jun 30, 2018 at 12:20 PM, Max Filippov wrote:
>> I'm observing the following failure with xtensa tests:
>>
>> (qemu) qemu: fatal: Unable to handle guest executing from RAM within a
>> small MPU region at 0xd804
>>
>> Bisection points to
On 30 June 2018 at 20:47, Thomas Huth wrote:
> Am Sat, 30 Jun 2018 17:12:01 +0100
> schrieb Peter Maydell :
>
>> On 30 June 2018 at 09:33, Thomas Huth wrote:
>> > The NeXTcube uses a linear framebuffer with 4 greyscale colors and
>> > a fixed resolution of 1120 * 832.
>> > This code has been take
On Sat, Jun 30, 2018 at 12:42 PM, Max Filippov wrote:
> On Sat, Jun 30, 2018 at 12:20 PM, Max Filippov wrote:
>> Hi Peter,
>>
>> On Wed, Jun 20, 2018 at 6:06 AM, Peter Maydell
>> wrote:
>>> Add support for MMU protection regions that are smaller than
>>> TARGET_PAGE_SIZE. We do this by marking
Am Sat, 30 Jun 2018 17:12:01 +0100
schrieb Peter Maydell :
> On 30 June 2018 at 09:33, Thomas Huth wrote:
> > The NeXTcube uses a linear framebuffer with 4 greyscale colors and
> > a fixed resolution of 1120 * 832.
> > This code has been taken from Bryce Lanham's GSoC 2011 NeXT branch
> > at
> >
On Sat, Jun 30, 2018 at 12:20 PM, Max Filippov wrote:
> Hi Peter,
>
> On Wed, Jun 20, 2018 at 6:06 AM, Peter Maydell
> wrote:
>> Add support for MMU protection regions that are smaller than
>> TARGET_PAGE_SIZE. We do this by marking the TLB entry for those
>> pages with a flag TLB_RECHECK. This
Hi Peter,
On Wed, Jun 20, 2018 at 6:06 AM, Peter Maydell wrote:
> Add support for MMU protection regions that are smaller than
> TARGET_PAGE_SIZE. We do this by marking the TLB entry for those
> pages with a flag TLB_RECHECK. This flag causes us to always
> take the slow-path for accesses. In the
On Fri, Jun 22, 2018 at 6:58 AM, Peter Maydell wrote:
> The xtensa frontend calls get_page_addr_code() from its
> itlb_hit_test helper function. This function is really part
> of the TCG core's internals, and calling it from a target
> helper makes it awkward to make changes to that core code.
> I
On Sat, Jun 30, 2018 at 10:32 AM, Richard Henderson
wrote:
> On 06/22/2018 06:58 AM, Peter Maydell wrote:
>> The xtensa frontend calls get_page_addr_code() from its
>> itlb_hit_test helper function. This function is really part
>> of the TCG core's internals, and calling it from a target
>> helper
On 30 June 2018 at 17:27, Markus Armbruster wrote:
> The following changes since commit 6f4fa0998fd13bd8a533f38ee69774ecad6911b6:
>
> Merge remote-tracking branch 'remotes/stefanha/tags/tracing-pull-request'
> into staging (2018-06-30 13:59:53 +0100)
>
> are available in the Git repository at:
On 06/22/2018 06:58 AM, Peter Maydell wrote:
> The xtensa frontend calls get_page_addr_code() from its
> itlb_hit_test helper function. This function is really part
> of the TCG core's internals, and calling it from a target
> helper makes it awkward to make changes to that core code.
> It also mea
On 06/30/2018 01:54 PM, Michael Tokarev wrote:
> Opengl support brings up libdrm. But actually nothing uses this library
> or includes any of its headers. Just remove checking for it from configure.
libgbm is linked to libdrm, but I don't see call from QEMU to libdrm,
son we don't need to check fo
Can this patch go via the Trivial tree?
On 06/22/2018 09:31 AM, Gerd Hoffmann wrote:
>>> Indention looks weird.
>>
>> Actually this is the code around that is weirdly intended, a mix of
>> and .
>
> Ok.
>
>> Do you prefer a previous indent cleanup patch or can I add your Acked-by
>> tag?
>
> L
Opengl support brings up libdrm. But actually nothing uses this library
or includes any of its headers. Just remove checking for it from configure.
Signed-off-by: Michael Tokarev
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index 65548df
Signed-off-by: Philippe Mathieu-Daudé
---
This was in e9dd993d-875f-4173-f68e-e6b4e75e3...@amsat.org but I can't
find it on the list...
tests/test-cutils.c| 2 +-
tests/test-qemu-opts.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/test-cutils.c b/tests/test-cu
From: Peter Xu
Previously we clean up the queues when we got CLOSED event. It was used
to make sure we won't send leftover replies/events of a old client to a
new client which makes perfect sense. However this will also drop the
replies/events even if the output port of the previous chardev back
From: Peter Xu
Out-Of-Band handlers need to protect shared state if there is any.
Mention it in the document. Meanwhile, touch up some other places too,
either with better English, or reordering of bullets.
Suggested-by: Markus Armbruster
Reviewed-by: Markus Armbruster
Signed-off-by: Peter Xu
From: Peter Xu
In my Out-Of-Band test, "check -qcow2 060" fail with this:
--- /home/peterx/git/qemu/tests/qemu-iotests/060.out
+++ /home/peterx/git/qemu/bin/tests/qemu-iotests/060.out.bad
@@ -427,8 +427,8 @@
QMP_VERSION
{"return": {}}
qcow2: Image is corrupt: L2 table offset 0x2a2a2a
On 29 June 2018 at 18:43, Dr. David Alan Gilbert (git)
wrote:
> From: "Dr. David Alan Gilbert"
>
> PPC tcg seems to be failing migration tests quite regularly;
> we believe this is TCG bugs in dirty bit updating; it's
> not clear why PPC fails more but lets skip for the moment.
>
> $ ./tests/migr
From: Peter Xu
It was unclear before on what does the CLOSED event mean. Meanwhile we
add a TODO to fix up the CLOSED event in the future when the in/out
ports are different for a chardev.
CC: Paolo Bonzini
CC: "Marc-André Lureau"
CC: Stefan Hajnoczi
CC: Markus Armbruster
Reviewed-by: Stefa
From: Peter Xu
The old names are confusing since both of the old functions are popping
an item from multiple queues rather than a single queue. In that
sense, *_pop_any() suites better than *_pop_one().
Since at it, touch up the function monitor_qmp_response_pop_any() a bit
to let the callers p
The following changes since commit 6f4fa0998fd13bd8a533f38ee69774ecad6911b6:
Merge remote-tracking branch 'remotes/stefanha/tags/tracing-pull-request'
into staging (2018-06-30 13:59:53 +0100)
are available in the Git repository at:
git://repo.or.cz/qemu/armbru.git tags/pull-monitor-2018-06-
I'm going to merge the fixes and cleanups [PATCH 1-5]. We need a few
more fixes before we can enable OOB [PATCH 6-7]. I'm working on some.
On 30 June 2018 at 09:33, Thomas Huth wrote:
> It is likely still quite incomplete (e.g. mouse and interrupts are not
> implemented yet), but it is good enough for keyboard input at the firmware
> monitor.
> This code has been taken from Bryce Lanham's GSoC 2011 NeXT branch at
>
> https://github.
On 30 June 2018 at 09:33, Thomas Huth wrote:
> The NeXTcube uses a linear framebuffer with 4 greyscale colors and
> a fixed resolution of 1120 * 832.
> This code has been taken from Bryce Lanham's GSoC 2011 NeXT branch at
>
> https://github.com/blanham/qemu-NeXT/blob/next-cube/hw/next-fb.c
>
> an
On 06/30/2018 01:33 AM, Thomas Huth wrote:
> +uint32_t pal[4] = { 0x, 0xFFAA, 0xFF55, 0xFF00 };
static const.
Otherwise,
Reviewed-by: Richard Henderson
r~
Hmm, must have sent a stale branch.
Thanks,
Paolo
Il sab 30 giu 2018, 17:40 Peter Maydell ha
scritto:
> On 30 June 2018 at 07:09, Paolo Bonzini wrote:
> > The following changes since commit
> 109b25045b3651f9c5d02c3766c0b3ff63e6d193:
> >
> > Merge remote-tracking branch 'remotes/bonzini/tag
On 06/29/2018 08:06 PM, John Arbuckle wrote:
> When the fdiv instruction divides a finite number by zero,
> the result actually depends on the FPSCR[ZE] bit. If this
> bit is set, the return value is the value originally in
> the destination register. If it is not set
> the result should be either
On 30 June 2018 at 07:09, Paolo Bonzini wrote:
> The following changes since commit 109b25045b3651f9c5d02c3766c0b3ff63e6d193:
>
> Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into
> staging (2018-06-29 12:30:29 +0100)
>
> are available in the git repository at:
>
>
> git:/
On 29 June 2018 at 18:53, Stefan Hajnoczi wrote:
> The following changes since commit 609ef9f451759151d0bfe7c3843410ab94d68f18:
>
> Merge remote-tracking branch 'remotes/berrange/tags/qio-next-pull-request'
> into staging (2018-06-28 17:53:31 +0100)
>
> are available in the Git repository at:
>
Am Sat, 30 Jun 2018 14:17:32 +0100
schrieb Peter Maydell :
> On 30 June 2018 at 14:14, Thomas Huth wrote:
> > Weird... the mail was ca. 1200 lines ... that not small, but not so
> > big that I'd expect that it would get blocked somewhere. Let's wait
> > some more more hours, maybe the spam filter
On 30 June 2018 at 14:14, Thomas Huth wrote:
> Weird... the mail was ca. 1200 lines ... that not small, but not so
> big that I'd expect that it would get blocked somewhere. Let's wait
> some more more hours, maybe the spam filter is just very slow today. If
> it is then still not available on the
Am Sat, 30 Jun 2018 10:42:56 +0100
schrieb Mark Cave-Ayland :
> On 30/06/18 09:33, Thomas Huth wrote:
>
> > During Google Summer of Code 2011, Bryce Lanham added the
> > possibility to emulate the NeXTcube machine in QEMU, e.g. see this
> > URL for some details:
> >
> > https://wiki.qemu.org/Goo
On 1 June 2018 at 18:15, Paolo Bonzini wrote:
> This is only half of the work, because the proxy devices (virtio-*-pci,
> virtio-*-ccw, etc.) are still included unconditionally. It is still a
> move in the right direction.
>
> Based-on: <20180522194943.24871-1-pbonz...@redhat.com>
> Signed-off-by
On 29 June 2018 at 18:22, Alistair Francis wrote:
> The following changes since commit 75507f1aba6feb73ae43329922d51571550b9128:
>
> Merge remote-tracking branch 'remotes/berrange/tags/min-glib-pull-request'
> into staging (2018-06-29 15:04:20 +0100)
>
> are available in the Git repository at:
On 29 June 2018 at 15:52, Peter Maydell wrote:
> Hopefully last target-arm queue before softfreeze;
> this one's largest part is the remainder of the SVE patches,
> but there are a selection of other minor things too.
>
> thanks
> -- PMM
>
> The following changes since commit 109b25045b3651f9c5d02
On Sat, 30 Jun 2018, David Gibson wrote:
On Fri, Jun 29, 2018 at 08:06:10PM +0200, Sebastian Bauer wrote:
Hi,
Am 2018-06-19 06:36, schrieb David Gibson:
Ok. However, your patch doesn't apply against the ppc-for-3.0 tree.
It looks like you've made it against a tree including some of BALATON
Zo
On 29 June 2018 at 15:09, Kevin Wolf wrote:
> The following changes since commit 609ef9f451759151d0bfe7c3843410ab94d68f18:
>
> Merge remote-tracking branch 'remotes/berrange/tags/qio-next-pull-request'
> into staging (2018-06-28 17:53:31 +0100)
>
> are available in the git repository at:
>
>
Public bug reported:
When using the -net
user,id=net0,ipv6=off,smb=/path/to/share/option,hostfwd=tcp::19500-:22 I can
successfully mount_smbfs the shared directory on the guest when QEMU is running
on a Linux or FreeBSD host. However, on a MacOS host the mount_smbfs command
just fails with
`mo
On 30/06/18 09:33, Thomas Huth wrote:
During Google Summer of Code 2011, Bryce Lanham added the possibility to
emulate the NeXTcube machine in QEMU, e.g. see this URL for some details:
https://wiki.qemu.org/Google_Summer_of_Code_2011#NeXT_machines_system_emulation
But since the machine require
Define a "cortex-m0" ARMv6-M CPU model.
Most of the register reset values set by other CPU models are not
relevant for the cut-down ARMv6-M architecture.
Signed-off-by: Stefan Hajnoczi
---
target/arm/cpu.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/target/arm/cpu.c b/targe
The ARMv7-M code is largely similar to what other M Profile CPUs need.
Extract the common M Profile aspects into the ARMMProfileState base
class. ARMv6-M will inherit from this class in the following patch.
It might be possible to make ARMv6-M the base class of ARMv7-M, but it
seems cleaner to ha
v2:
* Share code between ARMv6-M and ARMv7-M [Peter]
This patch series adds a skeleton ARM Cortex M0 CPU model and an ARMv6M object
so that machine types can make use of it.
These patches cannot be merged until Julia Suvorova's Cortex M0 work is
complete, since the target/arm/ code does not impl
The ARMv6M object will be used by machine types that need ARMv6-M CPUs.
There is no logic beyond what the ARMMProfile base class already
provides because ARMv6-M is a pretty small microcontroller without many
bells and whistles.
Signed-off-by: Stefan Hajnoczi
---
hw/arm/Makefile.objs
I don't have much clue about the NeXT hardware, but at least I know now
the source files a little bit, so I volunteer to pick up patches and send
PULL requests for them until someone else with more knowledge steps up
to do this job instead.
Signed-off-by: Thomas Huth
---
MAINTAINERS | 7 +++
During Google Summer of Code 2011, Bryce Lanham added the possibility to
emulate the NeXTcube machine in QEMU, e.g. see this URL for some details:
https://wiki.qemu.org/Google_Summer_of_Code_2011#NeXT_machines_system_emulation
But since the machine requires a 68040 CPU and this was not included i
It is likely still quite incomplete (e.g. mouse and interrupts are not
implemented yet), but it is good enough for keyboard input at the firmware
monitor.
This code has been taken from Bryce Lanham's GSoC 2011 NeXT branch at
https://github.com/blanham/qemu-NeXT/blob/next-cube/hw/next-kbd.c
and a
The NeXTcube uses a linear framebuffer with 4 greyscale colors and
a fixed resolution of 1120 * 832.
This code has been taken from Bryce Lanham's GSoC 2011 NeXT branch at
https://github.com/blanham/qemu-NeXT/blob/next-cube/hw/next-fb.c
and altered to fit the latest interface of the current QEMU
60 matches
Mail list logo
