u-boot.git/arch/x86/include/asm, branch v2012.07

net: move bootfile init into eth_initialize

2012-05-15T22:32:33Z

All arches init this the same way, so move the logic into the core net code to avoid duplicating it everywhere else. Signed-off-by: Mike Frysinger Reviewed-by: Joe Hershberger

net: punt bd->bi_ip_addr

2012-05-15T22:32:05Z

This field gets read in one place (by "bdinfo"), and we can replace that with getenv("ipaddr"). After all, the bi_ip_addr field is kept up-to-date implicitly with the value of the ipaddr env var. Signed-off-by: Mike Frysinger Reviewed-by: Joe Hershberger

x86: Convert board_init_f_r to a processing loop

2012-01-04T11:53:14Z

Create an init function array for board_init_f_r - This finalises the migration to a purely array based initialisation mechanism Also tweak a few comments while we are at it so everything is 'correct' -- Changes for v2: - Renamed to a more apt name - Fix bug in set_reloc_flag_r - Re-instate gd->flags = boot_flags; in board_init_f - Added commit message

x86: Split init functions out of board.c

2012-01-04T11:41:32Z

This patch moves towards reducing board.c to simply a set of init cores for the three initialisation phases (Flash, Flash/RAM, and RAM), a set of three init function arrays and a init function array processing function

x86: Create weak init_cache() and default enable_caches() functions

2012-01-04T11:19:01Z

-- Changes for v2: - Tweaked commit title

x86: Use fs for global data

2012-01-04T11:17:24Z

Use the base address of the 'F' segment as a pointer to the global data structure. By adding the linear address (i.e. the 'D' segment address) as the first word of the global data structure, the address of the global data relative to the 'D' segment can be found simply, for example, by: fs movl 0, %eax This makes the gd 'pointer' writable prior to relocation (by reloading the Global Desctriptor Table) which brings x86 into line with all other arches NOTE: Writing to the gd 'pointer' is expensive (but we only do it twice) but using it to access global data members (read and write) is still fairly cheap -- Changes for v2: - Rebased against changes made to patch #3 - Removed extra indent - Tweaked commit message

x86: Simplify Flash-to-RAM code execution transition

2012-01-04T11:17:20Z

Move the relocation offset calculation out of assembler and into C. This also paves the way for the upcoming init sequence simplification by adding the board_init_f_r flash to RAM transitional function -- Changes for v2: - Added commit message - Minor adjustment to new stack address comment

x86: Remove GDR related magic numbers

2012-01-04T10:05:09Z

-- Changes for v2: - Use an enum - Add defined for GDT size (previously added in patch 7) - Use X86_ namespace (as per Linux headers)

x86: Import glibc memcpy implementation

2012-01-01T16:58:46Z

Taken from glibc version 2.14.90 -- Changes for v2: - None

x86: Refactor the zboot innards so they can be reused with a vboot image

2011-12-19T02:26:16Z

If vboot successfully verifies a kernel, it will leave it in place and basically ready to boot. The zeropage table which is part of the x86 boot protocol is at the end of the kernel, though, instead of the beginning, and because the image is already in place there's no need to copy it around. This change refactors the code which implements the zboot command so that the configuration of the zeropage table and loading the pieces of the kernel into memory are done separately. Also, because the command line goes before the zeropage table in vboot which is somewhat incompatible with the normal protocol, where to put the command line is a now a parameter instead of being hard coded. Signed-off-by: Gabe Black