summaryrefslogtreecommitdiff
path: root/include/configs/tegra2-common.h
AgeCommit message (Collapse)Author
2012-08-22Initial Toradex Colibri T20 L4T R15 support.T20_LinuxImageV2.0Alpha1_20120808Marcel Ziswiler
2012-02-16arm: config: tegra: add bct offset addressVarun Wadekar
BUG=chromium-os:23496 TEST=build for Cardhu, Waluigi and Seaboard Change-Id: I32dbfa02ac1d6954b3a7e515914fbc0b6695f98b Signed-off-by: Varun Wadekar <vwadekar@nvidia.com> Reviewed-on: https://gerrit.chromium.org/gerrit/14683
2012-02-14arm: tegra2: split LP0 code to help future chipsVarun Wadekar
split the LP0 code for tegra2 into common LP0 code and chip specific warm boot code BUG=chromium-os:23496 TEST=build for Seaboard Change-Id: Ie04bf9ac17482a37afd0f4515dc3aafeb4f48ae7 Signed-off-by: Varun Wadekar <vwadekar@nvidia.com> Reviewed-on: https://gerrit.chromium.org/gerrit/15883
2012-02-08Revert "arm: tegra2: split LP0 code to help future chips"Brian Harring
This reverts commit 4c7502242627f64d91432cb4958be5f93f65fbff Don't think this is the cause of http://code.google.com/p/chromium-os/issues/detail?id=26116, but it was in the same batch so I'm reverting in the process. Change-Id: Icc013ced6c22e29d569ee4ca8ef73522154ec1a8 Reviewed-on: https://gerrit.chromium.org/gerrit/15561 Reviewed-by: Brian Harring <ferringb@chromium.org> Tested-by: Brian Harring <ferringb@chromium.org>
2012-02-08arm: tegra2: split LP0 code to help future chipsVarun Wadekar
split the LP0 code for tegra2 into common LP0 code and chip specific warm boot code BUG=chromium-os:23496 TEST=build for Seaboard Change-Id: Id9756c08f61502affa8beee636d883d01468e6ec Signed-off-by: Varun Wadekar <vwadekar@nvidia.com> Reviewed-on: https://gerrit.chromium.org/gerrit/13799
2011-10-13CHROMIUM: tegra: config: Add vmalloc to command line.Doug Anderson
This was added to the non-legacy kernel boot command line in <http://gerrit.chromium.org/gerrit/8373>. Since legacy has its own command line, we need it too. BUG=chromium-os:21650 TEST=Booted a newer kernel with this change and saw vmalloc=234MB. Change-Id: I1daaa71ce63892ef4534722caa705c4e9608c6ed Signed-off-by: Doug Anderson <dianders@chromium.org> Reviewed-on: http://gerrit.chromium.org/gerrit/10033 Reviewed-by: Sean Paul <seanpaul@chromium.org> Reviewed-by: Simon Glass <sjg@chromium.org>
2011-10-04tegra: Move common config into tegra-commonSimon Glass
It is arduous to maintain two very similar config files for Tegra 2 and Tegra3. This commit creates a new tegra-common.h to hold these common items. BUG=chromium-os:19004 TEST=build and boot on seaboard Change-Id: I1015d33c1ad581063618466335a27e6f82aab2f2 Reviewed-on: http://gerrit.chromium.org/gerrit/8683 Reviewed-by: Doug Anderson <dianders@chromium.org> Tested-by: Simon Glass <sjg@chromium.org>
2011-09-15tegra: Rename TEGRA2 to TEGRASimon Glass
Some constants are actually better of with generic Tegra family names. This also cleans up a few addresses which were in drivers rather than in the tegra.h header file. BUG=chromium-os:19004 TEST=build and boot on Seaboard Change-Id: I1cabb5191a2b36648a37268069beb3b43c12d0e1 Reviewed-on: http://gerrit.chromium.org/gerrit/7128 Reviewed-by: Simon Glass <sjg@chromium.org> Tested-by: Simon Glass <sjg@chromium.org>
2011-09-09tegra: Rename tegra2.h to tegra.hSimon Glass
We want to move to the idea of drivers and boards using generic tegra include files, and have these include files deal with the tegra2/3 differences. This will make it easier to share code between tegra2/3. BUG=chromium-os:19004 TEST=build and boot on Seaboard Change-Id: I9c4eec30707e41678fb307982a34fe383694ba16 Reviewed-on: http://gerrit.chromium.org/gerrit/7000 Reviewed-by: Yen Lin <yelin@nvidia.com> Reviewed-by: Tom Warren <twarren@nvidia.com> Tested-by: Simon Glass <sjg@chromium.org> Reviewed-by: Simon Glass <sjg@chromium.org>
2011-08-29tegra2: Implement board_panic_no_console()Simon Glass
BUG=chromium-os:17062 TEST=build and boot U-Boot without fdt: see message appear Change-Id: Ibc5fc8c6dbeefa6f95cdb2a771e3cd88fb44df31 Reviewed-on: http://gerrit.chromium.org/gerrit/6067 Reviewed-by: Anton Staaf <robotboy@chromium.org> Tested-by: Simon Glass <sjg@chromium.org>
2011-08-29CHROMIUM: Define CONFIG_USB_ETHER_SMSC95XX to support SMSC95XX USB Etherenet ↵Tom Wai-Hong Tam
Card. BUG=none TEST=booted u-boot and detected a SMSC9500 USB Etherenet Adadpter. Change-Id: I4800e431e0f981dc9dc4a41746cfe3584e96fc5d Reviewed-on: http://gerrit.chromium.org/gerrit/5715 Tested-by: Tom Wai-Hong Tam <waihong@chromium.org> Reviewed-by: Rong Chang <rongchang@chromium.org>
2011-08-29usb: add multiple controllers support for EHCIVincent Palatin
Add the ability to have several active EHCI controller on a system and implement it for Tegra EHCI controllers. BUG=chrome-os-partner:5043 TEST=boot an Aebl with USB key on USB3 port, boot a Kaen with USB key on USB1 port, boot a Kaen with USB key on USB3 port. Change-Id: Id37a9a4f92b986505fd6f8778d6f7964890d46b4 Reviewed-on: http://gerrit.chromium.org/gerrit/4981 Reviewed-by: Vincent Palatin <vpalatin@chromium.org> Tested-by: Vincent Palatin <vpalatin@chromium.org>
2011-08-29CHROMIUM: add cros_vboot/cros_legacy to kernel command lineChe-Liang Chiou
Some scripts, like those in factory process, detect whether Chrome OS is booted from a verified boot or a legacy boot by overloading crossystem. If crossystem returns a valid hardware id, the scripts believe that Chrome OS is booted from a verified boot. Although this trick works, it does not sound right. This patch adds "cros_vboot" and "cros_legacy" to kernel command line of verified boot firmware and legacy firmware so that the scripts can grep the value, or the crossystem may do the grep. This patch also fixes unsafe use of strncpy. BUG=chromium-os:15700,chromium-os:18139 TEST=verified boot and grep cros_vboot /proc/cmdline TEST=boot from legacy and grep cros_legacy /proc/cmdline Change-Id: Id5182c2f4e05fc566a17b1e50f9157f96c50f866 Reviewed-on: http://gerrit.chromium.org/gerrit/4645 Reviewed-by: Che-Liang Chiou <clchiou@chromium.org> Tested-by: Che-Liang Chiou <clchiou@chromium.org>
2011-08-29CHROMIUM: ARM: tegra: Remove TFTP user/serial# cruft.Doug Anderson
A recent change went in that simplified the TFTP names. http://gerrit.chromium.org/gerrit/4477 We should remove the user/serial# (and assocated docs) to keep things clean. BUG=chromium-os:17858 TEST=booted Change-Id: I1875f62eea0e64bd0e14b3b8298fc993f07b58d2 Reviewed-on: http://gerrit.chromium.org/gerrit/4498 Tested-by: Doug Anderson <dianders@chromium.org> Reviewed-by: Anton Staaf <robotboy@chromium.org>
2011-08-29Simplify naming of netboot artifactsNick Sanders
vmlinux.uimg, initrd.uimg BUG=chromium-os:17858 TEST=boots these images Change-Id: Ieae5b045b46b06c30b4f25766753aa2ac95064b1 Reviewed-on: http://gerrit.chromium.org/gerrit/4477 Reviewed-by: Rong Chang <rongchang@chromium.org> Reviewed-by: Hung-Te Lin <hungte@chromium.org> Tested-by: Nick Sanders <nsanders@chromium.org>
2011-08-29CHROMIUM: ARM: tegra: Remove 'secure_boot' variable from u-boot.Doug Anderson
The secure boot now can just call 'vboot_twostop' directly. BUG=chromium-os:17940 TEST=Built and booted non-legacy image. Change-Id: I20148f71007ef519ad09c3321eaf935f4a02bc26 Reviewed-on: http://gerrit.chromium.org/gerrit/4455 Tested-by: Doug Anderson <dianders@chromium.org> Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org> Reviewed-by: Gaurav Shah <gauravsh@chromium.org>
2011-08-29CHROMIUM: ARM: tegra: Don't run 'regen_all' in secure boot case.Doug Anderson
This requires 'bootargs' to be correct by default, so I did a little bit of refactoring of the way regen_all works to account for that. After this CL lands and is marked as stable, I'll change the FDT from 'run secure_boot' to just 'vboot_twostop'. That will mean that we're not _running_ any commands from the environment in the vboot case. BUG=chromium-os:17940 TEST=Saw the legacy boot worked; saw that vboot worked. Change-Id: I966c3f215beef5d9a1e47fa483a89f0ec42b8914 Reviewed-on: http://gerrit.chromium.org/gerrit/4448 Tested-by: Doug Anderson <dianders@chromium.org> Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
2011-08-29CHROMIUM: ARM: tegra: Remove the 'video=' kernel command line parameter.Doug Anderson
BUG=chromium-os:17923 TEST=Booted. Change-Id: I837063bc6458d5ad04433d0fcdab6e85369a53bd Reviewed-on: http://gerrit.chromium.org/gerrit/4445 Tested-by: Doug Anderson <dianders@chromium.org> Reviewed-by: Olof Johansson <olofj@chromium.org>
2011-08-29Cleaned up the environment variables in u-boot quite a bit.Doug Anderson
This makes the environment variables roughly match changes I previously made for 'legacy' in u-boot-config. Summary of changes: * No longer undefine the BOOTCOMMAND. While we don't use it in our non-legacy "image.bin" file (we override with the FDT), it still seems like it doesn't hurt to have it in the environment. ...and it's nice to be able to update the "bootcmd" in the legacy_image.bin. * Organized enviornment variables in tegra2_common and added comments; for example: all netboot related commands are now grouped together. * Got rid of hardcoded 172.22.72.144 value for TFTP/NFS server. Now defaults to 0.0.0.0 which disables TFTP/NFS. * Properly reads the boot script in partition 12 to do A/B switch of kernels. Note that the script in partition 12 should be cleaned up a little (separate CL) but what's there will work. * Made all netboot things conditional on both ethernet and non-zero IP address. * Added support for initrd booting. * Removed setting of "smpflag" to "smp", since nothing used it. NOTE: A future CL needs to be made to change chromeos-bootimage to reference the "secure_boot" command and to not override the bootcommand for legacy boot. BUG=chromium-os:17774 TEST=Put image on USB stick and saw boot from sda TEST=Put image on MMC1 and saw boot from MMC1 TEST=Installed image onto internal and saw boot form MMC0. TEST=Specified just 'tftpserverip' and saw initrd boot. TEST=Specified both 'tftpserverip' and nfsserverip' and saw nfs boot. TEST=Flashed non-legacy image and saw secure boot. Change-Id: Icacf0f1b57e971d1b86aab5ab72cd7ca4e4cf7e5 Reviewed-on: http://gerrit.chromium.org/gerrit/4350 Tested-by: Doug Anderson <dianders@chromium.org> Reviewed-by: Nick Sanders <nsanders@chromium.org> Reviewed-by: Anton Staaf <robotboy@chromium.org> Reviewed-by: Olof Johansson <olofj@chromium.org>
2011-08-29CHROMIUM: Change root to RO when legacy firmware boot.Tom Wai-Hong Tam
Since marked it as RW, kernel complains mount failed. Error messages like: [ 4.420377] GPT:1011746 != 7959551 [ 4.420405] GPT:Alternate GPT header not at the end of the disk. [ 4.420439] GPT:1011746 != 7959551 [ 4.420462] GPT: Use GNU Parted to correct GPT errors. [ 4.420727] mmcblk1: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 [ 4.455644] EXT3-fs (mmcblk0p3): error: couldn't mount RDWR because of unsupported optional features (ff000000) [ 4.497280] EXT2-fs (mmcblk0p3): error: couldn't mount RDWR because of unsupported optional features (ff000000) BUG=none TEST=boot legacy firmware to MMC disk success Change-Id: I876b25e33e4449b4f330a342cf69a48d88b5ff7f Reviewed-on: http://gerrit.chromium.org/gerrit/3673 Reviewed-by: Rong Chang <rongchang@chromium.org> Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
2011-08-29config: tegra: Display board name on console laterSimon Glass
Change-Id: Id23435986d3ce8eb7b28932f116e718280ae144e Reviewed-on: http://gerrit.chromium.org/gerrit/3502 Reviewed-by: Anton Staaf <robotboy@chromium.org> Tested-by: Simon Glass <sjg@chromium.org>
2011-08-29fdt: Add DEV_TREE_SEPARATE to provide an fdt separate from imageSimon Glass
This adds support for an FDT to be concatenated to the u-boot-bin binary. This is located at run-time by U-Boot. BUG=chromium-os:11623 TEST=Either emerge with http://gerrit.chromium.org/gerrit/2961 or build manually: make ... DEV_TREE_SEPARATE=true and check that u-boot.dtb is built. Change-Id: I7c8b1315d721bc957ef3fd07f167d86345868036 Reviewed-on: http://gerrit.chromium.org/gerrit/2962 Reviewed-by: Simon Glass <sjg@chromium.org> Tested-by: Simon Glass <sjg@chromium.org>
2011-08-29config: Increase maximum command arguments to 32Simon Glass
The default of 16 arguments is not enough to support verified boot and the code of increasing this is small. BUG=chromium-os:16508 TEST=build and do onestop boot Change-Id: I86d82c6583b28b540213acb3d8bc3ce60fd73057 Reviewed-on: http://gerrit.chromium.org/gerrit/3022 Reviewed-by: Che-Liang Chiou <clchiou@chromium.org> Tested-by: Simon Glass <sjg@chromium.org>
2011-08-29Modify seaboard configs to allow fdt based startup.Vadim Bendebury
These modifications are necessary to allow the u-boot to bring up ARM targets using the FDT (the flat device tree) as the means of communicating platform's hardware details to the kernel. As of this change, in addition to previously recognized kernel formats (particularly, uImage) the u-boot also accepts a so called FIT image. See doc/uImage.FIT/howto.txt for more information about the FIT image format. As a result, there are now three ways to boot up a kernel: 1. bootm <uImage addr> 2. bootm <uImage addr> - <device tree addr> 3. bootm <FIT image addr> 1. This is the legacy mode which has been using so far. On startup u-boot unpacks the uImage, and passes control to the kernel with the relocation start address, machine ID and pointer to the kernel command line as the three parameters. 2. This is a device tree mode using two separate images - the same uImage and the device tree blob. The '-' in the middle is used to indicate that there is no initrd. The u-boot relocates the device tree into the allotted window, modifies its contents to include target hardware specific information (memory size, clock frequencies, initrd location, command line, etc., etc.) and then invokes the kernel passing the pointer to the device tree as the third parameter instead of the kernel command line. The kernel startup code can tell that the third parameter is the device tree by checking for the appropriate device tree header. 3. In this case the zImage (which is used to create the uImage) and the device tree are combined in another device tree structure, the FIT image. The u-boot recognizes this by detecting the same device tree header pattern in the base of the image. Then it separates the kernel and the kernel device tree, places them in memory and continues as in case 2 above. BUG=chromium-os:16665 TEST=manual Reboot kaen, stop it at the u-boot prompt Prepare networking as follows: Tegra2 # usb start; dhcp; Try booting up the kernel using three different commands: tftpboot ${loadaddr} 172.22.73.75:/tftpboot/vbendeb/uImage; bootm tftpboot ${loadaddr} 172.22.73.75:/tftpboot/vbendeb/uImage; \ tftpboot 0x1300000 172.22.73.75:/tftpboot/vbendeb/kaen.dtb; \ boom ${loadaddr} - 0x1300000 tftpboot ${loadaddr} 172.22.73.75:/tftpboot/vbendeb/itsImage; bootm when booted using method 1 the /proc/device tree directory on the target is empty, when booted using the other two methods the /proc/device-tree directory contains the device tree passed in by u-boot. Change-Id: I2cdcc14170f7873c29844811e15c23a729142beb Reviewed-on: http://gerrit.chromium.org/gerrit/2922 Reviewed-by: Simon Glass <sjg@chromium.org> Tested-by: Vadim Bendebury <vbendeb@chromium.org>
2011-08-29config: Add dev_extras as a developer convenienceSimon Glass
Often it is required to add additional arguments to the bootargs. This makes it easier. BUG=chromium-os:11623 TEST=setenv devextras something; saveenv; reset; check that Linux boots with the extra args. Change-Id: Id6d2dbb7c9375b43b0f8bcc4fbbc59341cc6f040 Reviewed-on: http://gerrit.chromium.org/gerrit/2811 Reviewed-by: Simon Glass <sjg@chromium.org> Tested-by: Simon Glass <sjg@chromium.org>
2011-08-29config: Tidy up formating of config optionsSimon Glass
BUG=chromium-os:11623 TEST=build and boot on Seaboard Change-Id: I5ed3a4cb01d36a7e6bda597549817c79d9ca5d8c Reviewed-on: http://gerrit.chromium.org/gerrit/2810 Reviewed-by: Simon Glass <sjg@chromium.org> Tested-by: Simon Glass <sjg@chromium.org>
2011-08-29Move CONFIG_BOARD_EARLY_INIT_F to commonSimon Glass
This is required for all Tegra2 boards at present so it might as well be common. BUG=chromium-os:11623 TEST=build and boot on Seaboard Change-Id: I72b83cd5322842dfea7598925dab9abf608daac2 Reviewed-on: http://gerrit.chromium.org/gerrit/2805 Tested-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Warren <twarren@nvidia.com>
2011-08-29Derive board name and machine ID from the device tree.Vadim Bendebury
The board device ID needs to be passed to the kernel for proper initialization of the machine (until FDT is deployed for that). The device ID is picked based on the board name in the u-boot device tree. BUG=chromium-os:834 TEST=manual Tested combined with the rest of the patches in this set. Change-Id: Ifb9395196d13e96d6616ec61ae1e6fc6bd300ab6 Signed-off-by: Vadim Bendebury <vbendeb@chromium.org> Reviewed-on: http://gerrit.chromium.org/gerrit/2773 Reviewed-by: Simon Glass <sjg@chromium.org>
2011-08-29tegra2: enable warmboot code to support LP0Yen Lin
BUG=None TEST=Boot to kernel, suspend to LP0 then resume, and repeat Change-Id: Ic2a3cd455899e764c2d14026d86b321d0f84fbc2 Reviewed-on: http://gerrit.chromium.org/gerrit/2505 Tested-by: Yen Lin <yelin@nvidia.com> Reviewed-by: Jimmy Zhang <jimmzhang@nvidia.com>
2011-08-29arm: Tegra2: add env vars for mmc bootTom Warren
This adds the commands required to boot from mmc 0 on Seaboard. BUG=none TEST=booted older ChromiumOS from eMMC on Seaboard Signed-off-by: Tom Warren <twarren@nvidia.com> Change-Id: I21d0a0fe1c774c0bcd07fc4394771d4ed73332a0 Reviewed-on: http://gerrit.chromium.org/gerrit/2396
2011-08-29tegra2: add env vars for USB bootSimon Glass
This adds required commands to support booting a kernel from partition 3 on a USB stick. BUG=chromium-os:11623 TEST=insert USB stick with image and remove other USB devices env default -f; saveenv; reset watch it boot from USB Change-Id: I15234c8ce355ada0c1c45546845e8c6f0cdcb48e Reviewed-on: http://gerrit.chromium.org/gerrit/2404 Tested-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Warren <twarren@nvidia.com>
2011-08-29tegra2: Make cache write-through for LCD frame bufferSimon Glass
We want the display to be uncached, or use a write-through cache. Preliminary testing shows a very small advantage for write-through so this has been chosen. We can adjust later if needed. BUG=chromium-os:14082 TEST=build and boot on Seaboard, see that LCD updates properly now Change-Id: I3ca076f0c1c5bc15f0965f1b7b595db9a5e5828c Reviewed-on: http://gerrit.chromium.org/gerrit/2241 Reviewed-by: Simon Glass <sjg@chromium.org> Tested-by: Simon Glass <sjg@chromium.org>
2011-08-29Tegra2: Move CACHE_LINE_SIZE to common config fileAnton Staaf
The cache line size doesn't change from board to board, so it should be in the tegra2-common.h config file. BUG=chromium-os:16317 TEST=Build and boot U-Boot on Seaboard Change-Id: Ic9a9012eab0a01fc928ac824316dddb7376556ca Reviewed-on: http://gerrit.chromium.org/gerrit/2324 Reviewed-by: Tom Warren <twarren@nvidia.com> Tested-by: Anton Staaf <robotboy@chromium.org>
2011-08-29tegra2: config: Enable LCDSimon Glass
This enables an LCD display on Seaboard BUG=chromium-os:13228 TEST=Build, boot on Seaboard, see that LCD works Change-Id: Idd070c9a45f58082029e0f8d21ba4e0a877bdf65 Reviewed-on: http://gerrit.chromium.org/gerrit/1766 Tested-by: Simon Glass <sjg@chromium.org> Reviewed-by: Anton Staaf <robotboy@chromium.org>
2011-08-29tegra2: config: Fix mem= optionSimon Glass
This incorrectly had a space after mem= in the kernel command line. BUG=chromium-os:14082 TEST=build U-Boot Change-Id: Ib75d37b0fe691f6874b9428f22a21f3c1b077547 Reviewed-on: http://gerrit.chromium.org/gerrit/2242 Reviewed-by: Simon Glass <sjg@chromium.org> Tested-by: Simon Glass <sjg@chromium.org>
2011-08-29config: tegra2: Enable silent consoleSimon Glass
This enables silent console - if FDT is used it will be controlled from the FDT blob. BUG=chromium-os:11623 TEST=build and boot U-Boot on Seaboard Change-Id: I09b9abf51faa99788ac1b235e74620772a96fc17 Reviewed-on: http://gerrit.chromium.org/gerrit/964 Tested-by: Simon Glass <sjg@chromium.org> Reviewed-by: Doug Anderson <dianders@chromium.org>
2011-08-24Tegra2: Enable keyboard multiplexing.Rakesh Iyer
Multiplex tegra keyboard and serial to standard input for seaboard configs. Move tegra keyboard enable out of CONFIG_OF_CONTROL. BUG=None TEST=Multiplexing works fine on Seaboard. Change-Id: Idcf9a6a45f06b43ef0a4007bc992159634001e7c Signed-off-by: Rakesh Iyer <riyer@nvidia.com> Reviewed-on: http://gerrit.chromium.org/gerrit/1974 Reviewed-by: Tom Warren <twarren@nvidia.com> Reviewed-by: Simon Glass <sjg@chromium.org>
2011-08-24fdt: Seaboard config changes to enable serial controlSimon Glass
These config changes enable a console serial port under FDT control, and tidy up a few things in the config files. BUG=chromium-os:11623 TEST=build and boot U-Boot on Seaboard Change-Id: Id4f1b37939a82c4500760271b4006e662572d736 Reviewed-on: http://gerrit.chromium.org/gerrit/960 Reviewed-by: Doug Anderson <dianders@chromium.org> Tested-by: Simon Glass <sjg@chromium.org>
2011-08-24fdt: config: enable device tree support on SeaboardSimon Glass
This adds a temporary option CONFIG_OF_NO_KERNEL to indicate that we don't want to pass the FDT to the kernel. That is the normal behavior but we are not ready yet. BUG=chromium-os:11623 TEST=build and boot U-Boot on Seaboard Change-Id: Id7cf508e1ba68d043a5a8a2beaf716bb8f579b73 Reviewed-on: http://gerrit.chromium.org/gerrit/623 Tested-by: Simon Glass <sjg@chromium.org> Reviewed-by: Anton Staaf <robotboy@chromium.org>
2011-08-24arm: tegra2: Remove unneeded config optionsSimon Glass
CONFIG_ENABLE_CORTEXA9 and CONFIG_USB_CONTROLLER_INSTANCES are not needed, so remove them. BUG=chromium-os:13875 TEST=Boot U-Boot on Seaboard and run kernel Change-Id: I991b413e95448efcce1829dc49ce4486a30615c0 Reviewed-on: http://gerrit.chromium.org/gerrit/640 Tested-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Warren <twarren@nvidia.com> Reviewed-by: Simon Glass <sjg@chromium.org>
2011-08-24arm: tegra2: Use arch_cpu_init() to fire up Cortex-A9Simon Glass
We use board_early_init_f() for this but it is not really board init. Move to arch_cpu_init() instead. BUG=chromium-os:13228 TEST=Boot on Seaboard Change-Id: I36b0342700b19e073f4331cb1910c9d102d8b43b Reviewed-on: http://gerrit.chromium.org/gerrit/612 Tested-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Warren <twarren@nvidia.com> Reviewed-by: Anton Staaf <robotboy@chromium.org>
2011-08-24CHROMIUMOS: config: Move to zero delay for U-Boot bootSimon Glass
Now that SPI/UART is fixed pretty well, we can move to a zero boot delay. Hold down a key (e.g. space) before reset to interrupt boot, or use: setenv bootdelay 2 to increase the boot delay to 2 seconds for development. This speeds up the normal boot by 2 seconds. BUG=chromium-os:13228 TEST=Try U-Boot on Seaboard, check it doesn't wait for a boot, but it can be interrupted by holding down a key before reset. Change-Id: I8c433761bd977f750cecd844976574f340c54988 Reviewed-on: http://gerrit.chromium.org/gerrit/400 Reviewed-by: Simon Glass <sjg@chromium.org> Tested-by: Simon Glass <sjg@chromium.org>
2011-08-24No retry for USB storage to speed up the resume time.Tom Wai-Hong Tam
In the scenario, a user inserts a USB storage and boots to recovery mode, we required the user to plug the USB out first. However, in the meantime that the system is scanning the USB, the user plugs it out. It may need ~50sec to resume because there are many retry there. This change makes it no retry such that it only takes <1sec to resume. R=clchiou@chromium.org,sjg@chromium.org BUG=chromium-os:10500 TEST=emerge-tegra2_seaboard chromeos-u-boot-next successfully. When the system is scanning the USB storage, plug the USB out. It takes <1sec to resume. Review URL: http://codereview.chromium.org/6685083 Change-Id: I7d002a879bc8f93ccc354b5fc4a28b55a88276d1 Reviewed-on: http://gerrit.chromium.org/gerrit/397 Reviewed-by: Simon Glass <sjg@chromium.org> Tested-by: Simon Glass <sjg@chromium.org>
2011-08-24Add tftp speed indicationSimon Glass
This prints a tftp speed indication after the download completes. This is the 3.6 MiB/s indicator below. Tegra2 (SeaBoard) # tftp ... Using asx0 device TFTP from server 172.22.72.144; our IP address is 172.22.73.81 Filename '/tftpboot/uImage-user-seaboard-1'. Load address: 0x408000 Loading: ################################################# 3.6 MiB/s done BUG=chromium-os:13228 TEST=Boot on Seaboard, make sure message appears. Use 'time tftp ...' to make sure that speed reported is approximately right. Change-Id: I5e96e2ef6aa196a6fd8486f2dae0fe11f7464f20 Reviewed-on: http://gerrit.chromium.org/gerrit/225 Reviewed-by: Simon Glass <sjg@chromium.org> Tested-by: Simon Glass <sjg@chromium.org>
2011-08-24Enable time commandSimon Glass
BUG=chromium-os:13228 TEST=time usb start see that timing is produced Tegra2 (SeaBoard) # time usb start (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 3 USB Device(s) found scanning bus for storage devices... 0 Storage Device(s) found scanning bus for ethernet devices... 1 Ethernet Device(s) found time: 2.708 seconds, 2708 ticks Tegra2 (SeaBoard) # Change-Id: I93c53d4291ae4e6a97bdccb8250fb171bdb52cbf Reviewed-on: http://gerrit.chromium.org/gerrit/218 Reviewed-by: Simon Glass <sjg@chromium.org> Tested-by: Simon Glass <sjg@chromium.org>
2011-08-24Add microsecond boot time measurementSimon Glass
This defines the basics of a new boot time measurement feature. This allows logging of very accurate time measurements as the boot proceeds, by using an available microsecond counter. To enable the feature, define CONFIG_BOOTSTAGE in your board config file. Also available is CONFIG_BOOTSTAGE_REPORT which will cause a report to be printed just before handing off to the OS. BUG=chromium-os:13875 TEST=build and boot, check that progress is reported before running Linux: Timer summary in microseconds: Mark Elapsed Stage 0 0 awake 2,181,078 2,181,078 usb_start 11,861,817 9,680,739 bootp_start 11,884,610 22,793 bootp_stop 11,884,689 79 tftp start 15,271,536 3,386,847 tftp done 15,271,568 32 bootm_start 15,406,551 134,983 start_kernel Change-Id: I71b89c8402dc5dec75e68333bd24a6bab7500a1b Reviewed-on: http://gerrit.chromium.org/gerrit/197 Reviewed-by: Simon Glass <sjg@chromium.org> Tested-by: Simon Glass <sjg@chromium.org>
2011-08-24Enable SPI environment on SeaboardSimon Glass
This uses the SPI flash on Seaboard to store a 4KB environment. Change-Id: I9378cbe14b4b87ec31cab2f8d96868f371ef2a2d Reviewed-on: http://gerrit.chromium.org/gerrit/192 Tested-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Warren <twarren@nvidia.com> Reviewed-by: Simon Glass <sjg@chromium.org>
2011-08-24Tegra2: Enable data cacheSimon Glass
This plumbs in support for the Cortex A9's data cache. Since armv7 instructions are used we need to ensure that none of these appear in the instruction stream executed by the ARM7TDMI. BUG=chromium-os:12253 TEST=build and boot U-Boot on Seaboard, check that it makes it to Linux Tegra2 (SeaBoard) # dcache Data (writethrough) Cache is ON Tegra2 (SeaBoard) # Change-Id: I91e6ef847abcb821dcaf482faa31d82b98ba93b8 Reviewed-on: http://gerrit.chromium.org/gerrit/198 Tested-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Warren <twarren@nvidia.com> Reviewed-by: Simon Glass <sjg@chromium.org>
2011-08-24armv7: replace CONFIG_L2_OFF with CONFIG_SYS_NO_L2CACHEAneesh V
replace all occurences of CONFIG_L2_OFF with a more appropriate CONFIG_SYS_NO_L2CACHE CONFIG_SYS_NO_L2CACHE has been chosen to be in line with CONFIG_SYS_NO_ICACHE and CONFIG_SYS_NO_DCACHE Signed-off-by: Aneesh V <aneesh@ti.com>
2011-08-24Tegra2: config: enable network bootingSimon Glass
This enables networking booting using a USB dongle plugged into the side seaboard port. BUG=chromium-os:13875 TEST=build and boot, check that network boot completes Change-Id: I673bbed5a58ce7981590e49157cbf570129ca1a0 Review URL: http://codereview.chromium.org/6880194
generated by cgit v1.2.3 (git 2.0.4) at 2024-07-13 02:05:23 +0000