Public bug reported:
In a small hobby kernel for Raspberry Pi 2B, I am using the system timer
to control wait durations. This timer is located at 0x3f003000 and the
timer counts are located at 0x3f003004 (CLO) and 0x3f004008 (CHI).
Reading these memory locations returns 0 for both.
The basic cod
The command lines are:
[adam@os-dev ~]$ qemu-system-aarch64 -m 256 -M raspi2 -serial stdio
-kernel bin/rpi2b/kernel.elf
[adam@os-dev workspace]$ ./qemu/bin/debug/native/arm-softmmu/qemu-
system-arm -m 256 -M raspi2 -serial stdio -kernel
century/bin/rpi2b/kernel.elf
A sample kernel is also attac
Original conversation about this issue on osdev.org:
http://forum.osdev.org/viewtopic.php?f=1&t=25795
** Description changed:
Hi,
I have been getting a GPF when I enable interrupts, working on
implementing processes and a scheduler. When I comment out the scheduler
code, I still get th
Public bug reported:
Hi,
I have been getting a GPF when I enable interrupts, working on
implementing processes and a scheduler. When I comment out the scheduler
code, I still get the GPF. I used the following QEMU command line to
capture a log:
qemu-system-i386 -smp 4 -monitor stdio -cpu core2du
** Attachment added: "Test case for bug..."
https://bugs.launchpad.net/bugs/1050694/+attachment/3313662/+files/harddisk.img
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1050694
Title:
Interrup
