Although not strictly required to boot a 64MB board, bump
vm_max_virtual_address to be KERNVIRTADDR + 256MB. This allows some future shock protection since the KVA requirements have gone up since the unmapped changes have gone in, as well as preventing us from overlapping with the hardware devices, which we map at 0xd0000000, which we'd hit with anything more than 85MB... MFC after: 3 days
This commit is contained in:
parent
9f16518401
commit
0b40a04719
@ -633,7 +633,8 @@ initarm(struct arm_boot_params *abp)
|
||||
|
||||
pmap_curmaxkvaddr = afterkern + L1_S_SIZE * (KERNEL_PT_KERN_NUM - 1);
|
||||
arm_dump_avail_init(memsize, sizeof(dump_avail)/sizeof(dump_avail[0]));
|
||||
vm_max_kernel_address = KERNVIRTADDR + 3 * memsize;
|
||||
/* Always use the 256MB of KVA we have available between the kernel and devices */
|
||||
vm_max_kernel_address = KERNVIRTADDR + (256 << 20);
|
||||
pmap_bootstrap(freemempos, &kernel_l1pt);
|
||||
msgbufp = (void*)msgbufpv.pv_va;
|
||||
msgbufinit(msgbufp, msgbufsize);
|
||||
|
Loading…
Reference in New Issue
Block a user