- May 01, 2013
-
-
Egbert Eich authored
Bugfix: Here at this place we need the fat size in sectors not bytes. This was found during code review when adding support for storage devices with blocksizes != 512. Signed-off-by:
Egbert Eich <eich@suse.com>
-
Egbert Eich authored
For ISO we check the block size of the device if this is != the CD sector size we assume that the device has no ISO partition. Signed-off-by:
Egbert Eich <eich@suse.com>
-
Egbert Eich authored
Disks beyond 2T in size use blocksizes of 4096 bytes. However a lot of code in u-boot still assumes a 512 byte blocksize. This patch fixes the handling of GPTs. Signed-off-by:
Egbert Eich <eich@suse.com>
-
Egbert Eich authored
Devices that used to have a whole disk FAT filesystem but got then partitioned will most likely still have a FAT or FAT32 signature in the first sector as this sector does not get overwritten by a partitioning tool (otherwise the tool would risk to kill the mbr). The current partition search algorithm will erronously detects such a device as a raw FAT device. Instead of looking for the FAT or FAT32 signatures immediately we use the same algorithm as used by the Linux kernel and first check for a valid boot indicator flag on each of the 4 partitions. If the value of this flag is invalid for the first entry we then do the raw partition check. If the flag for any higher partition is wrong we assume the device is neiter a MBR nor PBR device. Signed-off-by:
Egbert Eich <eich@suse.com>
-
Simon Glass authored
The number 512 appears quite a bit in the mmc code. Add a constant for this so that it can be used here and in other parts of the code (e.g. SPL code which loads from mmc). Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Vadim Bendebury <vbendeb@google.com>
-
Wolfgang Denk authored
Signed-off-by:
Wolfgang Denk <wd@denx.de> Acked-by:
Stefan Roese <sr@denx.de>
-
Wolfgang Denk authored
Align some comments. Signed-off-by:
Wolfgang Denk <wd@denx.de> Acked-by:
Stefan Roese <sr@denx.de>
-
Wolfgang Denk authored
Signed-off-by:
Wolfgang Denk <wd@denx.de> Conflicts: include/configs/m28evk.h
-
Wolfgang Denk authored
Change all "#define<TAB>" sequences into "#define<SPACE>" Signed-off-by:
Wolfgang Denk <wd@denx.de> Acked-by:
Marek Vasut <marex@denx.de>
-
Wolfgang Denk authored
Add "setexpr name gsub r s [t]" and "setexpr name sub r s [t]" commands which implement substring matching for the regular expression <r> in the string <t>, and substitution of the string <s>. The result is assigned to the environment variable <name>. If <t> is not supplied, the previous value of <name> is used instead. "gsub" performs global substitution, while "sub" will replace only the first substring. Both commands are closely modeled after the gawk functions with the same names. Examples: - Generate broadcast address by substituting the last two numbers of the IP address by "255.255": => print ipaddr ipaddr=192.168.1.104 => setexpr broadcast sub "(.*\\.).*\\..*" "\\1255.255" $ipaddr broadcast=192.168.255.255 - Depending on keyboard configuration (German vs. US keyboard) a barcode scanner may initialize the MAC address as C0:E5:4E:02:06:DC or as C0>E5>4E>02>06>DC. Make sure we always have a correct value: => print ethaddr ethaddr=C0>E5>4E>02>06>DC => setexpr ethaddr gsub > : ethaddr=C0:E5:4E:02:06:DC - Do the same, but substitute one step at a time in a loop until no futher matches: => setenv ethaddr C0>E5>4E>02>06>DC => while setexpr ethaddr sub > : > do > echo ----- > done ethaddr=C0:E5>4E>02>06>DC ----- ethaddr=C0:E5:4E>02>06>DC ----- ethaddr=C0:E5:4E:02>06>DC ----- ethaddr=C0:E5:4E:02:06>DC ----- ethaddr=C0:E5:4E:02:06:DC ----- C0:E5:4E:02:06:DC: No match => print ethaddr ethaddr=C0:E5:4E:02:06:DC etc. To enable this feature, the CONFIG_REGEX option has to be defined in the board config file. Signed-off-by:
Wolfgang Denk <wd@denx.de>
-
Wolfgang Denk authored
Simplify the argument checking for the "setexpr" command. This is done mainly to make future extensions easier. Also improve the help message for the one argument version of the command - this does not "load an address", but a value, which in this context may be a plain number or a pointer dereference. Signed-off-by:
Wolfgang Denk <wd@denx.de>
-
Wolfgang Denk authored
When CONFIG_REGEX is enabled, the new option "-e" becomes available which causes regular expression matches to be used. This allows for example things like these: - print all MAC addresses: => env grep -e eth.*addr eth1addr=00:10:ec:80:c5:15 ethaddr=00:10:ec:00:c5:15 - print all variables that have at least 2 colons in their value: => env grep -v -e :.*: addip=setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:${netdev}:off panic=1 eth1addr=00:10:ec:80:c5:15 ethaddr=00:10:ec:00:c5:15 ver=U-Boot 2013.04-rc1-00289-g497746b-dirty (Mar 22 2013 - 12:50:25) etc. Signed-off-by:
Wolfgang Denk <wd@denx.de>
-
Wolfgang Denk authored
Downloaded from http://slre.sourceforge.net/ and adapted for U-Boot environment. Used to implement regex operations on environment variables. Code size is ~ 3.5 KiB on PPC. To enable this code, define the CONFIG_REGEX option in your board config file. Note: There are more recent versions of the SLRE library available at http://slre.googlecode.com ; unfortunately, the new code has a heavily reorked API which makes it less usable for our purposes: - the return code is strings, which are more difficult to process - we don't get any information any more which sub-string of the data was matched by the given regex - it is much more cumbersome to work with arbitrary expressions, where for example the number of substrings for capturing are not known at compile time Also, there does not seem to be any real changes or improvements of the functionality. Because of this, we deliberately stick with the older code. Note 2: the test code (built when SLRE_TEST is defined) was modified to allow for more extensive testing; now we can test the regexp matching on all lines on a text file (instead of the whole data in the file as a single block). Signed-off-by:
Wolfgang Denk <wd@denx.de>
-
Wolfgang Denk authored
Add options to "env grep" command: -n : search only the envrironment variable names -v : search only their values -b : search both names and values (= default) An option "--" will stop parsing options, so to print variables that contain the striing "- " please use: env grep -- "- " Or to print all environment varioables which have a '-' in their name, use: env grep -n -- - Signed-off-by:
Wolfgang Denk <wd@denx.de>
-
Wolfgang Denk authored
Also drop hstrstr_r() which is not needed any more. The new code is way more flexible. Signed-off-by:
Wolfgang Denk <wd@denx.de>
-
Wolfgang Denk authored
The output of "env grep" is unsorted, and printing is done by a private implementation to parse the hash table. We have all the needed code in place in hexport_r() alsready, so let's use this instead. Here we prepare the code for this, without any functional changes yet. Signed-off-by:
Wolfgang Denk <wd@denx.de>
-
Peter Korsgaard authored
block_read returns unsigned long, so it doesn't make sense to check for < 0. and neither does marking the header structure as const and then casting away the constness to load data into it. Also cleanup some unneeded pointer casting while we're at it. Signed-off-by:
Peter Korsgaard <peter.korsgaard@barco.com> Reviewed-by:
Tom Rini <trini@ti.com>
-
Simon Glass authored
Enable these options to use FITs on sandbox. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
This allows write of files from the host filesystem in sandbox. There is currently no concept of overwriting the file and removing its existing contents - all writing is done on top of what is there. This means that writing 10 bytes to the start of a 1KB file will only update those 10 bytes, not truncate the file to 10 byte slong. If the file does not exist it is created. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Add a new method for saving that filesystems can implement. This mirrors the existing load method. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Enhance the source command to work with sandbox, by using map_sysmem() to convert a ulong address into a pointer. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
This allows passing of entire scripts to sandbox with the -c argument, which is useful for testing. Commands can be delimited with a newline or semicolon. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
This reverts commit 3b73459e. In practice it doesn't seem like a good idea to make the the working FDT point to the control FDT. Now that we can access the control FDT using the 'fdt' command, there is no need for this feature. Remove it. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
If we have no FDT, don't attempt to read from it. This allows sandbox to run without an FDT if required. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
By using map_sysmem() we can get the fdt command to work correctly with sandbox. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
There is an existing fdt command to deal with the working FDT. Enhance this to support the control FDT also (CONFIG_OF_CONTROL). Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
This conversion is required in a number of places in U-Boot. Add a standard function to provide this feature, so we avoid all the different variations in the way it is coded. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
At present this only checks working_fdt, but we want to check other FDTs also. So add the FDT to check as a parameter to fdt_valid(). Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
With sandbox it is tricky to add an FDT to the image at build time (or later) since we build an ELF file, not a plain binary, and the address space of the whole U-Boot is not accessible in the emulated memory map of sandbox. Sandbox can read files directly from the host, though, so add an option to read an FDT from a host file on start-up. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Add generic board support for sandbox. and remove the old board init code. Select CONFIG_SYS_GENERIC_BOARD for sandbox now that this is supported. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Tom Rini <trini@ti.com>
-
Simon Glass authored
In many cases, pointers to memory are passed around, and these pointers refer to U-Boot memory, not host memory. This in itself is not a problem. However, in a few places, we cast that pointer back to a ulong (being a U-Boot memory address). It is possible to convert many of these cases to avoid this. However there are data structures (e.g. struct bootm_headers) which use pointers. We could with a lot of effort adjust the structs and all code that uses them to use ulong instead of pointers. This seems like an unacceptable cost, since our objective with sandbox is to minimise the impact on U-Boot code while maximising the features available to sandbox. Therefore, create a map_to_sysmem() function which converts from a pointer to a U-Boot address. This can be used sparingly when needed. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
At present the generic board error can occur when configuring U-Boot, or during distclean, but this is incorrect. The existing autoconf.mk may come from an earlier U-Boot configuration which is about to be overwritten. Make the error conditional so that it will only be triggered when we are actually building U-Boot. This avoids a problem where the system is being reconfigured to remove CONFIG_SYS_GENERIC_BOARD on an architecture that does not support it. Currently this will print an error and require the manual removal of include/autoconf.mk. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
git://git.denx.de/u-boot-i2cTom Rini authored
-
Anatolij Gustschin authored
Devices in CONFIG_SYS_POST_I2C_IGNORES list may be absent and the rule is not to report I2C POST failure for devices in this list. Currently this doesn't work since probing for these devices isn't done and thus they are not marked as successfully probed. Ignore optional devices when checking for devices that didn't respond. Signed-off-by:
Anatolij Gustschin <agust@denx.de>
-
- Apr 30, 2013
-
-
Michal Simek authored
Watchdog can be used on Microblaze, PPC and Zynq hw designs. Signed-off-by:
Michal Simek <michal.simek@xilinx.com> Reviewed-by:
Tom Rini <trini@ti.com>
-
Michal Simek authored
Fix microblaze soft reset function and disable all cpu features. Especially disable caches because IRQs were off by disable_interrupts(). Reported-by:
John Williams <john.williams@xilinx.com> Signed-off-by:
Michal Simek <monstr@monstr.eu> Signed-off-by:
Michal Simek <michal.simek@xilinx.com>
-
Michal Simek authored
Setup environment and enable netconsole. Signed-off-by:
Michal Simek <monstr@monstr.eu> Signed-off-by:
Michal Simek <michal.simek@xilinx.com> Reviewed-by:
Tom Rini <trini@ti.com>
-
Michal Simek authored
Remove CONFIG_SYS_RESET_ADDRESS macro. It was there from historical point of view when soft reset was just jump to u-boot text start (not used right now). Signed-off-by:
Michal Simek <monstr@monstr.eu> Signed-off-by:
Michal Simek <michal.simek@xilinx.com>
-
- Apr 29, 2013
-
-
Michal Simek authored
This is a MIME GnuPG-signed message. If you see this text, it means that your E-mail or Usenet software does not support MIME signed messages. The Internet standard for MIME PGP messages, RFC 2015, was published in 1996. To open this message correctly you will need to install E-mail or Usenet software that supports modern Internet standards. Easier for using with patman. Signed-off-by:
Michal Simek <michal.simek@xilinx.com>
-