The pca954x is an i2c mux, and this adds support for two variants of
this device: the pca9546 and pca9548.
This device is very common on BMCs to route a different channel to each
PCIe i2c bus downstream from the BMC.
Signed-off-by: Patrick Venture
Reviewed-by: Havard Skinnemoen
Reviewed-by: Hao
An i2c device can be reachable or not, controlled by some external
factor. This field is leveraged by an i2c mux which presents the
devices on the parent bus when the associated channel is enabled and
otherwise not.
Signed-off-by: Patrick Venture
Reviewed-by: Havard Skinnemoen
Reviewed-by: Hao
The i2c mux device pca954x implements two devices:
- the pca9546 and pca9548.
Patrick Venture (2):
hw/i2c/core: add reachable state boolean
hw/i2c: add pca954x i2c-mux switch
MAINTAINERS | 6 +
hw/i2c/Kconfig | 4 +
hw/i2c/core.c
On 4/2/21 2:42 PM, Richard Henderson wrote:
Changes for v3:
* linux-user mprotect fix moved to start, just to get it out
of the way while I reworked the others.
* Patch 2, the fix for unaligned accesses, has been split into 9.
Hopefully these are much easier to review than previo
That is awesome David,
qemu64 is like a very low common denominator with only very basic CPU features.
While "copy host" means "enable all you can".
We can surely work with that a bit, but until I get access to the same
HW I need you to do it.
If you run in a console `$virsh domcapabilities` it
Alex,
You are the one maintaining the testing/next tree at
https://gitlab.com/stsquad/qemu correct? The current patch series for hexagon
under review requires toolchain updates. These changes to llvm/clang landed in
the last week or two.
Can you apply this patch?
>From 68547357c895934
tags/20210403-xtensa
for you to fetch changes up to 30c676134eb8f956853a55023d694062062d40d7:
target/xtensa: make xtensa_modules static on import (2021-04-03 08:52:18
-0700)
target/xtensa fixes for v6.0:
- make meson.build pick
On 4/2/21 9:03 PM, Max Filippov wrote:
import_core.sh tries to change Makefile.objs when importing new xtensa
core, but that file no longer exists. Rewrite meson.build rule to pick
up all source files that match core-*.c pattern and drop commands that
change Makefile.objs.
Cc:qemu-sta...@nongnu.
With v2, a lot of KASAN tests start failing. This likely means that MTE
tag faults stop being generated in certain cases.
With v3 [1], no MTE faults are generated at all.
[1]
https://patchew.org/QEMU/20210402214217.422585-1-richard.hender...@linaro.org/
--
You received this bug notification bec
On 02/04/2021 17:20, Alexander Bulekov wrote:
Original crash:
qemu-fuzz-i386: ../hw/scsi/esp.c:791: void esp_transfer_data(SCSIRequest *,
uint32_t): Assertion `!s->do_cmd' failed.
==257532== ERROR: libFuzzer: deadly signal
__assert_fail assert/assert.c:101:3
esp_transfer_data hw/scsi/esp.c:791:
Public bug reported:
openSuse 15.2
kde plasma 5.21.3, frameworks 5.80.0
libvirt 7.0.0
qemu 5.2.0
virgl renderer 0.8.2
here is my invocation
qemu-kvm -enable-kvm \
-m 2048 -smp 2 -cpu host \
-device virtio-vga,virgl=on -display gtk,gl=on \
-device usb-ehci \
-device usb-kbd \
-device usb-mouse \
11 matches
Mail list logo