August 2015 - U-Boot

[U-Boot] Adding new command using existing commands
by Ajanta Sarma 21 Aug '15

21 Aug '15

Hi, I am trying to add one command in U-Boot using set of existing commands. e.g. adding one command for fusing flash with a newly compiled file. new command - "fuse_uboot" used commands: 1. ping (do_ping() call) 2. tftp (do_tftpb() call) 3. protect off (do_protect() call) 4. erase (do_flerase() call) 5. cp.b (do_cp_mem() call) 6. protect on (do_protect() call) 7. reset (do_reset) I am copying a section of my code: addition in common/cmd_mem.c: extern int ping_extern(cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[]); extern void protect_extern(cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[]); extern int erase_extern(cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[]); static int do_mem_cp(cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[]); #if defined(FUSE_UBOOT_FILE) static int do_fuse_uboot(cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[]) { int ret = 0, ret1 = 0, ret2 = 1; unsigned int f_size = 0; char *ping_argv[] = {"ping", NULL, NULL, NULL}; char *tftp_argv[] = {"tftp", NULL, NULL, NULL}; char *protect_argv[] = {"protect", NULL, NULL, NULL}; char *erase_argv[] = {"erase", NULL, NULL, NULL}; char *cp_argv[] = {"cp.b", NULL, NULL, NULL}; printf("Fusing U-Boot\n"); ping_argv[1] = getenv("serverip"); ret = ping_extern(cmdtp, 0, 2, ping_argv); if (ret == 0) { tftp_argv[1] = "10000"; tftp_argv[2] = "uboot_new.bin"; ret1 = (do_tftpb(cmdtp, 0, 3, tftp_argv)); f_size = getenv("filesize"); if (ret1 == 0) { protect_argv[1] = "off"; protect_argv[2] = "1:0-10"; protect_extern(cmdtp, 0, 3, protect_argv); erase_argv[1] = "1:0-10"; ret2 = erase_extern(cmdtp, 0, 2, erase_argv); if (ret2 == 0) { cp_argv[1] = "10000"; cp_argv[2] = "fe000000"; cp_argv[3] = f_size; do_mem_cp(cmdtp, 0, 4, cp_argv); protect_argv[1] = "on"; protect_argv[2] = "1:0-10"; protect_extern(cmdtp, 0, 3, protect_argv); do_reset(NULL, 0, 0, NULL); } else printf("Flash not erased : ERROR %d\n", ret2); } else printf("FILE NOT FOUND\n"); } else printf("PING FAILED : CHECK NETWORK PARAMETERS !!!\n"); return 0; } U_BOOT_CMD( fuse_boot, 1, 0, do_fuse_uboot, "fuse uboot file from your TFTP server", "" ); #endif addition in common/cmd_flash.c: int erase_extern(cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[]) { int ret; ret = do_flerase(cmdtp, 0, 2, argv); return ret; } void protect_extern(cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[]) { do_protect(cmdtp, 0, 3, argv); } addition in common/cmd_net.c: int ping_extern(cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[]) { int ret; ret = do_ping(cmdtp, 0, 2, argv); return ret; } The problem I am facing: whenever I pass "1:0-10" as protect_argv[2], after calling protect_extern(), erase get only "1" as erase_argv[1]. Same goes with every values, if arguments are same for both the call second value gets corrupted. please help me out !!! Thanks in advance, Ajanta Regards, अजंता शर्मा रिसर्च इंजिनियर प्लॅटफॉर्म सॉफ्टवेर ग्रूप सी-डॉट, बेंगालुरू Ajanta Sarma Research Engineer Platform Software Group C-DOT Bangalore Contact - 08025119895 Mobile - 9739778513 Disclaimer: ---------- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If

1 0

[U-Boot] Kernel bootparam injection
by Christian Litjes 21 Aug '15

21 Aug '15

Dear Denx, I've been working on an embedded system which starts over TFTP with an NFS rootfs. During the development I noticed that it's possible to inject bootparams in to the dhcp messages. If a system boots from NFS and I provide the following path to the nfs share the extra bootparams will be executed aswell. option root-path "/media/share/nfs/,tcp ro" The ro parameter is put in to the kernel parameter as well and executed. I'm using this hack currently on our own system into our advantage to override the rw with ro in the kernel command line without the need of recompiling uboot. I'm going to plug this hole because it's a security risk for our product. I've looked in the current uboot version and this is still a possibility. My suggestion is to verify the options passed trough, these are separated by "," and ignore anything with a space inside the rootpath. If you agree this is an issue and have a suggestion for a solution. I will supply the patch we are currently using for our own product. Kind regards, Christian Litjes

