in the source code "hw/net/e1000.c"
[LEDCTL] = 0x602,
maybe should be:
[LEDCTL] = 0x07068302,
according to the "*Table 13-60. LED Control Bit Description*" of the doc:
https://www.intel.com/content/dam/doc/manual/pci-pci-x-family-gbe-controllers-software-dev-manual.pdf
0x602 is EEPROM default
According to the commit below, configure qemu like this:
$ ./configure --enable-debug --enable-slirp
and even before configure, i did:
$ meson subprojects download
but qemu still builded with native libslirp,
then how can I build with slirp.wrap? even when libslirp is installed on
the system.
*c
in qemu branch statble-9.2
> $ ./build/qemu-system-arm -M microbit -device
> loader,file=/path/to/heart-hearts-makecode.hex
>
Segmentation fault
about the error, gdb backtrace like this:
> bash-5.1$ gdb ./build/qemu-system-arm
> GNU gdb (GDB) 11.2
> Copyright (C) 2022 Free Software Foundation,
bash-5.1$ git diff net/net.c
diff --git a/net/net.c b/net/net.c
index c1bb19a523..af68029428 100644
--- a/net/net.c
+++ b/net/net.c
@@ -173,6 +173,7 @@ static void qemu_macaddr_set_used(MACAddr *macaddr)
for (index = 0x56; index < 0xFF; index++) {
if (macaddr->a[5] == index) {
Does efi-e1000.rom come from 8086100e.mrom?
If yes, how to convert it? Thanks
*8086100e.mrom*: ipxe/src/bin/8086100e.mrom
>
*efi-e1000.rom*: qemu/pc-bios/efi-e1000.rom
I want to build qemu with libslirp which built from source code but not
from the system.
Maybe the "subprojects/slirp.wrap" is the right way, is it? But I can't
find more information about how to use it on the internet. Is there some
notes about that? Thanks.
on qemu-manpage (https://www.qemu.org/docs/master/system/qemu-manpage.html)
-netdev user,id=id[,option][,option][,...]
...
id=id
Assign symbolic name for use in monitor commands.
on qemu-wikipage (https://wiki.qemu.org/Documentation/Networking)
-netdev TYPE,id=NAME,...
The id option gives the
How to compile QEMU with glib source code? But not with the glib library
I want to debug QEMU by stepping into glib internally.
Thanks.
Thanks, I'll check it out.
it does be a very old version, almost the first version of QEMU
$ git checkout initial -b initial
I will try it on my own, thanks a lot.
On Thu, Dec 7, 2023 at 7:32 PM Peter Maydell
wrote:
> On Thu, 7 Dec 2023 at 11:20, Liu Jaloo wrote:
> >
> &g
qemu checkout tag "initial" version, then
$ make
report error, like this:
make: *** No rule to make target 'i386/fp87.c', needed by 'i386/fp87.o'.
Stop.
How or where can I get the resource about folder "i386", just like OBJS in
Makefile
OBJS= i386/fp87.o i386/interp_main.o i386/interp_modrm.o
i3
Thanks a lot.
On Thu, Aug 31, 2023 at 2:11 PM Philippe Mathieu-Daudé
wrote:
> Hi,
>
> On 31/8/23 05:15, Liu Jaloo wrote:
> > Where actually defined the "PC_MACHINE_CLASS", I can't find it in source
> > code, please help to point out the file.
>
Where actually defined the "PC_MACHINE_CLASS", I can't find it in source
code, please help to point out the file.
Thanks.
Thanks for your reply.
On Thu, Aug 24, 2023 at 5:33 PM Peter Maydell
wrote:
> On Thu, 24 Aug 2023 at 06:55, Markus Armbruster wrote:
> >
> > Liu Jaloo writes:
> >
> > > What's the difference between "__attribute__((constructor))" and
> >
What's the difference between "__attribute__((constructor))" and
"__attribute__((__constructor__))" in qemu source?
Thanks!
maybe QOP stands for QEMU OPs? that's maybe.
On Fri, Jun 10, 2022 at 6:31 PM Paolo Bonzini wrote:
> On 6/10/22 04:01, Liu Jaloo wrote:
> > Dear Paul Brook:
> > in qemu/tcg/README:
> > "
> > ...
> > QOP code generator written by Paul Brook.
>
Dear Paul Brook:
in qemu/tcg/README:
"
...
QOP code generator written by Paul Brook.
...
"
Is there some text about QOP? or basically what QOP stands for?
I can't find out anything about QOP from Google. thanks.
from hw/arm/boot.c
static const ARMInsnFixup bootloader[] = {
{ 0xe28fe004 }, /* add lr, pc, #4 */
...
}
$ rasm2 -a arm -d -e 0xe28fe004
add lr, pc, 4
$ rasm2 --help
-e Use big endian instead of little endian
why arm bootloader defalut is big endian?
17 matches
Mail list logo
