- 29 10月, 2015 12 次提交
-
-
由 Josh Wu 提交于
As we don't modify the 'name' parameter, so change it to const. Signed-off-by: NJosh Wu <josh.wu@atmel.com> Reviewed-by: NSimon Glass <sjg@chromium.org> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Gong Qianyu 提交于
The loop should check all ethenet devices, not only the first device, to set each specified ethaddr, or it'll cause failure when we use other devices. Signed-off-by: NGong Qianyu <Qianyu.Gong@freescale.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Stefan Brüns 提交于
smsc95xx_recv() does not reassemble bursts spread over multiple URBs. If there is a lot of broadcast traffic, the fifo will fill up to the burst cap limit. Lowering the burst cap to the URB size ensures no packet spans multiple urbs. Caveat, lower limit for working burst cap is 5/33 HS/FS packets. Signed-off-by: NStefan Brüns <stefan.bruens@rwth-aachen.de> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Stefan Brüns 提交于
Timeout handler should be stopped after reception of DHCPACK. If "autoload" is not set, the handler is immediately replaced by the TFTP handler, otherwise it may trigger before the next boot stage begins. Signed-off-by: NStefan Brüns <stefan.bruens@rwth-aachen.de> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Stefan Brüns 提交于
eth_rx() in the main reception loop may trigger sending a packet which is already timed out (or will immediately) upon reception of an ARP reply. As long as the ARP reply is pending, the timeout handler of a packet should be postponed. Happens on TFTP with bad network (e.g. WLAN). Signed-off-by: NStefan Brüns <stefan.bruens@rwth-aachen.de> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Stefan Brüns 提交于
net_start_again() will be called from net_loop() if state is NETLOOP_FAIL. Signed-off-by: NStefan Brüns <stefan.bruens@rwth-aachen.de> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Stefan Brüns 提交于
Pad has no len byte, so the normal parsing code fails. Signed-off-by: NStefan Brüns <stefan.bruens@rwth-aachen.de> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Stefan Brüns 提交于
RFC1542, 3.2: "The 'secs' field of a BOOTREQUEST message SHOULD represent the elapsed time, in seconds, since the client sent its first BOOTREQUEST message. Note that this implies that the 'secs' field of the first BOOTREQUEST message SHOULD be set to zero." Signed-off-by: NStefan Brüns <stefan.bruens@rwth-aachen.de> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Stefan Brüns 提交于
Rename check_packet to check_reply_packet to make its function more obvious. The check for DHCP_* values is completely off, as it should compare against DHCP option 53 (Message Type). Only valid value for any Bootp/DHCP reply is BOOTREPLY. Signed-off-by: NStefan Brüns <stefan.bruens@rwth-aachen.de> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Thomas Chou 提交于
This fixes the error when STATUS_LED_BOOT is not defined. Signed-off-by: NThomas Chou <thomas@wytron.com.tw> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Hannes Petermaier 提交于
If CONFIG_CMD_DHCP is enabled, the vci (vendor-class-identifier) string isn't inserted into the bootp-packet during SPL stage because the CONFIG_BOOTP_VCI_STRING instead CONFIG_SPL_NET_VCI_STRING We fix this with testing for CONFIG_SPL_BUILD and testing for existing CONFIG_SPL_NET_VCI_STRING. Signed-off-by: NHannes Schmelzer <oe5hpm@oevsv.at> Acked-by: NJoe Hershberger <joe.hershberger@ni.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Albert ARIBAUD \(3ADEV\) 提交于
TFTP source and destination port variable names are 'tftpsrcp' and 'tftpdstp' in the code, but 'tftpsrcport' and 'tftpdstport' in the README file. Fix the README. Add environment variable 'tftptimeoutcountmax'. As per the comments about the global variable tftp_timeout_count_max, make sure tftptimeoutcountmax is nonnegative. Introduce configuration option CONFIG_NET_TFTP_VARS, which controls whether environment variables tftpblocksize, tftptimeout, and tftptimoueoutcountmax are read by the TFTP client code. CONFIG_NET_TFTP_VARS defaults to y but can be set to n by targets with to tight size contraints. Make bf527-ezkit set CONFIG_NET_TFTP_VARS to n to keep the target size below limit.
-
- 25 10月, 2015 22 次提交
-
-
由 Gong Qianyu 提交于
get_clocks() should not be limited by ESDHC. Signed-off-by: NGong Qianyu <Qianyu.Gong@freescale.com>
-
由 Masahiro Yamada 提交于
We have finished Generic Board conversion for ARM and PowerPC, i.e. all the boards have been converted except OpenRISC, SuperH, SPARC, which have not supported Generic Board framework yet. Select SYS_GENERIC_BOARD in arch/Kconfig and delete all the macro defines in include/configs/*.h. Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
-
由 Simon Glass 提交于
This reverts commit 321f86e1. The original bug has been fixed. Signed-off-by: NSimon Glass <sjg@chromium.org> Tested-on: Zedboard and ZC706 board Tested-by: NMasahiro Yamada <yamada.masahiro@socionext.com> Tested-on: zc702 Tested-by: NMichal Simek <michal.simek@xilinx.com>
-
由 Simon Glass 提交于
We should not init the console this early since it precludes using driver model for the UART, since it is not set up at the start of board_init_f(). See the README for more information. The debug UART does not have this restriction. If we want to do early init with the console on it can be done in spl_board_init(). Move the preloader_console_init() call from board_init_f() to board_init_r(). Signed-off-by: NSimon Glass <sjg@chromium.org> Tested-by: NMasahiro Yamada <yamada.masahiro@socionext.com> Tested-by: NMichal Simek <michal.simek@xilinx.com>
-
由 Simon Glass 提交于
This C function should be used to do the early memory layout and init. This is beyond my powers, so just add a TODO for the maintainer. Signed-off-by: NSimon Glass <sjg@chromium.org> Acked-by: NMichal Simek <michal.simek@xilinx.com>
-
由 Simon Glass 提交于
There is quite a bit of assembler code that can be removed if we use the generic global_data setup. Less arch-specific code makes it easier to add new features and maintain the start-up code. Drop the unneeded code and adjust the hooks in board_f.c to cope. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
There is quite a bit of assembler code that can be removed if we use the generic global_data setup. Less arch-specific code makes it easier to add new features and maintain the start-up code. Drop the unneeded code and adjust the hooks in board_f.c to cope. Tested on LS2085ARDB and LS2085AQDS (armv8 SoC). Tested-by: NYork Sun <yorksun@freescale.com> Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Change the #ifdef so that the early malloc() area is not set up in SPL if CONFIG_SYS_SPL_MALLOC_START is defined. In that case it would never actually be used, and just chews up stack space. Signed-off-by: NSimon Glass <sjg@chromium.org> Tested-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
-
由 Simon Glass 提交于
Unfortunately memset() is not always available, so provide a substitute when needed. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
This function will be used by both SPL and U-Boot proper. So move it into a common place. Also change the #ifdef so that the early malloc() area is not set up in SPL if CONFIG_SYS_SPL_MALLOC_START is defined. In that case it would never actually be used, and just chews up stack space. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Stephen Warren 提交于
In the following snippet: if [ ! -x `which $prereq` ]; then When $prereq does not exist, `which $prereq` evaluates to the empty string, which results in *no* argument being passed to the -x operator, which then evaluates to true, which is the equivalent of the prereq having been found. In order for this to fail as expected, we must pass an empty argument, which then causes -x to fail. Do this by wrapping the `` in quotes so there's always an argument to -x, even if the value of the argument is zero-length. Signed-off-by: NStephen Warren <swarren@wwwdotorg.org> Reviewed-by: NSimon Glass <sjg@chromium.org> Tested-by: NSimon Glass <sjg@chromium.org>
-
由 Stephen Warren 提交于
In my patch series to replace fs/fat with "ff.c", I enhanced ff.c to optimize file reading, so that reads of contiguous clusters are submitted to the IO device as a single read. This test attempts to torture-test edge-cases of that enhancement. BTW, the only way I found to validate that this script actually does create non-contiguous files was to manually inspect the FAT bitmap in a hex dump of the FAT image. hdparm --fibmap doesn't work on loop-mounted filesystems. filefrag -v -e seems to lie about files being contiguous when they aren't. Signed-off-by: NStephen Warren <swarren@wwwdotorg.org> Reviewed-by: NSimon Glass <sjg@chromium.org> Tested-by: NSimon Glass <sjg@chromium.org>
-
由 Stephen Warren 提交于
itest accesses memory, and hence must map/unmap it. Without doing so, it accesses invalid addresses and crashes. Signed-off-by: NStephen Warren <swarren@wwwdotorg.org> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Roy Spliet 提交于
Under the assumptions of having a UBI volume called boot, containing a ubifs filesystem. Signed-off-by: NRoy Spliet <rspliet@eclipso.eu> Signed-off-by: NHans de Goede <hdegoede@redhat.com> Acked-by: NStephen Warren <swarren@nvidia.com>
-
由 Hans de Goede 提交于
Add generic fs support, so that commands like ls, load and test -e can be used on ubifs. Signed-off-by: NHans de Goede <hdegoede@redhat.com> Reviewed-by: NHeiko Schocher <hs@denx.de>
-
由 Hans de Goede 提交于
Implement the necessary functions for implementing generic fs support for ubifs. Signed-off-by: NHans de Goede <hdegoede@redhat.com> Reviewed-by: NHeiko Schocher <hs@denx.de>
-
由 Hans de Goede 提交于
Modify the ubifs u-boot wrapper function prototypes for generic fs use, and give them their own header file. This is a preparation patch for adding ubifs support to the generic fs code from fs/fs.c. Signed-off-by: NHans de Goede <hdegoede@redhat.com> Reviewed-by: NHeiko Schocher <hs@denx.de>
-
由 Hans de Goede 提交于
This is not necessary / useful when not building with CONFIG_SANDBOX and with the addition of ubifs support to the generic fs commands it actually gets in the way, since both operate on a fake / NULL blkdev. Signed-off-by: NHans de Goede <hdegoede@redhat.com> Acked-by: NStephen Warren <swarren@nvidia.com>
-
由 Pierre Aubert 提交于
Scripts are multi-file images, the imxtract command should handle them in the same manner. Signed-off-by: NPierre Aubert <p.aubert@staubli.com>
-
由 Thomas Huth 提交于
In the "Getting Started with Coccinelle - KVM edition" presentation that has been held by Julia Lawall at the KVM forum 2015 (see the slides at http://events.linuxfoundation.org/sites/events/files/slides/tutorial_kvm_0.pdf), she pointed out some bad return value checks in U-Boot that can be detected with Coccinelle by using the following config file: @@ identifier x,y; identifier f; statement S; @@ x = f(...); ( if (x < 0) S | if ( - y + x < 0) S ) This patch now fixes these issues. Signed-off-by: NThomas Huth <huth@tuxfamily.org>
-
由 Guillaume GARDET 提交于
Add CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG support and enable it to set 'board_rev' and 'board_name' envs. 'board_rev' can be used in scripts to determine what board we are running on and 'board_name' for pretty printing. Signed-off-by: NGuillaume GARDET <guillaume.gardet@free.fr> Cc: Stephen Warren <swarren@wwwdotorg.org> Acked-by: NStephen Warren <swarren@wwwdotorg.org>
-
由 Bernhard Nortmann 提交于
For current U-Boot to initialize status LEDs via status_led_init(), it is required to have both CONFIG_STATUS_LED and STATUS_LED_BOOT defined. This may be a particular concern with GPIO LEDs, where __led_init() is required to correctly set up the GPIO (gpio_request and gpio_direction_output). Without STATUS_LED_BOOT the initialization isn't called, which could leave the user with a non-functional "led" command - due to the fact that the LED routines in gpio_led.c use gpio_set_value() just fine, but the GPIO never got set up properly in the first place. I think having CONFIG_STATUS_LED is sufficient to justify a corresponding call to status_led_init(), even with no STATUS_LED_BOOT defined. To do so, common/board_r.c needs call that routine, so it now is exposed via status_led.h. Signed-off-by: NBernhard Nortmann <bernhard.nortmann@web.de> [trini: Add dummy __led_init to pca9551_led.c] Signed-off-by: NTom Rini <trini@konsulko.com>
-
- 24 10月, 2015 1 次提交
-
-
由 Bernhard Nortmann 提交于
For boards that support LEDs driven via GPIO (CONFIG_GPIO_LED), it may be useful to have some generic stubs (wrapper functions) for the "colored" LEDs. This allows defining STATUS_LED_* values directly to GPIO numbers, e.g.: #define STATUS_LED_GREEN 248 /* = PH24 */ To keep those optional, it's probably best to introduce an additional configuration setting. I've chosen CONFIG_GPIO_LED_STUBS for that. Placing the code in drivers/misc/gpio_led.c also ensures that it automatically depends on CONFIG_GPIO_LED too. Signed-off-by: NBernhard Nortmann <bernhard.nortmann@web.de> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
- 23 10月, 2015 5 次提交
-
-
由 Lokesh Vutla 提交于
Add driver model support for keystone serial driver. Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Thomas Chou 提交于
Convert altera_tse to driver model and phylib. Signed-off-by: NThomas Chou <thomas@wytron.com.tw> Reviewed-by: NMarek Vasut <marex@denx.de> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Thomas Chou 提交于
As the virtual address and physical address mapping of nios2 with MMU are different. Add a check of MMU, and fix the mapping. Signed-off-by: NThomas Chou <thomas@wytron.com.tw> Acked-by: NMarek Vasut <marex@denx.de> Reviewed-by: NLey Foon Tan <lftan@altera.com>
-
由 Thomas Chou 提交于
Add README.nios2 about how to add nios2 boards to u-boot. Signed-off-by: NThomas Chou <thomas@wytron.com.tw> Acked-by: NMarek Vasut <marex@denx.de>
-
由 Thomas Chou 提交于
As we use device tree to control u-boot now, the generic board can be removed. Signed-off-by: NThomas Chou <thomas@wytron.com.tw>
-