1 0

[U-Boot] [PATCH v2] corvus, dfu: add dfu support
by Heiko Schocher 21 Aug '15

21 Aug '15

add support for DFU on the corvus board. Signed-off-by: Heiko Schocher <hs(a)denx.de> --- Changes in v2: - rebase to 0d339cf9a969f0c249713d3697e735184f1bd955 - fix changes introduced through commit: 01acd6abbdd5: usb: USB download gadget and functions config options coherent naming board/siemens/corvus/board.c | 21 +++++++++++++++++++++ include/configs/corvus.h | 29 +++++++++++++++++++++++++++-- 2 files changed, 48 insertions(+), 2 deletions(-) diff --git a/board/siemens/corvus/board.c b/board/siemens/corvus/board.c index f3f6dae..426d0cd 100644 --- a/board/siemens/corvus/board.c +++ b/board/siemens/corvus/board.c @@ -29,6 +29,10 @@ #include <netdev.h> #include <spi.h> +#ifdef CONFIG_USB_GADGET_ATMEL_USBA +#include <asm/arch/atmel_usba_udc.h> +#endif + DECLARE_GLOBAL_DATA_PTR; static void corvus_nand_hw_init(void) @@ -210,6 +214,19 @@ int board_early_init_f(void) return 0; } +#ifdef CONFIG_USB_GADGET_ATMEL_USBA +/* from ./arch/arm/mach-at91/armv7/sama5d3_devices.c */ +void at91_udp_hw_init(void) +{ + struct at91_pmc *pmc = (struct at91_pmc *)ATMEL_BASE_PMC; + + /* Enable UPLL clock */ + writel(AT91_PMC_UPLLEN | AT91_PMC_BIASEN, &pmc->uckr); + /* Enable UDPHS clock */ + at91_periph_clk_enable(ATMEL_ID_UDPHS); +} +#endif + int board_init(void) { /* address of boot parameters */ @@ -230,6 +247,10 @@ int board_init(void) #ifdef CONFIG_CMD_USB taurus_usb_hw_init(); #endif +#ifdef CONFIG_USB_GADGET_ATMEL_USBA + at91_udp_hw_init(); + usba_udc_probe(&pdata); +#endif return 0; } diff --git a/include/configs/corvus.h b/include/configs/corvus.h index 2d2f3c1..2bad20f 100644 --- a/include/configs/corvus.h +++ b/include/configs/corvus.h @@ -113,7 +113,32 @@ #define CONFIG_DOS_PARTITION #define CONFIG_USB_STORAGE -#define CONFIG_SYS_LOAD_ADDR 0x72000000 /* load address */ +/* USB DFU support */ +#define CONFIG_CMD_MTDPARTS +#define CONFIG_MTD_DEVICE +#define CONFIG_MTD_PARTITIONS + +#define CONFIG_USB_GADGET +#define CONFIG_USB_GADGET_DUALSPEED +#define CONFIG_USB_GADGET_ATMEL_USBA + +/* DFU class support */ +#define CONFIG_CMD_DFU +#define CONFIG_USB_FUNCTION_DFU +#define CONFIG_DFU_NAND +#define CONFIG_USB_GADGET_DOWNLOAD +#define CONFIG_USB_GADGET_VBUS_DRAW 2 +#define CONFIG_SYS_DFU_DATA_BUF_SIZE (1 << 20) +#define DFU_MANIFEST_POLL_TIMEOUT 25000 + +/* USB DFU IDs */ +#define CONFIG_G_DNL_VENDOR_NUM 0x0908 +#define CONFIG_G_DNL_PRODUCT_NUM 0x02d2 +#define CONFIG_G_DNL_MANUFACTURER "Siemens AG" + +#define CONFIG_SYS_CACHELINE_SIZE 0x2000 +/* fuer was das ? */ +#define CONFIG_SYS_LOAD_ADDR ATMEL_BASE_CS6 /* bootstrap + u-boot + env in nandflash */ #define CONFIG_ENV_IS_IN_NAND @@ -146,7 +171,7 @@ * Size of malloc() pool */ #define CONFIG_SYS_MALLOC_LEN ROUND(3 * CONFIG_ENV_SIZE + \ - 128*1024, 0x1000) + 4*1024*1024, 0x1000) /* Defines for SPL */ #define CONFIG_SPL_FRAMEWORK #define CONFIG_SPL_TEXT_BASE 0x300000 -- 2.1.0

