linux-toradex.git/arch/avr32/kernel/setup.c, branch v2.6.32.31

avr32: added mem kernel command line option support

2008-09-22T07:51:01+00:00

Signed-off-by: Marco Stornelli 
Signed-off-by: Haavard Skinnemoen

avr32: Use instead of

2008-08-05T12:36:57+00:00

Update all avr32-specific files to use the new platform-specific header
locations. Drivers shared with ARM are left alone for now.

Signed-off-by: Haavard Skinnemoen

atmel_lcdfb: don't initialize a pre-allocated framebuffer

2008-04-28T15:58:38+00:00

If the user specified a fixed framebuffer address on the command line, it may
have been initialized already with a splash image or something, so we
shouldn't clear it.

Therefore, we should only initialize the framebuffer if we allocated it
ourselves.  This patch also updates the AVR32 setup code to clear the
framebuffer if it allocated it itself, i.e.  the user didn't provide a fixed
address or the reservation failed.

I've updated the at91 platform code as well so that it initializes the
framebuffer if it is located in SRAM, but I haven't tested that it actually
works.

Signed-off-by: Haavard Skinnemoen 
Cc: "Antonino A. Daplas" 
Cc: Nicolas FERRE 
Cc: Andrew Victor 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

avr32: Fix bug in early resource allocation code

2008-03-27T14:31:57+00:00

add_reserved_region() tries to keep the resource list sorted, so when
looking for a place to insert the new resource, it may break out
before the last entry.

When this happens, the list is broken in two because the sibling field
of the new entry doesn't point to the next resource. Fix it by
updating the new resource's sibling field appropriately.

Signed-off-by: Haavard Skinnemoen

Introduce flags for reserve_bootmem()

2008-02-07T16:42:25+00:00

This patchset adds a flags variable to reserve_bootmem() and uses the
BOOTMEM_EXCLUSIVE flag in crashkernel reservation code to detect collisions
between crashkernel area and already used memory.

This patch:

Change the reserve_bootmem() function to accept a new flag BOOTMEM_EXCLUSIVE.
If that flag is set, the function returns with -EBUSY if the memory already
has been reserved in the past.  This is to avoid conflicts.

Because that code runs before SMP initialisation, there's no race condition
inside reserve_bootmem_core().

[akpm@linux-foundation.org: coding-style fixes]
[akpm@linux-foundation.org: fix powerpc build]
Signed-off-by: Bernhard Walle 
Cc: 
Cc: "Eric W. Biederman" 
Cc: Vivek Goyal 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[AVR32] fix command line parsing in early_parse_fbmem

2007-10-11T10:16:56+00:00

Signed-off-by: Matteo Vit - Dave S.r.l. 
Signed-off-by: Haavard Skinnemoen

[AVR32] Correct misspelled CONFIG_BLK_DEV_INITRD variable.

2007-07-18T18:47:04+00:00

Signed-off-by: Robert P. J. Day 
Signed-off-by: Haavard Skinnemoen

[AVR32] Fix build error in parse_tag_rdimg()

2007-07-18T18:47:04+00:00

This code is inside an #ifdef with a misspelled config symbol, so it
hasn't been used for a long time. Fix it before fixing the config
symbol to keep bisection working.

Signed-off-by: Haavard Skinnemoen

[AVR32] Get rid of board_setup_fbmem()

2007-04-27T11:44:15+00:00

Since the core setup code takes care of both allocation and
reservation of framebuffer memory, there's no need for this board-
specific hook anymore. Replace it with two global variables,
fbmem_start and fbmem_size, which can be used directly.

Signed-off-by: Haavard Skinnemoen

[AVR32] Reserve framebuffer memory in early_parse_fbmem()

2007-04-27T11:44:14+00:00

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