?Hi Robbie,
Groups are not supported by released versions of CAmkES (such as 2.2). They are
however, supported on our development version of CAmkES in a branch called
"next". You can get the latest version of CAmkES next and its dependencies
using repo:
repo init -u
Hi Oak,
I don't suppose that any of those calls are returning errors?
DMA is optional for the SDHC. It has been a while since I looked at the
code, but I believe that passing 0 as the paddr will prevent the driver
from using DMA. Of course, this is not a solution to your problem, but
it could
So I use the following code to create a new buffer for vaddr and paddr :
void *vaddr = vspace_new_pages(, seL4_AllRights, 1, seL4PageBits);
seL4_CPtr frame_cap = vsapce_get_cap(, vaddr);
seL4_ARM_Page_GetAddress_t gaddr = seL4_ARCH_Page_GetAddress(frame_cap);
uintptr_t paddr = (uintptr_t)
Hi Jeff,
What you are experiencing is a long standing set of limitations of seL4:
* Limited (currently 512mb on ia32) kernel window
* Static kernel window (i.e. memory cannot be swapped in and out)
* Simple offset translation of kernel virtual addresses to physical addresses
The result of these
Hi all,
Using x86 master on qemu with 2G memory, the kernel's map looks good:
Parsing GRUB physical memory map
Physical Memory Region from 0 size 9fc00 type 1
Physical Memory Region from 9fc00 size 400 type 2
Physical Memory Region from f size 1 type 2
Physical Memory Region from 10
Hello,
I have been trying to get groups with CAmkES 2.2 working, but it doesn't look
like it will build correctly. At first, when I place components in a group, I
get that there is an unresolved reference to one of the components during
compilation.
I was able to get past this by moving the
Hi, all
I have a question about adding a device to ARM VM linux. When a device is
added to the vmlinux, two functions, map_device () and map_ram () are
invoked. I don't understand the purpose of map_ram().
In map_device(), the capacity to the device is used to set up the mapping
between a