2 2

[U-Boot] [PATCH v3] dfu:tests: Modify dfu_gadget_test.sh to accept USB device vendor:product ID
by Lukasz Majewski 21 Aug '15

21 Aug '15

dfu-util allows filtering on USB device vendor:product ID by using the -d flag (-d 0451:d022). Such option is very handy when many DFU devices are connected to a single host PC. This commit allows testing when above situation emerges. Signed-off-by: Lukasz Majewski <l.majewski(a)majess.pl> Reviewed-by: Simon Glass <sjg(a)chromium.org> Tested-by: Lukasz Majewski <l.majewski(a)majess.pl> Test HW - AM335x Beagle Bone Black NOTE: Max size of file to transfer: 2MiB --- Changes for v2: - Change major:minor to USB's Vendor:Product ID Changes for v3: - One more correction --- test/dfu/README | 9 ++++++++- test/dfu/dfu_gadget_test.sh | 18 +++++++++++------- 2 files changed, 19 insertions(+), 8 deletions(-) diff --git a/test/dfu/README b/test/dfu/README index 5176aba..8925a91 100644 --- a/test/dfu/README +++ b/test/dfu/README @@ -26,12 +26,19 @@ Example usage: setenv dfu_alt_info dfu_test.bin fat 0 6\;dfudummy.bin fat 0 6 dfu 0 mmc 0 2. On the host: - test/dfu/dfu_gadget_test.sh X Y [test file name] + test/dfu/dfu_gadget_test.sh X Y [test file name] [usb device vendor:product] e.g. test/dfu/dfu_gadget_test.sh 0 1 or e.g. test/dfu/dfu_gadget_test.sh 0 1 ./dat_960.img + or + e.g. test/dfu/dfu_gadget_test.sh 0 1 0451:d022 + or + e.g. test/dfu/dfu_gadget_test.sh 0 1 ./dat_960.img 0451:d022 ... where X and Y are dfu_test.bin's and dfudummy.bin's alt setting numbers. They can be obtained from dfu-util -l or $dfu_alt_info. It is also possible to pass optional [test file name] to force the script to test one particular file. +If many DFU devices are connected, it may be useful to filter on USB +vendor/product ID (0451:d022). +One can get them by running "lsusb" command on a host PC. diff --git a/test/dfu/dfu_gadget_test.sh b/test/dfu/dfu_gadget_test.sh index 2f5b7db..9c79422 100755 --- a/test/dfu/dfu_gadget_test.sh +++ b/test/dfu/dfu_gadget_test.sh @@ -45,18 +45,18 @@ dfu_test_file () { printf "$COLOUR_GREEN ========================================================================================= $COLOUR_DEFAULT\n" printf "File:$COLOUR_GREEN %s $COLOUR_DEFAULT\n" $1 - dfu-util -D $1 -a $TARGET_ALT_SETTING >> $LOG_FILE 2>&1 || die $? + dfu-util $USB_DEV -D $1 -a $TARGET_ALT_SETTING >> $LOG_FILE 2>&1 || die $? echo -n "TX: " calculate_md5sum $1 MD5_TX=$MD5SUM - dfu-util -D ${DIR}/dfudummy.bin -a $TARGET_ALT_SETTING_B >> $LOG_FILE 2>&1 || die $? + dfu-util $USB_DEV -D ${DIR}/dfudummy.bin -a $TARGET_ALT_SETTING_B >> $LOG_FILE 2>&1 || die $? N_FILE=$DIR$RCV_DIR${1:2}"_rcv" - dfu-util -U $N_FILE -a $TARGET_ALT_SETTING >> $LOG_FILE 2>&1 || die $? + dfu-util $USB_DEV -U $N_FILE -a $TARGET_ALT_SETTING >> $LOG_FILE 2>&1 || die $? echo -n "RX: " calculate_md5sum $N_FILE @@ -89,13 +89,17 @@ fi TARGET_ALT_SETTING=$1 TARGET_ALT_SETTING_B=$2 -if [ -n "$3" ] +file=$3 +[[ $3 == *':'* ]] && USB_DEV="-d $3" && file="" +[ $# -eq 4 ] && USB_DEV="-d $4" + +if [ -n "$file" ] then - dfu_test_file $3 + dfu_test_file $file else - for file in $DIR*.$SUFFIX + for f in $DIR*.$SUFFIX do - dfu_test_file $file + dfu_test_file $f done fi -- 2.1.4

