Skip to content

U
U-Boot.Mirror

OS / U-Boot.Mirror

通知 1
Star 0
Fork 0
U
U-Boot.Mirror

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 02 4月, 2009 8 次提交
    • D
      libfdt: Rework/cleanup fdt_next_tag() · a22d9cfb
      由 David Gibson 提交于 
      Currently, callers of fdt_next_tag() must usually follow the call with
some sort of call to fdt_offset_ptr() to verify that the blob isn't
truncated in the middle of the tag data they're going to process.
This is a bit silly, since fdt_next_tag() generally has to call
fdt_offset_ptr() on at least some of the data following the tag for
its own operation.

This patch alters fdt_next_tag() to always use fdt_offset_ptr() to
verify the data between its starting offset and the offset it returns
in nextoffset.  This simplifies fdt_get_property() which no longer has
to verify itself that the property data is all present.

At the same time, I neaten and clarify the error handling for
fdt_next_tag().  Previously, fdt_next_tag() could return -1 instead of
a tag value in some circumstances - which almost none of the callers
checked for.  Also, fdt_next_tag() could return FDT_END either because
it encountered an FDT_END tag, or because it reached the end of the
structure block - no way was provided to tell between these cases.

With this patch, fdt_next_tag() always returns FDT_END with a negative
value in nextoffset for an error.  This means the several places which
loop looking for FDT_END will still work correctly - they only need to
check for errors at the end.  The errors which fdt_next_tag() can
report are:
	- -FDT_ERR_TRUNCATED if it reached the end of the structure
	   block instead of finding a tag.

	- -FDT_BADSTRUCTURE if a bad tag was encountered, or if the
           tag data couldn't be verified with fdt_offset_ptr().

This patch also updates the callers of fdt_next_tag(), where
appropriate, to make use of the new error reporting.

Finally, the prototype for the long gone _fdt_next_tag() is removed
from libfdt_internal.h.
Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      a22d9cfb
    • D
      libfdt: Rework fdt_next_node() · 2c0b843e
      由 David Gibson 提交于 
      Currently fdt_next_node() will find the next node in the blob
regardless of whether it is above, below or at the same level in the
tree as the starting node - the depth parameter is updated to indicate
which is the case.  When a depth parameter is supplied, this patch
makes it instead terminate immediately when it finds the END_NODE tag
for a node at depth 0.  In this case it returns the offset immediately
past the END_NODE tag.

This has a couple of advantages.  First, this slightly simplifies
fdt_subnode_offset(), which no longer needs to explicitly check that
fdt_next_node()'s iteration hasn't left the starting node.  Second,
this allows fdt_next_node() to be used to implement
_fdt_node_end_offset() considerably simplifying the latter function.

The other users of fdt_next_node() either don't need to iterate out of
the starting node, or don't pass a depth parameter at all.  Any
callers that really need to iterate out of the starting node, but keep
tracking depth can do so by biasing the initial depth value.

This is a semantic change, but I think it's very unlikely to break any
existing library users.
Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      2c0b843e
    • W
      Merge branch 'master' of git://git.denx.de/u-boot-i2c · ed9953d6
      由 Wolfgang Denk 提交于
      ed9953d6
    • W
      Merge branch 'master' of git://git.denx.de/u-boot-mpc85xx · da72af8d
      由 Wolfgang Denk 提交于
      da72af8d
    • K
      rtc: remove broken rtc_read and rtc_write declarations · c2eb8be7
      由 Kim Phillips 提交于 
      commit 04e11cf3 "rtc: add support for 4543 RTC (manufactured by e.g.
EPSON)" introduces the following build error on boards configuring e.g,
the ds1374 rtc:

Configuring for MPC837XEMDS board...
ds1374.c:103: error: static declaration of 'rtc_read' follows non-static declaration
/home/r1aaha/git/u-boot/include/rtc.h:64: error: previous declaration of 'rtc_read' was here
ds1374.c:104: error: conflicting types for 'rtc_write'
/home/r1aaha/git/u-boot/include/rtc.h:65: error: previous declaration of 'rtc_write' was here

this reverts the erroneous chunk.
Signed-off-by: NKim Phillips <kim.phillips@freescale.com>
Acked-by: NDetlev Zundel <dzu@denx.de>
CC: Detlev Zundel <dzu@denx.de>
CC: Andreas Pfefferle <ap@denx.de>
      c2eb8be7
    • K
      85xx/86xx: Ensure MP boot page is not used · fc39c2fd
      由 Kumar Gala 提交于 
      We had a bug on 86xx in which the boot page used to bring up secondary
cores was being overwritten and used for the malloc region in u-boot.

We need to reserve the region of memory that the boot page is going to
be put at so nothing uses it.
Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
Acked-by: NBecky Bruce <beckyb@kernel.crashing.org>
      fc39c2fd
    • K
      85xx: Introduce determine_mp_bootpg() helper. · c840d26c
      由 Kumar Gala 提交于 
      Match determine_mp_bootpg() that was added for 86xx.  We need this to
address a bug introduced in v2009.03 with 86xx MP booting.  We have to
make sure to reserve the region of memory used for the MP bootpg() so
other u-boot code doesn't use it.

Also added a comment about how cpu_reset() is dealing w/an errata on
early 85xx MP HW.
Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      c840d26c
    • K
      86xx: Cleanup MP support · 7649a590
      由 Kumar Gala 提交于 
      * Use CONFIG_MP instead of CONFIG_NUM_CPUS to match 85xx
* Introduce determine_mp_bootpg() helper.  We'll need this to address a
  bug introduced in v2009.03 with 86xx MP booting.  We have to make sure
  to reserve the region of memory used for the MP bootpg() so other
  u-boot code doesn't use it.
* Added dummy versions of cpu_reset(), cpu_status() & cpu_release() to
  allow cmd_mp.c to build and work. In the future we should look at
  implementing all these functions. This could be common w/85xx if we
  use spin tables on 86xx.
Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      7649a590
  3. 01 4月, 2009 1 次提交
  5. 31 3月, 2009 10 次提交
  7. 30 3月, 2009 5 次提交
  9. 29 3月, 2009 4 次提交
  11. 28 3月, 2009 7 次提交
  13. 27 3月, 2009 4 次提交
  15. 26 3月, 2009 1 次提交