Change ext2 to ext3 for am335x-evm#1
Open
koenkooi wants to merge 269 commits intojoelagnel:masterfrom
koenkooi:patch-1
Open
Change ext2 to ext3 for am335x-evm#1koenkooi wants to merge 269 commits intojoelagnel:masterfrom koenkooi:patch-1
koenkooi wants to merge 269 commits intojoelagnel:masterfrom
koenkooi:patch-1
Conversation
AM35xx do not have DPLL2. The patch skips DPLL2 related init code on AM35xx. DPLL2 init is adding unnecessary delays to the boot time as the code waits 12000000 cycles for DPLL to lock which never happens on AM35xx. Signed-off-by: Ranjith Lohithakshan <ranjithl@ti.com> Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
This patch adds support for the AM/DM37x devices. The initialization depends upon run-time detection of the silicon family. This allows same binary to be used across OMAP35x and AM/DM37x family. Signed-off-by: Sanjeev Premi <premi@ti.com> Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
192MHz configuration has some residue effect on Kernel, results is DSS clock configuration error which need to debug further.
Signed-off-by: Vaibhav Hiremath<hvaibhav@ti.com>
Configure M3, M4, M5, M6 to expected defaults
M3 - 54MHz
M4 - 96MHz
M5 - 216MHz
M6 - 288MHz
Signed-off-by: Vaibhav Hiremath<hvaibhav@ti.com> Signed-off-by: Steve Sakoman <steve@sakoman.com> Reported-by: Steve Sakoman <steve@sakoman.com>
Operating on a sys clock lower than 19.2MHz can lead to DDR corruption when exiting OFF mode. DM37x is now made to operate at 26MHz sys clock and the internal sys clock division is removed. All DPLL parameters now recomputed with 26MHz as sys clock input. Signed-off-by: Ranjith Lohithakshan <ranjithl@ti.com> Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
Allows one to set the omap clock rate via "setenv mpurate 720" for example OMAP3: Beagle, Overo: remove omapfb.debug=y from default env Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
set mpurate to 600 for revB and revC1-3 and to 1000 for xM Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
This defaults to "on" condition for USB and DVI. May want to revise for power savings. Signed-off-by: Jason Kridner <jkridner@beagleboard.org> Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
Enable ethernet, net support in am3517 configuration. Signed-off-by: Sriramakrishnan <srk@ti.com>
Reduced the MTU_BLOCKSIZE to 512 bytes for better inter-op. Signed-off-by: Sriramakrishnan <srk@ti.com>
The current implementation assumes that the EMAC driver will be used on Socs from Davinci Family only. The AM3517 Soc (non- davinci)uses the same MAC controller and can leverage the existing driver. To make the implementation more generic, moved arch independent definitions to separate header file and added am3517 specific definitions to separate file. Signed-off-by: Sriramakrishnan <srk@ti.com>
Added ifdefs around PHY handling functions. Signed-off-by: Sriramakrishnan <srk@ti.com>
Adds "DaVinci EMAC" as the name of the device so that it gets printed as "Using DaVinci EMAC device" during network access (dhcp, tftp) instead of empty name in "Using" statement. This name also gets reflected in 'ethact' env variable. Signed-off-by: Hemant Pedanekar <hemantp@ti.com> Signed-off-by: Sriramakrishnan <srk@ti.com>
On Socs like AM3517 the BD address from CPPI perspecive is different from that of CPU view. Add logic for BD_TO_HW address translation in such cases. Signed-off-by: Sriramakrishnan <srk@ti.com>
The GPIO pin used for resetting the external LAN chip has changed for Rev.G board. Signed-off-by: Sriramakrishnan <srk@ti.com>
Add EMAC driver initialization to board init sequence and program mux accordingly Signed-off-by: Sriramakrishnan <srk@ti.com>
This patch enables auto-negotiation on every open call. Also, the speed,duplex,rmii control bits are programmed based on auto-negn results Signed-off-by: Sriramakrishnan <srk@ti.com>
Added a missing double quote to fix compiler warning. Also removed unused local variable. Signed-off-by: Sriramakrishnan <srk@ti.com>
This reverts commit 32d9301fd3e0561ccf66d2d96ccc30a29cd245a5. Conflicts: arch/arm/cpu/arm_cortexa8/omap3/board.c
This reverts commit 1f2effcbc64f2cfb93e75e81138145f5d304ec1e.
This patch updates the mach-types.h based on the latest linux kernel Signed-off-by: Thomas Weber <weber@corscience.de>
PLL clock config for i2c1 & i2c2 is added. However, i2c2 pin-mux is yet to be finalized. Hence this patch does not contain pin-mux for i2c2. when we are in i2c correction also, allgin i2c0 pin-mux with Linux Signed-off-by: Hebbar, Gururaja <gururaja.hebbar@ti.com>
This patch 1. fixes incorrect calling of printf() from board_init() where console is still not set 2. updates Coding style Signed-off-by: Hebbar, Gururaja <gururaja.hebbar@ti.com>
This patch is added to correct TLK110 PHY address. The PHY address is changed from 1 (00001) to 30 (11110) Signed-off-by: Chandan Nath <chandan.nath@ti.com> Signed-off-by: Hebbar, Gururaja <gururaja.hebbar@ti.com>
Doing setenv in default_serial_console() was causing U-boot to hang. Move setenv on console to board_late_init(). Signed-off-by: Afzal Mohammed <afzal@ti.com> Signed-off-by: Hebbar, Gururaja <gururaja.hebbar@ti.com>
This patch is to support 2 byte address write for EEPROM. Existing omap24xx_i2c.c does not support address length greater than one. 1. CAT24C256 EEPROM requires writing two byte address for write/read operations. 2. To support the EEPROM write/read support call the i2c_read/i2c_write API with alen 2. Also, this patch corrects the handling of error states in i2c functionalities. On detecting I2C bus busy, return from function with error status added. when we are at it, 1. I2C printf are removed since these functionalities might be called before console sets up. 2. Removed the unused functions & there by eliminating warning. Signed-off-by: Philip, Avinash <avinashphilip@ti.com> Signed-off-by: Hebbar, Gururaja <gururaja.hebbar@ti.com>
This patch changes reg offset to depend on i2c base address rather than being complete address themselves. This also make way for implementing MULTI-I2C feature. Signed-off-by: Hebbar, Gururaja <gururaja.hebbar@ti.com>
All AM335X EVM support atleast 2 i2c busses (i2c0 i2c1/i2c2). So enable support to access them. Also, EEPROM read command requires to send two bytes of address. so fix the same Signed-off-by: Hebbar, Gururaja <gururaja.hebbar@ti.com>
This patch adds support for enabling In Band mode in 10 mbps speed. RGMII supports 1 Gig and 100 mbps mode for Forced mode of operation. For 10mbps mode it should be configured to in band mode so that link status, duplexity and speed are determined from the RGMII input data stream Signed-off-by: Chandan Nath <chandan.nath@ti.com> Signed-off-by: Hebbar, Gururaja <gururaja.hebbar@ti.com>
This patch removes extra rmii1_refclk and rmii2_refclk pinmux configuration from rgmii pinmux configuration which are not required for current mode of operation. Also, this pins are been used by audio and should not be configure here. Signed-off-by: Chandan Nath <chandan.nath@ti.com> Signed-off-by: Hebbar, Gururaja <gururaja.hebbar@ti.com>
Through use of #define, enable display of evm info Signed-off-by: Hebbar, Gururaja <gururaja.hebbar@ti.com>
u-boot 1st stage enables required uart. so enable early printf in 2nd stage. Signed-off-by: Hebbar, Gururaja <gururaja.hebbar@ti.com>
Allign spi1 pin-mux as per Linux. This patch enable spi flash on IA Board accessible Signed-off-by: Hebbar, Gururaja <gururaja.hebbar@ti.com>
Signed-off-by: Hebbar, Gururaja <gururaja.hebbar@ti.com>
While merging bring-up branch to integration branch, evm type related boot. This patch corrcts the same. Signed-off-by: Hebbar, Gururaja <gururaja.hebbar@ti.com>
Initially all EEPROM were assumed to contain valid EVM Configuration. However few EVM's are seen with empty/incorrect EEPROM data. In such cases, this patch provides valid fallback method In case of errors, fallback to default configuration. board_id = GP_BOARD; profile = 0 daughter_board_connected = TRUE; Signed-off-by: Hebbar, Gururaja <gururaja.hebbar@ti.com>
Signed-off-by: Joel A Fernandes <agnel.joel@gmail.com>
Signed-off-by: Joel A Fernandes <agnel.joel@gmail.com>
…teve Kipisz for the BeagleBone board Signed-off-by: Joel A Fernandes <agnel.joel@gmail.com>
…are for the EVM Signed-off-by: Joel A Fernandes <agnel.joel@gmail.com>
Signed-off-by: Joel A Fernandes <agnel.joel@gmail.com>
Signed-off-by: Joel A Fernandes <agnel.joel@gmail.com>
Signed-off-by: Joel A Fernandes <agnel.joel@gmail.com>
This does not affect functionality as the 'binary blob' is relocotable and is loaded by first-stage. However debugging tools will hate it as the symbols are not mapped to what is loaded in memory. This fixes it. Signed-off-by: Joel A Fernandes <agnel.joel@gmail.com>
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
joelagnel
pushed a commit
that referenced
this pull request
Oct 11, 2011
Spl wip 07oct ti814x evm spl nand
eballetbo
referenced
this pull request
in eballetbo/u-boot
Aug 5, 2012
This reverts commit 69d26d0. Apparently, this commit got mainline only because of out-of-tree port and causes breakage on board that is mainline. Revert. Reason: * The OOT board has 512MB of DRAM, enabling this additional address line enabled it to work fine with 512MB of RAM. * Every mainline port has max. 256MB of DRAM, therefore this revert has no impact on any mainline port * Though this caused a problem with new M28 board with 256MB of DRAM where the chips are wired differently. The patch-to-be-reverted caused the DRAM to behave like this: [128MB chunk #1][128MB chunk #1 again][128MB chunk #2][128MB chunk #2 again] Therefore to retain the current one-memory-init-rules-them-all situation, revert this patch until another board emerges and will actually be pushed mainline that needs different setup. Signed-off-by: Marek Vasut <marex@denx.de> Cc: Wolfgang Denk <wd@denx.de> Cc: Detlev Zundel <dzu@denx.de> Cc: Stefano Babic <sbabic@denx.de> Cc: Fabio Estevam <festevam@gmail.com>
eballetbo
referenced
this pull request
in eballetbo/u-boot
May 30, 2014
Since B&R boards uses only MMC-Controller #1, it only wastes time if we initialize #0 first to see that there is nothing. Cc: <trini@ti.com> Acked-by: Pantelis Antoniou <panto@antoniou-consulting.com> Signed-off-by: Hannes Petermaier <oe5hpm@oevsv.at>
eballetbo
referenced
this pull request
in eballetbo/u-boot
Jul 11, 2014
Use get_device_and_partition() is better since: 1. It will call the device initialize function internally. So we can remove the mmc intialization code to save many lines. 2. It is used by fatls/fatload/fatwrite. So saveenv & load env should use it too. 3. It can parse the "D:P", "D", "D:", "D:auto" string to get correct device and partition information by run-time. Also we remove the FAT_ENV_DEVICE and FAT_ENV_PART. We use a string: FAT_ENV_DEVICE_AND_PART. For at91sam9m10g45ek, it is "0". That means use device 0 and if: a)device 0 has no partition table, use the whole device as a FAT file system. b)device 0 has partittion table, use the partition #1. Refer to the commit: 10a37fd for details of device & partition string. Signed-off-by: Josh Wu <josh.wu@atmel.com> Reviewed-by: Stephen Warren <swarren@nvidia.com>
eballetbo
referenced
this pull request
in eballetbo/u-boot
Jan 28, 2015
Attempting to run the sandbox leads to a segfault, because some dynamic
libraries (outside of u-boot) attempt to use malloc() to allocate memory
before u-boot's gd variable is initialized.
Check for gd not being NULL in the SYS_MALLOC_F_LEN handling, so that
malloc() doesn't crash when called at this point.
$ gdb -q --args ./u-boot
(gdb) r
Program received signal SIGSEGV, Segmentation fault.
0x0000000000412b9b in malloc (bytes=bytes@entry=37) at common/dlmalloc.c:2184
2184 if (!(gd->flags & GD_FLG_RELOC)) {
(gdb) p gd
$1 = (gd_t *) 0x0
(gdb) bt
#0 0x0000000000412b9b in malloc (bytes=bytes@entry=37) at common/dlmalloc.c:2184
#1 0x00007ffff75bf8e1 in set_binding_values (domainname=0x7ffff11f4f12 "libgpg-error", dirnamep=0x7fffffffe168, codesetp=0x0)
at bindtextdom.c:228
#2 0x00007ffff75bfb4c in set_binding_values (codesetp=0x0, dirnamep=0x7fffffffe168, domainname=<optimized out>) at bindtextdom.c:350
#3 __bindtextdomain (domainname=<optimized out>, dirname=0x7ffff11f4f00 "/usr/share/locale") at bindtextdom.c:348
#4 0x00007ffff11eca17 in ?? () from /lib/x86_64-linux-gnu/libgpg-error.so.0
#5 0x00007ffff7dea9fa in call_init (l=<optimized out>, argc=argc@entry=1, argv=argv@entry=0x7fffffffe208,
env=env@entry=0x7fffffffe218) at dl-init.c:78
#6 0x00007ffff7deaae3 in call_init (env=0x7fffffffe218, argv=0x7fffffffe208, argc=1, l=<optimized out>) at dl-init.c:36
#7 _dl_init (main_map=0x7ffff7ffe1a8, argc=1, argv=0x7fffffffe208, env=0x7fffffffe218) at dl-init.c:126
#8 0x00007ffff7ddd1ca in _dl_start_user () from /lib64/ld-linux-x86-64.so.2
Signed-off-by: Rabin Vincent <rabin@rab.in>
Acked-by: Simon Glass <sjg@chromium.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.