2 2

[U-Boot] [PATCH] net: Return -1 when ctrl+c is pressed
by Michal Simek 21 Aug '15

21 Aug '15

Current behavior is that if CTRL+C is pressed command returns 0 that was successful which is not correct behavior. The easiest test case is "tftpboot 80000 uImage && echo yes" and press CTRL+C. Then the second command is called which is incorrect. Error log: zynq-uboot> tftpb 80000 uImage && echo yes Gem.e000b000:7 is connected to Gem.e000b000. Reconnecting to Gem.e000b000 Gem.e000b000 Waiting for PHY auto negotiation to complete....... done Using Gem.e000b000 device TFTP from server 192.168.0.102; our IP address is 192.168.0.101 Filename 'uImage'. Load address: 0x80000 Loading: ################ Abort yes zynq-uboot> This patch adds -1 return value when CTRL+C is pressed. Signed-off-by: Michal Simek <michal.simek(a)xilinx.com> --- Not sure if -1 is the right error code but I have parsed the code and it looks like that -1 is standard behavior for CTRL+C. But I am happy to change this behavior. --- net/net.c | 1 + 1 file changed, 1 insertion(+) diff --git a/net/net.c b/net/net.c index 67e0ad297cf5..738a0db8c2ba 100644 --- a/net/net.c +++ b/net/net.c @@ -565,6 +565,7 @@ restart: /* include a debug print as well incase the debug messages are directed to stderr */ debug_cond(DEBUG_INT_STATE, "--- net_loop Abort!\n"); + ret = -1; goto done; } -- 2.3.5

4 4

[U-Boot] [PATCH] arm: socfpga: Fix MAINTAINERS entry for CV/AV SoCDK
by Marek Vasut 21 Aug '15

21 Aug '15

Repair the maintainer entries so they match the current state of code. Signed-off-by: Marek Vasut <marex(a)denx.de> --- board/altera/arria5-socdk/MAINTAINERS | 11 +++-------- board/altera/cyclone5-socdk/MAINTAINERS | 2 +- 2 files changed, 4 insertions(+), 9 deletions(-) diff --git a/board/altera/arria5-socdk/MAINTAINERS b/board/altera/arria5-socdk/MAINTAINERS index 0482581..30f2477 100644 --- a/board/altera/arria5-socdk/MAINTAINERS +++ b/board/altera/arria5-socdk/MAINTAINERS @@ -2,11 +2,6 @@ SOCFPGA BOARD M: Dinh Nguyen <dinguyen(a)altera.com> M: Chin-Liang See <clsee(a)altera.com> S: Maintained -F: board/altera/socfpga/ -F: include/configs/socfpga_cyclone5.h -F: configs/socfpga_cyclone5_defconfig - -SOCRATES BOARD -M: Stefan Roese <sr(a)denx.de> -S: Maintained -F: configs/socfpga_socrates_defconfig +F: board/altera/arria5-socdk/ +F: include/configs/socfpga_arria5.h +F: configs/socfpga_arria5_defconfig diff --git a/board/altera/cyclone5-socdk/MAINTAINERS b/board/altera/cyclone5-socdk/MAINTAINERS index 0482581..f218ca4 100644 --- a/board/altera/cyclone5-socdk/MAINTAINERS +++ b/board/altera/cyclone5-socdk/MAINTAINERS @@ -2,7 +2,7 @@ SOCFPGA BOARD M: Dinh Nguyen <dinguyen(a)altera.com> M: Chin-Liang See <clsee(a)altera.com> S: Maintained -F: board/altera/socfpga/ +F: board/altera/cyclone5-socdk/ F: include/configs/socfpga_cyclone5.h F: configs/socfpga_cyclone5_defconfig -- 2.1.4

2 5

[U-Boot] [UBOOT PATCH v5 0/3] Add ACPI table support
by Saket Sinha 21 Aug '15

21 Aug '15

