- 10 8月, 2010 7 次提交
-
-
由 Ben Warren 提交于
Commit 6e37b1a3a25004d3df5867de49fff6b3fc9c4f04 modifies several net calls to take a (const char *) parameter instead of (char *), but in some cases the modified functions call other functions taking (char *). The end result is warnings about discarding the const qualifier. This patch fixes these other function signatures. Signed-off-by: NBen Warren <biggerbadderben@gmail.com>
-
由 Mike Frysinger 提交于
For code that uses miiphy_{read,write}, every call invokes a full look up of the mii list. There is already a "current_mii" cache that is used by some code, but have the miiphy_{read,write} function use it as well. This does increase the code size slightly, but I think it's worth it. Signed-off-by: NMike Frysinger <vapier@gentoo.org> Signed-off-by: NBen Warren <biggerbadderben@gmail.com>
-
由 Mike Frysinger 提交于
Rather than have every func re-implement the list walking code, do it one local function. This shrinks the resulting object code a little while making the source much more manageable. Signed-off-by: NMike Frysinger <vapier@gentoo.org> Signed-off-by: NBen Warren <biggerbadderben@gmail.com>
-
由 Mike Frysinger 提交于
The driver name does not need to be writable, so constify it. Signed-off-by: NMike Frysinger <vapier@gentoo.org> Signed-off-by: NBen Warren <biggerbadderben@gmail.com>
-
由 Kim Phillips 提交于
continuation of commit 2ecc2262d66a286e3aac79005bcb5f461312dea8 "net ppc: fix ethernet device names with spaces" (currently in u-boot-net.git) for QE based parts. Signed-off-by: NKim Phillips <kim.phillips@freescale.com> Acked-by: NDave Liu <daveliu@freescale.com> Signed-off-by: NBen Warren <biggerbadderben@gmail.com>
-
由 Heiko Schocher 提交于
since commit 1384f3bb ethernet names with spaces drop a Warning: eth device name has a space! message. This patch fix it for: - "FEC ETHERNET" devices found on mpc512x, mpc5xxx, mpc8xx and mpc8220 boards. renamed to "FEC". - "SCC ETHERNET" devices found on mpc8xx, mpc82xx based boards. Renamed to "SCC". - "HDLC ETHERNET" devices found on mpc8xx boards Renamed to "HDLC" - "FCC ETHERNET" devices found on mpc8260 and mpc85xx based boards. Renamed to "FCC" Tested on the kup4k board. Signed-off-by: NHeiko Schocher <hs@denx.de> Signed-off-by: NBen Warren <biggerbadderben@gmail.com>
-
由 Stefano Babic 提交于
After discussion on the ML it is suggested to drop unrequired and not useful characters from the device name. This patch changes the name for the fec_mxc driver from "FEC_MXC" to "FEC". Signed-off-by: NStefano Babic <sbabic@denx.de> Signed-off-by: NBen Warren <biggerbadderben@gmail.com>
-
- 09 8月, 2010 19 次提交
-
-
由 Marek Vasut 提交于
Signed-off-by: NMarek Vasut <marek.vasut@gmail.com>
-
由 Marek Vasut 提交于
Signed-off-by: NMarek Vasut <marek.vasut@gmail.com>
-
由 Marek Vasut 提交于
Signed-off-by: NMarek Vasut <marek.vasut@gmail.com>
-
由 Mike Frysinger 提交于
Simply trying to include a basic header file like stdlib.h on OS X 10.5 and then building with -traditional-cpp fails with lots of errors like: In file included from /usr/include/stdlib.h:63, from test.c:3: /usr/include/available.h:85: error: stray '#' in program /usr/include/available.h:85: error: syntax error before numeric constant /usr/include/available.h:86: error: stray '#' in program In the past, I hadn't noticed because the old logic for these flags were restricted to Darwin running on PowerPC systems while I'm running on an Intel system. But after some recent clean ups and changes, the flag was being applied to all Darwin systems and my host tools broke. Signed-off-by: NMike Frysinger <vapier@gentoo.org>
-
由 Feng Wang 提交于
Original bug description from Feng (fdt_resize() bug caused "WARNING: could not set linux, initrd-start FDT_ERR_NOSPACE."): What I got is an error: "WARNING: could not set linux,initrd-start FDT_ERR_NOSPACE." after loading Device Tree blob. This in turn caused linux to miss init part. After some digging, I found out the reason for this error, it is caused by fdt_resize(). FDT blob got resized after filling in all board specific information of PowerPC. (in boot_body_linux()). It reduced blob size with only extra space for two fdt_reserve_entry, one for fdt itself, and one for initrd. Then it's aligned to a 0x1000 page boundary. However, later in fdt_initrd(), it could add two more properties, initrd-start AND initrd-end, each one needs at least two fdt_reserve_entry sizes done by _fdt_add_property() (name and value). Thus, the two fdt_reserve_entry extra space is not sufficient. So for some specific fdt size which is just under the page boundary after resizing, this will cause an error of FDT_ERR_NOSPACE in fdt_initrd() when setting those two properties, and failed to pass initrd information to linux. My fix is in fdt_resize(), leave at least 4 fdt_reserve_entry for initrd. So instead of 2*sizeof(struct fdt_reserve_entry) for actual_totalsize, use 5*sizeof(struc fdt_reserve_entry). Stefan: I got this same error on katmai, when trying to boot with initrd (run flash_self). This patch fixes this issue. Signed-off-by: NFeng Wang <fwang02@harris.com> Tested-by: NStefan Roese <sr@denx.de> Cc: Jerry Van Baren <gvb.uboot@gmail.com> Acked-by: NGerald Van Baren <vanbaren@cideas.com>
-
由 Frans Meulenbroeks 提交于
removed a variable that was not used Signed-off-by: NFrans Meulenbroeks <fransmeulenbroeks@gmail.com>
-
由 Frans Meulenbroeks 提交于
Most of the files have U_BOOT_CMD on a separate line, but a few didn't and had the first line on the same line as U_BOOT_CMD. This changes these files by adding a line break and a tab Signed-off-by: NFrans Meulenbroeks <fransmeulenbroeks@gmail.com>
-
由 Frans Meulenbroeks 提交于
removed the command name from the help message as it is already printed. for cmd_mmc also rewrote the message a little bit Signed-off-by: NFrans Meulenbroeks <fransmeulenbroeks@gmail.com>
-
由 Detlev Zundel 提交于
The invalidation of the old environment instance did not work for flashes supporting hardware locking. Now we unlock/lock around this update also. Signed-off-by: NDetlev Zundel <dzu@denx.de>
-
由 Mike Frysinger 提交于
If a flash is unable to be detected, and then someone calls flash_protect on it (like the common code does in flash_init), the flash_protect logic will dereference a NULL pointer. Since flash_protect already does sanity checking on the info structs, add a NULL pointer check in there. Signed-off-by: NMike Frysinger <vapier@gentoo.org>
-
由 Wolfgang Denk 提交于
Fix error handling in getenv_f() when the user provided buffer is too short to hold the variable name; make sure to truncate and NUL-terminate without overwriting the buffer limits. Signed-off-by: NWolfgang Denk <wd@denx.de>
-
由 Mike Frysinger 提交于
Signed-off-by: NMike Frysinger <vapier@gentoo.org>
-
由 Mike Frysinger 提交于
Signed-off-by: NMike Frysinger <vapier@gentoo.org>
-
由 Mike Frysinger 提交于
Applying a little creative format string allows us to shrink the initial data read & display loop by only calling printf once. Re-using the local data buffer to generate the string we want to display then allows us to output everything with just one printf call instead of multiple calls to the putc function. The local stack buffer needs increasing by 1 byte, but the resulting code shrink and speed up is worth it I think. Signed-off-by: NMike Frysinger <vapier@gentoo.org>
-
由 Mike Frysinger 提交于
No need to output spaces 1 char at a time in a loop when the printf code can do the same thing with the right format string. This shrinks things and gives a nice speed up when killing off lines more than a byte or two as printf will send out the buffer in one big chunk. Signed-off-by: NMike Frysinger <vapier@gentoo.org>
-
由 Heiko Schocher 提交于
Signed-off-by: NHeiko Schocher <hs@denx.de>
-
由 Heiko Schocher 提交于
- nfs-options removed - hda->sda changed - mtd parts added - loadaddress changed - cmd-line length increased - lcd stuff removed - code cleanup (use I/O accessors etc.) Signed-off-by: NKlaus Heydeck <heydeck@kieback-peter.de>
-
由 Stephan Linz 提交于
Platforms with flat device tree support can use a bootmap to relocate the fdt_blob. This is not a must. That's why the relocation function boot_relocate_fdt() should be use only if CONFIG_OF_LIBFDT was defined together with CONFIG_SYS_BOOTMAPSZ (see common/cmd_bootm.c). On MicroBlaze platforms there is no need to use a bootmap to relocate a fdt blob. So we need a more precise focus on the compilation and usage of boot_relocate_fdt(). In general it is valid to exclude the function boot_relocate_fdt() if the bootmap size CONFIG_SYS_BOOTMAPSZ is not defined. Signed-off-by: NStephan Linz <linz@li-pro.net>
-
由 Nobuhiro Iwamatsu 提交于
Some Linux distributions include the "mkimage" as a package. This commit provides a manual page for mkimage. Signed-off-by: NNobuhiro Iwamatsu <iwamatsu@nigauri.org> Added documentation for FIT images and examples. Moved to doc/ directory. Signed-off-by: NWolfgang Denk <wd@denx.de>
-
- 08 8月, 2010 3 次提交
-
-
由 Matthias Weisser 提交于
If both LZMA and LZO compressions are used there is a compile error in cmd_bootm.c Signed-off-by: NMatthias Weisser <weisserm@arcor.de>
-
由 Aaron Pace 提交于
Doubly-indirect block numbers are compared against the first-level indirect block when checking for a cached copy. This is causing the doubly-indirect block to be re-read each time it is accessed. Repairing this reduces load time for a 70M file from 72 seconds to 38 seconds. Signed-off-by: NAaron Pace <Aaron.Pace@alcatel-lucent.com>
-
由 Matthew McClintock 提交于
If the user sets bootm_low and does not set bootm_size, u-boot will report the memory node in the flat device tree incorrectly. Instead of reporting the remaining size of memory, it will report the total available memory which is incorrect. Specifically this fixes the situation when booting a relocatable kernel and the memory is reported as an offset and size in the device tree, and the size needs to be adjusted accordingly. Signed-off-by: NMatthew McClintock <msm@freescale.com> Acked-by: NKumar Gala <galak@kernel.crashing.org>
-
- 07 8月, 2010 1 次提交
-
-
由 Wolfgang Denk 提交于
Idea and implementation courtesy of Kim Phillips <kim.phillips@freescale.com> Signed-off-by: NWolfgang Denk <wd@denx.de>
-
- 06 8月, 2010 1 次提交
-
-
由 Wolfgang Denk 提交于
Some commands (like 'mii') use this name to select devices, but they break when those names contain spaces. So drop the space from Ethernet driver names (cf. commit 1384f3bb). Signed-off-by: NWolfgang Denk <wd@denx.de> Cc: Ben Warren <biggerbadderben@gmail.com>
-
- 04 8月, 2010 3 次提交
-
-
由 Wolfgang Denk 提交于
While running from flash, i. e. before relocation, we have only a limited C runtime environment without writable data segment. In this phase, some configurations (for example with environment in EEPROM) must not use the normal getenv(), but a special function. This function had been called getenv_r(), with the idea that the "_r" suffix would mean the same as in the _r_eentrant versions of some of the C library functions (for example getdate vs. getdate_r, getgrent vs. getgrent_r, etc.). Unfortunately this was a misleading name, as in U-Boot the "_r" generally means "running from RAM", i. e. _after_ relocation. To avoid confusion, rename into getenv_f() [as "running from flash"] Signed-off-by: NWolfgang Denk <wd@denx.de> Acked-by: NDetlev Zundel <dzu@denx.de>
-
由 Mike Frysinger 提交于
Avoid warning: cmd_bootm.c: In function 'bootm_load_os': cmd_bootm.c:394: warning: passing argument 2 of 'lzmaBuffToBuffDecompress' from incompatible pointer type For 32 bit systems, this change shouldn't make a difference to code size since sizeof(size_t) and sizeof(unsigned int) are equal. But it does fix the warning. Signed-off-by: NMike Frysinger <vapier@gentoo.org>
-
-
- 02 8月, 2010 3 次提交
-
-
由 Kim Phillips 提交于
doing so helps avant garde users, such as those using simulators that allow users to configure the number of cores, so as to not have to manually adjust u-boot sources. h/w should also be reliably setting FRR NCPU in the future. Signed-off-by: NKim Phillips <kim.phillips@freescale.com> Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
-
由 Kim Phillips 提交于
because it's convenient. Signed-off-by: NKim Phillips <kim.phillips@freescale.com> Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
-
由 Kumar Gala 提交于
Add support for the P4080DS board, with the following features: * 36-bit only * Boots from NOR flash * FMAN drivers NOT supported * SPD DDR initialization Signed-off-by: NEd Swarthout <Ed.Swarthout@freescale.com> Signed-off-by: NEmil Medve <Emilian.Medve@Freescale.com> Signed-off-by: NBecky Bruce <beckyb@kernel.crashing.org> Signed-off-by: NAshish Kalra <Ashish.Kalra@freescale.com> Signed-off-by: NStuart Yoder <stuart.yoder@freescale.com> Signed-off-by: NDave Liu <daveliu@freescale.com> Signed-off-by: NLan Chunhe-B25806 <b25806@freescale.com> Signed-off-by: NScott Wood <scottwood@freescale.com> Signed-off-by: NKim Phillips <kim.phillips@freescale.com> Signed-off-by: NRoy Zang <tie-fei.zang@freescale.com> Signed-off-by: NTimur Tabi <timur@freescale.com> Signed-off-by: NAndy Fleming <afleming@freescale.com> Signed-off-by: NYork Sun <yorksun@freescale.com> Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
-
- 30 7月, 2010 1 次提交
-
-
由 Mike Frysinger 提交于
Signed-off-by: NMike Frysinger <vapier@gentoo.org>
-
- 27 7月, 2010 2 次提交
-
-
由 york 提交于
Enabled SPD Enabled DDR2 Enabled hwconfig Signed-off-by: NYork Sun <yorksun@freescale.com>
-
由 york 提交于
Changes for P2020DS DDR applies to other 8xxx platform Signed-off-by: NYork Sun <yorksun@freescale.com>
-