| commit | f9692b9501c339ec90647d8cd6ee5c106f072f9f | |
| author | Haavard Skinnemoen <hskinnemoen@atmel.com> | |
| Wed, 21 Mar 2007 15:16:50 +0000 (21 16:16 +0100) | ||
| committer | Haavard Skinnemoen <hskinnemoen@atmel.com> | |
| Fri, 27 Apr 2007 11:44:14 +0000 (27 13:44 +0200) | ||
| tree | 3a11d55a0383d10cb712b31bc18e57585cdeed4c | treesnapshot (tar.gz zip) |
| parent | d8011768e6bdd0d9de5cc7bdbd3077b4b4fab8c7 | commitdiff |
[AVR32] Reserve framebuffer memory in early_parse_fbmem()
With the current strategy of using the bootmem allocator to allocate
or reserve framebuffer memory, there's a slight chance that the
requested area has been taken by the boot allocator bitmap before we
get around to reserving it.
By inserting the framebuffer region as a reserved region as early as
possible, we improve our chances for success and we make the region
visible as a reserved region in dmesg and /proc/iomem without any
extra work.
Signed-off-by: Haavard Skinnemoen <hskinnemoen@atmel.com>
With the current strategy of using the bootmem allocator to allocate
or reserve framebuffer memory, there's a slight chance that the
requested area has been taken by the boot allocator bitmap before we
get around to reserving it.
By inserting the framebuffer region as a reserved region as early as
possible, we improve our chances for success and we make the region
visible as a reserved region in dmesg and /proc/iomem without any
extra work.
Signed-off-by: Haavard Skinnemoen <hskinnemoen@atmel.com>
| arch/avr32/kernel/setup.c | diffblobblamehistory |