ACPI(Advanced Configuration and Power Interface), is a Power Management and configuration standard allowing the operating system to control the amount of power each device is given (allowing it to put certain devices on standby or power-off for example). It is also used to control and/or check thermal zones (temperature sensors, fan speeds, etc), battery levels, PCI IRQ routing, CPUs, NUMA domains and many other things. Changes in v5: - Incoporated Simon's review comments. Saket Sinha (3): x86: Generate a valid ACPI table x86: Add ACPI table support to QEMU x86: Add DSDT table for supporting ACPI on QEMU arch/x86/Kconfig | 9 + arch/x86/cpu/qemu/Makefile | 1 + arch/x86/cpu/qemu/acpi.c | 179 ++++++++++++++ arch/x86/cpu/qemu/acpi/cpu-hotplug.asl | 78 ++++++ arch/x86/cpu/qemu/acpi/dbug.asl | 26 ++ arch/x86/cpu/qemu/acpi/hpet.asl | 33 +++ arch/x86/cpu/qemu/acpi/isa.asl | 102 ++++++++ arch/x86/cpu/qemu/acpi/pci-crs.asl | 61 +++++ arch/x86/cpu/qemu/dsdt.asl | 414 +++++++++++++++++++++++++++++++ arch/x86/include/asm/acpi_table.h | 390 +++++++++++++++++++++++++++++ arch/x86/lib/Makefile | 1 + arch/x86/lib/acpi_table.c | 433 +++++++++++++++++++++++++++++++++ arch/x86/lib/tables.c | 5 + scripts/Makefile.lib | 11 + 14 files changed, 1743 insertions(+) create mode 100644 arch/x86/cpu/qemu/acpi.c create mode 100644 arch/x86/cpu/qemu/acpi/cpu-hotplug.asl create mode 100644 arch/x86/cpu/qemu/acpi/dbug.asl create mode 100644 arch/x86/cpu/qemu/acpi/hpet.asl create mode 100644 arch/x86/cpu/qemu/acpi/isa.asl create mode 100644 arch/x86/cpu/qemu/acpi/pci-crs.asl create mode 100644 arch/x86/cpu/qemu/dsdt.asl create mode 100644 arch/x86/include/asm/acpi_table.h create mode 100644 arch/x86/lib/acpi_table.c -- 2.1.4

2 15

[U-Boot] [PATCH v2 2/2] arm: socfpga: config: Remove hard-coded drvsel and smpsel
by Chin Liang See 21 Aug '15

21 Aug '15

Remove hard-coded SDMMC timing parameter drvsel and smplsel. This setting now will come from SDMMC calibration Signed-off-by: Chin Liang See <clsee(a)altera.com> Cc: Dinh Nguyen <dinguyen(a)opensource.altera.com> Cc: Pavel Machek <pavel(a)denx.de> Cc: Marek Vasut <marex(a)denx.de> Cc: Stefan Roese <sr(a)denx.de> --- Changes for v2 - Update the CC list --- include/configs/socfpga_common.h | 2 -- 1 files changed, 0 insertions(+), 2 deletions(-) diff --git a/include/configs/socfpga_common.h b/include/configs/socfpga_common.h index c64c7ed..1a070fd 100644 --- a/include/configs/socfpga_common.h +++ b/include/configs/socfpga_common.h @@ -155,8 +155,6 @@ #define CONFIG_DWMMC #define CONFIG_SOCFPGA_DWMMC #define CONFIG_SOCFPGA_DWMMC_FIFO_DEPTH 1024 -#define CONFIG_SOCFPGA_DWMMC_DRVSEL 3 -#define CONFIG_SOCFPGA_DWMMC_SMPSEL 0 /* FIXME */ /* using smaller max blk cnt to avoid flooding the limited stack we have */ #define CONFIG_SYS_MMC_MAX_BLK_COUNT 256 /* FIXME -- SPL only? */ -- 1.7.7.4

2 2

[U-Boot] [PATCH] ARM: tegra: replace V_PROMPT define with kconfig
by Stephen Warren 21 Aug '15

21 Aug '15

From: Stephen Warren <swarren(a)nvidia.com> Commit 181bd9dc61d2 "kconfig: add config option for shell prompt" replaced define V_PROMPT with Kconfig option SYS_PROMPT. This crossed with patches adding Tegra T210 boards. Migrate the boards to the new scheme. Signed-off-by: Stephen Warren <swarren(a)nvidia.com> --- configs/e2220-1170_defconfig | 1 + configs/p2371-0000_defconfig | 1 + configs/p2371-2180_defconfig | 1 + configs/p2571_defconfig | 1 + include/configs/e2220-1170.h | 1 - include/configs/p2371-0000.h | 1 - include/configs/p2371-2180.h | 1 - include/configs/p2571.h | 1 - 8 files changed, 4 insertions(+), 4 deletions(-) diff --git a/configs/e2220-1170_defconfig b/configs/e2220-1170_defconfig index 455e7892b5cb..e86715ae129f 100644 --- a/configs/e2220-1170_defconfig +++ b/configs/e2220-1170_defconfig @@ -15,3 +15,4 @@ CONFIG_SPI_FLASH=y CONFIG_USB=y CONFIG_DM_USB=y CONFIG_USE_PRIVATE_LIBGCC=y +CONFIG_SYS_PROMPT="Tegra210 (E2220-1170) # " diff --git a/configs/p2371-0000_defconfig b/configs/p2371-0000_defconfig index cd7d21fe3a4b..379747824394 100644 --- a/configs/p2371-0000_defconfig +++ b/configs/p2371-0000_defconfig @@ -15,3 +15,4 @@ CONFIG_SPI_FLASH=y CONFIG_USB=y CONFIG_DM_USB=y CONFIG_USE_PRIVATE_LIBGCC=y +CONFIG_SYS_PROMPT="Tegra210 (P2371-0000) # " diff --git a/configs/p2371-2180_defconfig b/configs/p2371-2180_defconfig index 83fde57a0c46..98448eed82dd 100644 --- a/configs/p2371-2180_defconfig +++ b/configs/p2371-2180_defconfig @@ -15,3 +15,4 @@ CONFIG_SPI_FLASH=y CONFIG_USB=y CONFIG_DM_USB=y CONFIG_USE_PRIVATE_LIBGCC=y +CONFIG_SYS_PROMPT="Tegra210 (P2371-2180) # " diff --git a/configs/p2571_defconfig b/configs/p2571_defconfig index 5fd2a54eb18e..7bcba51d8538 100644 --- a/configs/p2571_defconfig +++ b/configs/p2571_defconfig @@ -15,3 +15,4 @@ CONFIG_SPI_FLASH=y CONFIG_USB=y CONFIG_DM_USB=y CONFIG_USE_PRIVATE_LIBGCC=y +CONFIG_SYS_PROMPT="Tegra210 (P2571) # " diff --git a/include/configs/e2220-1170.h b/include/configs/e2220-1170.h index 47d491f05078..998a69aba106 100644 --- a/include/configs/e2220-1170.h +++ b/include/configs/e2220-1170.h @@ -13,7 +13,6 @@ #include "tegra210-common.h" /* High-level configuration options */ -#define V_PROMPT "Tegra210 (E2220-1170) # " #define CONFIG_TEGRA_BOARD_STRING "NVIDIA E2220-1170" /* Board-specific serial config */ diff --git a/include/configs/p2371-0000.h b/include/configs/p2371-0000.h index e190733357b5..f2a713d0bee2 100644 --- a/include/configs/p2371-0000.h +++ b/include/configs/p2371-0000.h @@ -13,7 +13,6 @@ #include "tegra210-common.h" /* High-level configuration options */ -#define V_PROMPT "Tegra210 (P2371-0000) # " #define CONFIG_TEGRA_BOARD_STRING "NVIDIA P2371-0000" /* Board-specific serial config */ diff --git a/include/configs/p2371-2180.h b/include/configs/p2371-2180.h index 378d5a905e93..f994a493fe61 100644 --- a/include/configs/p2371-2180.h +++ b/include/configs/p2371-2180.h @@ -13,7 +13,6 @@ #include "tegra210-common.h" /* High-level configuration options */ -#define V_PROMPT "Tegra210 (P2371-2180) # " #define CONFIG_TEGRA_BOARD_STRING "NVIDIA P2371-2180" /* Board-specific serial config */ diff --git a/include/configs/p2571.h b/include/configs/p2571.h index 87abee603dc1..c65d3e5fcbc1 100644 --- a/include/configs/p2571.h +++ b/include/configs/p2571.h @@ -13,7 +13,6 @@ #include "tegra210-common.h" /* High-level configuration options */ -#define V_PROMPT "Tegra210 (P2571) # " #define CONFIG_TEGRA_BOARD_STRING "NVIDIA P2571" /* Board-specific serial config */ -- 1.9.1

1 0

Re: [U-Boot] [PATCH 2/5] arm: tegra20: video: ifdef gate hard-coded ugly Tegra20 pin muxing
by Marcel Ziswiler 21 Aug '15

21 Aug '15

On 20 Aug 2015 22:04, Stephen Warren <swarren(a)wwwdotorg.org> wrote: > That option doesn't seem to exist, except in > arch/arm/include/asm/mach-types.h where I think it's the name of an > unrelated board. Do you mean CONFIG_TEGRA20, as defined by > arch/arm/mach-tegra/tegra20/Kconfig? No, I'm talking about T20 in general. Will fix it accordingly.

1 0