Hi list,
I'm doing some LAPIC programing.
According to Intel's document, FEE0 H to FEE0 03F0H is the range of
local APIC. However, examining it from QEMU console, I can only find the
value 0 there:
(qemu) x/128b 0xfee0
fee0: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Some versions of the gcc startup code initializes floating point
processor/feature even if the program doesn't use it.
Historically, this created a problem because the Linux kernel (on 32
bit x86) could context switch faster if it knew a process never touched
the floating point state, but gcc
Well, ok playing with the cpio options seems to have done the trick:
zcat ../arm_test.img | cpio -idmv
find . | cpio -ov -R root --format=newc | gzip > ../test.img
I can boot the new image now, and run my test app - of course it didn't work,
its giving me "Floating point exception", lol.
Well, I was able to unpack the arm_test.img and add my file, but after
repacking and using as a boot image I get a Kernel panic - not syncing: VFS:
Unable to mount root fs unknown-block(0,0)
Pretty sure there must be some different options in use than whats given at the
link
On 3 November 2016 at 22:48, Brooke Wallace wrote:
> Thanks again Peter,
>
> Is there anyway to mount an -initrd image to the host?
You can't directly mount it, because it's not a filesystem.
But there are tools for manipulating initrd images:
something like
Thanks again Peter,
Is there anyway to mount an -initrd image to the host? Can I unzip it or
something? I'd just like to run my cross-compiled app and say that it worked.
Then maybe I can start poking around in the code and see where I can start
adding some hooks.
Send me a pointer to the
On 3 November 2016 at 19:42, Peter Maydell wrote:
> On 3 November 2016 at 18:56, Brooke Wallace wrote:
>> Thanks for the sympathy Peter. Unfortunately the lack of documentation
>> and reasonable introductory guide is making this a non-starter for
For network conectivity testing, you can try with "nc" to another
TCP/UDP port.
El 03/11/16 a les 19:56, Brooke Wallace ha escrit:
> Thanks for the sympathy Peter. Unfortunately the lack of documentation and
> reasonable introductory guide is making this a non-starter for us.
>
> 1. The
On 3 November 2016 at 18:56, Brooke Wallace wrote:
> Thanks for the sympathy Peter. Unfortunately the lack of documentation
> and reasonable introductory guide is making this a non-starter for us.
Yeah, I was surprised there wasn't a decent guide to getting
the 'virt' board
Thanks for the sympathy Peter. Unfortunately the lack of documentation and
reasonable introductory guide is making this a non-starter for us.
1. The integratorcp test image does not have scp
the only command I can find for file transfer is tftp, but it looks like no
one uses this anymore
On 2 November 2016 at 20:03, Brooke Wallace wrote:
> I'm new to QEMU and was able to pull the latest stable version and build it.
> I downloaded a simple test arm image that I found in one of the docs -
> arm-test-0.2.tar.gz and was able to run that w/o any problems.
If your disk image is RAW, try to attach it with ploop before
partitioning, formatting or mounting volumes from it.
After these preparations on the image, release any attachment or mount
from the file before running Qemu using the image file.
Using Qemu filesharing features, I only use SMB to
12 matches
Mail list logo