Commit d8011768 authored by Haavard Skinnemoen's avatar Haavard Skinnemoen

[AVR32] Simplify early handling of memory regions

Use struct resource to specify both physical memory regions and
reserved regions and push everything into the same framework,
including kernel code/data and initrd memory. This allows us to get
rid of many special cases in the bootmem initialization and will also
make it easier to implement more robust handling of framebuffer
memory later.
Signed-off-by: default avatarHaavard Skinnemoen <hskinnemoen@atmel.com>
parent 5539f59a
This diff is collapsed.
...@@ -124,19 +124,13 @@ struct tagtable { ...@@ -124,19 +124,13 @@ struct tagtable {
#define for_each_tag(t,base) \ #define for_each_tag(t,base) \
for (t = base; t->hdr.size; t = tag_next(t)) for (t = base; t->hdr.size; t = tag_next(t))
extern struct tag_mem_range *mem_phys;
extern struct tag_mem_range *mem_reserved;
extern struct tag_mem_range *mem_ramdisk;
extern struct tag *bootloader_tags; extern struct tag *bootloader_tags;
extern void setup_processor(void);
void setup_processor(void);
extern void board_setup_fbmem(unsigned long fbmem_start, extern void board_setup_fbmem(unsigned long fbmem_start,
unsigned long fbmem_size); unsigned long fbmem_size);
/* Chip-specific hook to enable the use of SDRAM */
void chip_enable_sdram(void);
#endif /* !__ASSEMBLY__ */ #endif /* !__ASSEMBLY__ */
#endif /* __KERNEL__ */ #endif /* __KERNEL__ */
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment