[U-Boot] [PATCH] ARM: Don't grab memory for LCD if FB address is defined

2011-03-03 Thread Minkyu Kang
If FB address is defined as specific address then don't grab memory for LCD

Signed-off-by: Minkyu Kang mk7.k...@samsung.com
---
 arch/arm/lib/board.c |4 
 1 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/arch/arm/lib/board.c b/arch/arm/lib/board.c
index c620d2c..5a4d2bd 100644
--- a/arch/arm/lib/board.c
+++ b/arch/arm/lib/board.c
@@ -356,9 +356,13 @@ void board_init_f (ulong bootflag)
 #endif /* CONFIG_VFD */
 
 #ifdef CONFIG_LCD
+#ifdef CONFIG_FB_ADDR
+   gd-fb_base = CONFIG_FB_ADDR;
+#else
/* reserve memory for LCD display (always full pages) */
addr = lcd_setmem (addr);
gd-fb_base = addr;
+#endif /* CONFIG_FB_ADDR */
 #endif /* CONFIG_LCD */
 
/*
-- 
1.7.1
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


[U-Boot] uboot for MIPS: need help to skip relocate uboot and start uboot from RAM

2011-03-03 Thread Pandurang Kale
Hello Everyone,

We have MIPS based development board and I am trying to get the uboot up and
running on it.
We have a primary bootloader which check for the valid mod-image stored on
the flash. This mod-image consist of header, uboot and linux kernel.
Depending on the recent, active and stable imagethe primary bootloader first
copies the uboot image. and later on we would copy the kernel image from
uboot.

But when primary bootloader copies the uboot image to the RAM and passes the
control to the uboot, uboot (MIPS version of start.S and
arch/mips/lib/borad.c) tries to relocate the
already copied image from RAM (the primary bootloader copied it to start of
the RAM+1MB address) to top of the RAM (0x87fc) region thinking that the
uboot image is stored in flash.

All I need to do is skip the uboot relocate code in MIPS version of uboot
startup as the primary bootloader has already relocated the uboot from Flash
to RAM and set up the stack pointer and other global data appropriately,
which it does after relocation.
I can see there is a switch for ARM processor, CONFIG_SKIP_RELOCATE_UBOOT,
which skips the relocation of uboot code and tries to run the uboot from
RAM. I
cannot see a similar switch implemented for MIPS and didnt find any related
thread anywhere in mailing list or on net.

Do we have similar ARM like switch to SKIP the RELOCATION? If not has anyone
done this before?

I would really appreciate if you can guide me to overcome this issue to run
the uboot cleanly skipping the relocation.

Thanks in advance,
Pandu
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] CONFIG_WATCHDOG on MPC85XX and QorIQ P1/P2

2011-03-03 Thread Tabi Timur-B04825
Felix Radensky wrote:
 Correct. It works fine in linux. I've even tried to port linux code that
 enables watchdog (booke_wdt.c/__booke_wdt_enable()) to u-boot,
 but was not successful. Watchdog never triggered, although I did
 not refresh it.

 I'd appreciate some advice on what may be different in u-boot
 vs. linux.

I don't know what to tell you.  I would need to try to make it myself in order 
to see what's going on.  Maybe you really didn't program TCR correctly.  Or 
maybe it is working, but the default behavior of U-Boot is to handle everything 
silently.

-- 
Timur Tabi
Linux kernel developer
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] CONFIG_WATCHDOG on MPC85XX and QorIQ P1/P2

2011-03-03 Thread Felix Radensky
Hi Timur,

On 03/03/2011 02:33 PM, Tabi Timur-B04825 wrote:
 Felix Radensky wrote:
 Correct. It works fine in linux. I've even tried to port linux code that
 enables watchdog (booke_wdt.c/__booke_wdt_enable()) to u-boot,
 but was not successful. Watchdog never triggered, although I did
 not refresh it.

 I'd appreciate some advice on what may be different in u-boot
 vs. linux.
 I don't know what to tell you.  I would need to try to make it myself in 
 order to see what's going on.  Maybe you really didn't program TCR correctly. 
  Or maybe it is working, but the default behavior of U-Boot is to handle 
 everything silently.

Thanks. I suspect u-boot WDT behaviour should be different from Linux.
Linux sets TCR_WIE bit to enable watchdog interrupt,  u-boot should not
do this and just reset the CPU on first time-out. The TCR values are 
identical
in u-boot and linux, except for TCR_WIE and TCR_DIE bits that are set 
in linux.

Except not setting TCI_WIE bit and setting WRC to 10b, is there 
anything else
that should be done to cause reset of first time-out ?

Felix.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] CONFIG_WATCHDOG on MPC85XX and QorIQ P1/P2

2011-03-03 Thread Tabi Timur-B04825
Felix Radensky wrote:

 Except not setting TCI_WIE bit and setting WRC to 10b, is there anything
 else
 that should be done to cause reset of first time-out ?

Like I said, I would need to debug it myself to know more, and I don't have the 
time for that.

-- 
Timur Tabi
Linux kernel developer
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


[U-Boot] p4080ds starts OS with MSR[EE]=1 and DEC armed?

2011-03-03 Thread Jimi Xenidis
I was surprised to find myself at the decrement interrupt when running my new 
stuff.
That is against ePAPR, right?
Does u-boot at least make sure that the DEC is set to some large value before 
it leaps at me?
I don't mind forcing EE=0 but I'd like to make sure I make it that far into the 
code :)
-JX

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [beagleboard] Re: [PATCH v3] omap3_beagle: enable the use of a plain text file named uEnv.txt instead of boot.scr

2011-03-03 Thread Jason Kridner
On Wed, Mar 2, 2011 at 6:48 PM, Robert Nelson robertcnel...@gmail.com wrote:
 On Wed, Mar 2, 2011 at 5:41 PM, Alexander Holler hol...@ahsoftware.de wrote:
 Hello Jason,

 Am 02.03.2011 21:26, schrieb Jason Kridner:

 For backwards compatibility the use of boot.scr is still supported.


 Sorry, but I think that line in the description should get removed too.

I'll submit a v4.



 So, just a thought..  Are you guys planning to push this same boot
 method to all the other omap devices that just finally got boot.scr
 boot support by default in u-boot?  It also seems's like it'll end up
 be the FAQ of the month for the beagleboard group.. ;)

Indeed it is likely to be FAQ of the month, especially if it lands in
the next software update that gets shipped with the board.  It is a
case, however, in which I like the answer--no more need to run
mkimage.  The conversion process of a boot.scr script (commands) to a
uEnv.txt file (variable setting) won't be exactly trivial, so that has
me a tiny bit concerned.  Still, most cases will be solved by a *much*
simpler uEnv.txt script and an overall simpler process.

I still see a need to use the USER button to go into some sort of
fall-back state to ignore this file and boot some sort of recovery
image.  Since that code isn't upstream yet, there is still going to be
some delta between upstream and what ships on the board--unless I can
somehow figure out an easy way to get a command added for the generic
gpio framework.


 Regards,

 --
 Robert Nelson
 http://www.rcn-ee.com/

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


[U-Boot] [PATCH v4] omap3_beagle: enable the use of a plain text file named uEnv.txt instead of boot.scr

2011-03-03 Thread Jason Kridner
From: Alexander Holler hol...@ahsoftware.de

Using the new env import command it is possible to use plain text files instead
of script-images. Plain text files are much easier to handle.

E.g. If your boot.scr contains the following:
---
setenv dvimode 1024x768-16@60
run loaduimage
run mmcboot
---
you could create a file named uEnv.txt and use that instead of boot.scr:
---
dvimode=1024x768-16@60
uenvcmd=run loaduimage; run mmcboot
---
The variable uenvcmd (if existent) will be executed (using run) after uEnv.txt
was loaded. If uenvcmd doesn't exist the default boot sequence will be started,
therefore you could just use
---
dvimode=1024x768-16@60
---
as uEnv.txt because loaduimage and mmcboot is part of the default boot sequence.
---
Changes for v2:
  - Eliminated else redundant clause that would be ignored if boot
succeeds.

Changes for v3:
  - Removed boot.scr

Changes for v4:
  - Removed comment about boot.scr being supported.

Signed-off-by: Jason Kridner jkrid...@beagleboard.org
Cc: Sandeep Paulraj s-paul...@ti.com
---
 include/configs/omap3_beagle.h |   28 
 1 files changed, 16 insertions(+), 12 deletions(-)

diff --git a/include/configs/omap3_beagle.h b/include/configs/omap3_beagle.h
index 8b580ef..c85537c 100644
--- a/include/configs/omap3_beagle.h
+++ b/include/configs/omap3_beagle.h
@@ -213,9 +213,9 @@
omapdss.def_disp=${defaultdisplay}  \
root=${nandroot}  \
rootfstype=${nandrootfstype}\0 \
-   loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr\0 \
-   bootscript=echo Running bootscript from mmc ...;  \
-   source ${loadaddr}\0 \
+   loadbootenv=fatload mmc ${mmcdev} ${loadaddr} uEnv.txt\0 \
+   importbootenv=echo Importing environment from mmc ...;  \
+   env import -t $loadaddr $filesize\0 \
loaduimage=fatload mmc ${mmcdev} ${loadaddr} uImage\0 \
mmcboot=echo Booting from mmc ...;  \
run mmcargs;  \
@@ -227,15 +227,19 @@
 
 #define CONFIG_BOOTCOMMAND \
if mmc rescan ${mmcdev}; then  \
-   if run loadbootscript; then  \
-   run bootscript;  \
-   else  \
-   if run loaduimage; then  \
-   run mmcboot;  \
-   else run nandboot;  \
-   fi;  \
-   fi;  \
-   else run nandboot; fi
+   echo SD/MMC found on device ${mmcdev}; \
+   if run loadbootenv; then  \
+   run importbootenv; \
+   fi; \
+   if test -n $uenvcmd; then  \
+   echo Running uenvcmd ...; \
+   run uenvcmd; \
+   fi; \
+   if run loaduimage; then  \
+   run mmcboot; \
+   fi; \
+   fi; \
+   run nandboot; \
 
 #define CONFIG_AUTO_COMPLETE   1
 /*
-- 
1.5.6.4

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] uboot for MIPS: need help to skip relocate uboot and start uboot from RAM

2011-03-03 Thread Charles Krinke
Dear Pandurang:

Sounds like you have battling boot loaders going on, perhaps with the
Broadcom CFE (Common Firmware Environment) ?

Someone else may have some data on CONFIG_SKIP_RELOCATE_UBOOT, or you could
reflash your target and replace the existing bootloader with the U-Boot
bootloader so your bootloaders are not battling for the same resource.

Charles

On Thu, Mar 3, 2011 at 2:08 AM, Pandurang Kale kale.pandur...@gmail.comwrote:

 Hello Everyone,

 We have MIPS based development board and I am trying to get the uboot up
 and
 running on it.
 We have a primary bootloader which check for the valid mod-image stored on
 the flash. This mod-image consist of header, uboot and linux kernel.
 Depending on the recent, active and stable imagethe primary bootloader
 first
 copies the uboot image. and later on we would copy the kernel image from
 uboot.

 But when primary bootloader copies the uboot image to the RAM and passes
 the
 control to the uboot, uboot (MIPS version of start.S and
 arch/mips/lib/borad.c) tries to relocate the
 already copied image from RAM (the primary bootloader copied it to start of
 the RAM+1MB address) to top of the RAM (0x87fc) region thinking that
 the
 uboot image is stored in flash.

 All I need to do is skip the uboot relocate code in MIPS version of uboot
 startup as the primary bootloader has already relocated the uboot from
 Flash
 to RAM and set up the stack pointer and other global data appropriately,
 which it does after relocation.
 I can see there is a switch for ARM processor, CONFIG_SKIP_RELOCATE_UBOOT,
 which skips the relocation of uboot code and tries to run the uboot from
 RAM. I
 cannot see a similar switch implemented for MIPS and didnt find any related
 thread anywhere in mailing list or on net.

 Do we have similar ARM like switch to SKIP the RELOCATION? If not has
 anyone
 done this before?

 I would really appreciate if you can guide me to overcome this issue to run
 the uboot cleanly skipping the relocation.

 Thanks in advance,
 Pandu

 ___
 U-Boot mailing list
 U-Boot@lists.denx.de
 http://lists.denx.de/mailman/listinfo/u-boot




-- 
Charles Krinke
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] uboot for MIPS: need help to skip relocate uboot and start uboot from RAM

2011-03-03 Thread Pandurang Kale
Hi Charles,

 Thanks for the info.
 We have a primary  boot loader, which read the flash which might contain
more than one existing mod-image(containing header, uboot and kernel) and
depending on the state and condition it decides which mod is valid and
copies the uboot from the valid mod-image to RAM.

 So our primary bootloader is needed to load correct version of u-boot to
RAM from flash. But I am looking for a fix where in the uboot should setup
the stack and gp and start executing from RAM and not to copy/relocate
itself all over again to different RAM (High-memory region) location.

Thanks,
Pandu

On Thu, Mar 3, 2011 at 3:27 PM, Charles Krinke charles.kri...@gmail.comwrote:

 Dear Pandurang:

 Sounds like you have battling boot loaders going on, perhaps with the
 Broadcom CFE (Common Firmware Environment) ?

 Someone else may have some data on CONFIG_SKIP_RELOCATE_UBOOT, or you could
 reflash your target and replace the existing bootloader with the U-Boot
 bootloader so your bootloaders are not battling for the same resource.

 Charles

 On Thu, Mar 3, 2011 at 2:08 AM, Pandurang Kale 
 kale.pandur...@gmail.comwrote:

 Hello Everyone,

 We have MIPS based development board and I am trying to get the uboot up
 and
 running on it.
 We have a primary bootloader which check for the valid mod-image stored on
 the flash. This mod-image consist of header, uboot and linux kernel.
 Depending on the recent, active and stable imagethe primary bootloader
 first
 copies the uboot image. and later on we would copy the kernel image from
 uboot.

 But when primary bootloader copies the uboot image to the RAM and passes
 the
 control to the uboot, uboot (MIPS version of start.S and
 arch/mips/lib/borad.c) tries to relocate the
 already copied image from RAM (the primary bootloader copied it to start
 of
 the RAM+1MB address) to top of the RAM (0x87fc) region thinking that
 the
 uboot image is stored in flash.

 All I need to do is skip the uboot relocate code in MIPS version of uboot
 startup as the primary bootloader has already relocated the uboot from
 Flash
 to RAM and set up the stack pointer and other global data appropriately,
 which it does after relocation.
 I can see there is a switch for ARM processor, CONFIG_SKIP_RELOCATE_UBOOT,
 which skips the relocation of uboot code and tries to run the uboot from
 RAM. I
 cannot see a similar switch implemented for MIPS and didnt find any
 related
 thread anywhere in mailing list or on net.

 Do we have similar ARM like switch to SKIP the RELOCATION? If not has
 anyone
 done this before?

 I would really appreciate if you can guide me to overcome this issue to
 run
 the uboot cleanly skipping the relocation.

 Thanks in advance,
 Pandu

 ___
 U-Boot mailing list
 U-Boot@lists.denx.de
 http://lists.denx.de/mailman/listinfo/u-boot




 --
 Charles Krinke



___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


[U-Boot] [PATCH] OMAP3: BeagleBoard: Enable pullups on i2c2.

2011-03-03 Thread Jason Kridner
From: Steve Kipisz s-kipi...@ti.com

This allows the reading of EEPROMS on the expansion bus without adding
external pull-ups.
---
v2 updates
 * Updated per http://patchwork.ozlabs.org/patch/71997/
 * Added description
 * Used OMAP34XX_CTRL_BASE
 * Used structure and writel to perform write

Signed-off-by: Jason Kridner jkrid...@beagleboard.org
---
 arch/arm/include/asm/arch-omap3/omap3.h |   16 
 board/ti/beagle/beagle.c|4 
 2 files changed, 20 insertions(+), 0 deletions(-)

diff --git a/arch/arm/include/asm/arch-omap3/omap3.h 
b/arch/arm/include/asm/arch-omap3/omap3.h
index 3957c79..88454f2 100644
--- a/arch/arm/include/asm/arch-omap3/omap3.h
+++ b/arch/arm/include/asm/arch-omap3/omap3.h
@@ -50,6 +50,22 @@
 /* CONTROL */
 #define OMAP34XX_CTRL_BASE (OMAP34XX_L4_IO_BASE + 0x2000)
 
+#ifndef __ASSEMBLY__
+
+/* Signal Integrity Parameter Control Registers */
+struct control_prog_io {
+   unsigned char res[0x408];
+   unsigned int io2;   /* 0x408 */
+   unsigned char res2[0x38];
+   unsigned int io0;   /* 0x444 */
+   unsigned int io1;   /* 0x448 */
+};
+
+#endif /* __ASSEMBLY__ */
+
+/* Bit definition for CONTROL_PROG_IO1 */
+#define PRG_I2C2_PULLUPRESX0x0001
+
 /* UART */
 #define OMAP34XX_UART1 (OMAP34XX_L4_IO_BASE + 0x6a000)
 #define OMAP34XX_UART2 (OMAP34XX_L4_IO_BASE + 0x6c000)
diff --git a/board/ti/beagle/beagle.c b/board/ti/beagle/beagle.c
index 929461c..7ba98f1 100644
--- a/board/ti/beagle/beagle.c
+++ b/board/ti/beagle/beagle.c
@@ -148,6 +148,10 @@ int misc_init_r(void)
 {
struct gpio *gpio5_base = (struct gpio *)OMAP34XX_GPIO5_BASE;
struct gpio *gpio6_base = (struct gpio *)OMAP34XX_GPIO6_BASE;
+   struct prog_io *prog_io_base = (struct gpio *)OMAP34XX_CTRL_BASE;
+
+   /* Enable i2c2 pullup resisters */
+   writel(~(PRG_I2C2_PULLUPRESX), prog_io_base-io1);
 
switch (get_board_revision()) {
case REVISION_AXBX:
-- 
1.5.6.4

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


[U-Boot] [PATCH 1/1] ARMV7: Vexpress: Remove config.mk

2011-03-03 Thread matt . waddel
From: Matt Waddel matt.wad...@linaro.org

Remove obsolete board config.mk.

Signed-off-by: Matt Waddel matt.wad...@linaro.org
---
 board/armltd/vexpress/config.mk |   22 --
 include/configs/ca9x4_ct_vxp.h  |1 +
 2 files changed, 1 insertions(+), 22 deletions(-)
 delete mode 100644 board/armltd/vexpress/config.mk

diff --git a/board/armltd/vexpress/config.mk b/board/armltd/vexpress/config.mk
deleted file mode 100644
index 36395f2..000
--- a/board/armltd/vexpress/config.mk
+++ /dev/null
@@ -1,22 +0,0 @@
-#
-# See file CREDITS for list of people who contributed to this
-# project.
-#
-# This program is free software; you can redistribute it and/or
-# modify it under the terms of the GNU General Public License as
-# published by the Free Software Foundation; either version 2 of
-# the License, or (at your option) any later version.
-#
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY; without even the implied warranty of
-# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-# GNU General Public License for more details.
-#
-# You should have received a copy of the GNU General Public License
-# along with this program; if not, write to the Free Software
-# Foundation, Inc., 59 Temple Place, Suite 330, Boston,
-# MA 02111-1307 USA
-#
-# Linux-Kernel is expected to be at 0x60008000
-#
-CONFIG_SYS_TEXT_BASE = 0x6080
diff --git a/include/configs/ca9x4_ct_vxp.h b/include/configs/ca9x4_ct_vxp.h
index 4ab58c0..c6fac32 100644
--- a/include/configs/ca9x4_ct_vxp.h
+++ b/include/configs/ca9x4_ct_vxp.h
@@ -30,6 +30,7 @@
 /* Board info register */
 #define SYS_ID 0x1000
 #define CONFIG_REVISION_TAG1
+#define CONFIG_SYS_TEXT_BASE   0x6080
 
 /* High Level Configuration Options */
 #define CONFIG_ARMV7   1
-- 
1.7.1

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


[U-Boot] [PATCH v3] OMAP3: BeagleBoard: Enable pullups on i2c2.

2011-03-03 Thread Jason Kridner
From: Steve Kipisz s-kipi...@ti.com

This allows the reading of EEPROMS on the expansion bus without adding
external pull-ups.
---
v2 updates
 * Updated per http://patchwork.ozlabs.org/patch/71997/
 * Added description
 * Used OMAP34XX_CTRL_BASE
 * Used structure and writel to perform write

v3 updates
 * Included v3 in the subject line
 * Fixed structure name typo that got messed up in generating patch
 * Removed some extraneous blank lines

Signed-off-by: Jason Kridner jkrid...@beagleboard.org
---
 arch/arm/include/asm/arch-omap3/omap3.h |   14 ++
 board/ti/beagle/beagle.c|4 
 2 files changed, 18 insertions(+), 0 deletions(-)

diff --git a/arch/arm/include/asm/arch-omap3/omap3.h 
b/arch/arm/include/asm/arch-omap3/omap3.h
index 3957c79..cc2b541 100644
--- a/arch/arm/include/asm/arch-omap3/omap3.h
+++ b/arch/arm/include/asm/arch-omap3/omap3.h
@@ -50,6 +50,20 @@
 /* CONTROL */
 #define OMAP34XX_CTRL_BASE (OMAP34XX_L4_IO_BASE + 0x2000)
 
+#ifndef __ASSEMBLY__
+/* Signal Integrity Parameter Control Registers */
+struct control_prog_io {
+   unsigned char res[0x408];
+   unsigned int io2;   /* 0x408 */
+   unsigned char res2[0x38];
+   unsigned int io0;   /* 0x444 */
+   unsigned int io1;   /* 0x448 */
+};
+#endif /* __ASSEMBLY__ */
+
+/* Bit definition for CONTROL_PROG_IO1 */
+#define PRG_I2C2_PULLUPRESX0x0001
+
 /* UART */
 #define OMAP34XX_UART1 (OMAP34XX_L4_IO_BASE + 0x6a000)
 #define OMAP34XX_UART2 (OMAP34XX_L4_IO_BASE + 0x6c000)
diff --git a/board/ti/beagle/beagle.c b/board/ti/beagle/beagle.c
index 929461c..3884ca1 100644
--- a/board/ti/beagle/beagle.c
+++ b/board/ti/beagle/beagle.c
@@ -148,6 +148,10 @@ int misc_init_r(void)
 {
struct gpio *gpio5_base = (struct gpio *)OMAP34XX_GPIO5_BASE;
struct gpio *gpio6_base = (struct gpio *)OMAP34XX_GPIO6_BASE;
+   struct control_prog_io *prog_io_base = (struct gpio 
*)OMAP34XX_CTRL_BASE;
+
+   /* Enable i2c2 pullup resisters */
+   writel(~(PRG_I2C2_PULLUPRESX), prog_io_base-io1);
 
switch (get_board_revision()) {
case REVISION_AXBX:
-- 
1.5.6.4

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


[U-Boot] [PATCH v2] OMAP3: BeagleBoard: add xM rev B to ID table

2011-03-03 Thread Jason Kridner
From: Koen Kooi k...@dominion.thruhere.net

Patch was updated by Jason Kridner jkrid...@beagleboard.org:
* Use tabs to match style of other board revisions
* Only include board revisions that exist
* Default to the same configuration as the latest revision, but
  without setting 'beaglerev'
---
v2 Changes
  * Updated with feedback from http://patchwork.ozlabs.org/patch/71995/
  * Removed setting of mpurate based on board revision
  * Set mpurate to auto in default environment variables

Cc: Koen Kooi k...@dominion.thruhere.net
Signed-off-by: Jason Kridner jkrid...@beagleboard.org
---
 board/ti/beagle/beagle.c   |   22 +-
 board/ti/beagle/beagle.h   |3 ++-
 include/configs/omap3_beagle.h |2 +-
 3 files changed, 20 insertions(+), 7 deletions(-)

diff --git a/board/ti/beagle/beagle.c b/board/ti/beagle/beagle.c
index 3884ca1..4049606 100644
--- a/board/ti/beagle/beagle.c
+++ b/board/ti/beagle/beagle.c
@@ -157,18 +157,15 @@ int misc_init_r(void)
case REVISION_AXBX:
printf(Beagle Rev Ax/Bx\n);
setenv(beaglerev, AxBx);
-   setenv(mpurate, 600);
break;
case REVISION_CX:
printf(Beagle Rev C1/C2/C3\n);
setenv(beaglerev, Cx);
-   setenv(mpurate, 600);
MUX_BEAGLE_C();
break;
case REVISION_C4:
printf(Beagle Rev C4\n);
setenv(beaglerev, C4);
-   setenv(mpurate, 720);
MUX_BEAGLE_C();
/* Set VAUX2 to 1.8V for EHCI PHY */
twl4030_pmrecv_vsel_cfg(TWL4030_PM_RECEIVER_VAUX2_DEDICATED,
@@ -176,10 +173,19 @@ int misc_init_r(void)
TWL4030_PM_RECEIVER_VAUX2_DEV_GRP,
TWL4030_PM_RECEIVER_DEV_GRP_P1);
break;
-   case REVISION_XM:
+   case REVISION_XM_A:
printf(Beagle xM Rev A\n);
setenv(beaglerev, xMA);
-   setenv(mpurate, 1000);
+   MUX_BEAGLE_XM();
+   /* Set VAUX2 to 1.8V for EHCI PHY */
+   twl4030_pmrecv_vsel_cfg(TWL4030_PM_RECEIVER_VAUX2_DEDICATED,
+   TWL4030_PM_RECEIVER_VAUX2_VSEL_18,
+   TWL4030_PM_RECEIVER_VAUX2_DEV_GRP,
+   TWL4030_PM_RECEIVER_DEV_GRP_P1);
+   break;
+   case REVISION_XM_B:
+   printf(Beagle xM Rev B\n);
+   setenv(beaglerev, xMB);
MUX_BEAGLE_XM();
/* Set VAUX2 to 1.8V for EHCI PHY */
twl4030_pmrecv_vsel_cfg(TWL4030_PM_RECEIVER_VAUX2_DEDICATED,
@@ -189,6 +195,12 @@ int misc_init_r(void)
break;
default:
printf(Beagle unknown 0x%02x\n, get_board_revision());
+   MUX_BEAGLE_XM();
+   /* Set VAUX2 to 1.8V for EHCI PHY */
+   twl4030_pmrecv_vsel_cfg(TWL4030_PM_RECEIVER_VAUX2_DEDICATED,
+   TWL4030_PM_RECEIVER_VAUX2_VSEL_18,
+   TWL4030_PM_RECEIVER_VAUX2_DEV_GRP,
+   TWL4030_PM_RECEIVER_DEV_GRP_P1);
}
 
switch (get_expansion_id()) {
diff --git a/board/ti/beagle/beagle.h b/board/ti/beagle/beagle.h
index b22b653..b0e26e5 100644
--- a/board/ti/beagle/beagle.h
+++ b/board/ti/beagle/beagle.h
@@ -37,7 +37,8 @@ const omap3_sysinfo sysinfo = {
 #define REVISION_AXBX  0x7
 #define REVISION_CX0x6
 #define REVISION_C40x5
-#define REVISION_XM0x0
+#define REVISION_XM_A  0x0
+#define REVISION_XM_B  0x1
 
 /*
  * IEN  - Input Enable
diff --git a/include/configs/omap3_beagle.h b/include/configs/omap3_beagle.h
index c85537c..51e14d0 100644
--- a/include/configs/omap3_beagle.h
+++ b/include/configs/omap3_beagle.h
@@ -190,7 +190,7 @@
loadaddr=0x8200\0 \
usbtty=cdc_acm\0 \
console=ttyS2,115200n8\0 \
-   mpurate=500\0 \
+   mpurate=auto\0 \
vram=12M\0 \
dvimode=1024x768MR-16@60\0 \
defaultdisplay=dvi\0 \
-- 
1.5.6.4

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


[U-Boot] [PATCH v2] OMAP3: BeagleBoard: add more expansionboard IDs

2011-03-03 Thread Jason Kridner
From: Koen Kooi k...@dominion.thruhere.net

Information on configurations pulled from
http://www.elinux.org/BeagleBoardPinMux#Vendor_and_Device_IDs

Boards added:
* Added BeagleBoardToys WiFi, VGA and LCD boards
* Added KBADC Beagle FPGA board
* Added Brainmux LCDog and LCDog Touch
* Added Liquidware BeagleTouch
---
v2 updates
  * Feedback from http://www.mail-archive.com/u-boot@lists.denx.de/msg41851.html
- Removed unused definitions
- The detection mechanism *is* consistent, simple read from an EEPROM
  * Added BeagleBoardToys board configurations
  * Made definition names consistent as VENDOR_BOARD

Signed-off-by: Jason Kridner jkrid...@beagleboard.org
Cc: Koen Kooi k...@dominion.thruhere.net
---
 board/ti/beagle/beagle.c |   30 +-
 board/ti/beagle/beagle.h |   12 
 2 files changed, 41 insertions(+), 1 deletions(-)

diff --git a/board/ti/beagle/beagle.c b/board/ti/beagle/beagle.c
index 4049606..e05232f 100644
--- a/board/ti/beagle/beagle.c
+++ b/board/ti/beagle/beagle.c
@@ -48,7 +48,12 @@
 #define TINCANTOOLS_TRAINER0x04000100
 #define TINCANTOOLS_SHOWDOG0x03000100
 #define KBADC_BEAGLEFPGA   0x01000600
-
+#define LW_BEAGLETOUCH 0x01000700
+#define BRAINMUX_LCDOG 0x01000800
+#define BRAINMUX_LCDOGTOUCH0x02000800
+#define BBTOYS_WIFI0x01000B00
+#define BBTOYS_VGA 0x02000B00
+#define BBTOYS_LCD 0x03000B00
 #define BEAGLE_NO_EEPROM   0x
 
 DECLARE_GLOBAL_DATA_PTR;
@@ -239,6 +244,29 @@ int misc_init_r(void)
MUX_KBADC_BEAGLEFPGA();
setenv(buddy, beaglefpga);
break;
+   case LW_BEAGLETOUCH:
+   printf(Recognized Liquidware BeagleTouch board\n);
+   setenv(buddy, beagletouch);
+   break;
+   case BRAINMUX_LCDOG:
+   printf(Recognized Brainmux LCDog board\n);
+   setenv(buddy, lcdog);
+   break;
+   case BRAINMUX_LCDOGTOUCH:
+   printf(Recognized Brainmux LCDog Touch board\n);
+   setenv(buddy, lcdogtouch);
+   break;
+   case BBTOYS_WIFI:
+   printf(Recognized BeagleBoardToys WiFi board\n);
+   MUX_BBTOYS_WIFI()
+   setenv(buddy, bbtoys-wifi);
+   break;;
+   case BBTOYS_VGA:
+   printf(Recognized BeagleBoardToys VGA board\n);
+   break;;
+   case BBTOYS_LCD:
+   printf(Recognized BeagleBoardToys LCD board\n);
+   break;;
case BEAGLE_NO_EEPROM:
printf(No EEPROM on expansion board\n);
setenv(buddy, none);
diff --git a/board/ti/beagle/beagle.h b/board/ti/beagle/beagle.h
index b0e26e5..0f21790 100644
--- a/board/ti/beagle/beagle.h
+++ b/board/ti/beagle/beagle.h
@@ -458,4 +458,16 @@ const omap3_sysinfo sysinfo = {
MUX_VAL(CP(MCBSP1_DR),  (IEN  | PTU | EN  | M1)) /*MCSPI4_SOMI*/\
MUX_VAL(CP(MCBSP1_FSX), (IDIS | PTU | DIS | M1)) /*MCSPI4_CS0*/
 
+#define MUX_BBTOYS_WIFI() \
+   MUX_VAL(CP(MMC2_CLK),   (IEN  | PTU | EN  | M0)) /*MMC2_CLK*/\
+   MUX_VAL(CP(MMC2_CMD),   (IEN  | PTU | EN  | M0)) /*MMC2_CMD*/\
+   MUX_VAL(CP(MMC2_DAT0),  (IEN  | PTU | EN  | M0)) /*MMC2_DAT0*/\
+   MUX_VAL(CP(MMC2_DAT1),  (IEN  | PTU | EN  | M0)) /*MMC2_DAT1*/\
+   MUX_VAL(CP(MMC2_DAT2),  (IEN  | PTU | EN  | M0)) /*MMC2_DAT2*/\
+   MUX_VAL(CP(MMC2_DAT3),  (IEN  | PTU | EN  | M0)) /*MMC2_DAT3*/\
+   MUX_VAL(CP(MMC2_DAT4),  (IDIS | PTU | EN  | M4)) /*GPIO_136 
FM_EN/BT_WU*/\
+   MUX_VAL(CP(MMC2_DAT5),  (IEN  | PTU | EN  | M4)) /*GPIO_137 
WLAN_IRQ*/\
+   MUX_VAL(CP(MMC2_DAT6),  (IDIS | PTU | EN  | M4)) /*GPIO_138 BT_EN*/\
+   MUX_VAL(CP(MMC2_DAT7),  (IDIS | PTU | EN  | M4)) /*GPIO_139 
WLAN_EN*/
+
 #endif
-- 
1.5.6.4

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


[U-Boot] Leaving at 3:30 PM Tomorrow

2011-03-03 Thread Richard Retanubun
Hi Guys,

Heads up, I am planning to leave at 3:30 tomorrow for an appointment. Find me 
today and tomorrow.
Have made up the hours by staying late this week.

- Richard
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH] net: axi_ethernet: Add driver to u-boot

2011-03-03 Thread Mike Frysinger
On Tuesday, March 01, 2011 04:29:21 Michal Simek wrote:
 Mike Frysinger wrote:
  On Tuesday, March 01, 2011 03:34:38 Michal Simek wrote:
  How does it look like phy lib u-boot support?
  
  i dont know what you mean ... how is phylib relevant to this ?  or are
  you just asking in general ?
 
 Ben wanted to create general phy lib support and remove all phy specific
 things from net drivers. I hope you see that connection because there is
 also phy part.
 If phy lib support is in progress (which probably not) then I would change
 the driver to support it.

yes, but that isnt relevant to any of the feedback ive given for this patch

  also, you should change the hang() to return 0 in the init func.
  
  Are you sure return 0 which should mean success. Anything different from
  0 seems to me relevant.
  
  as i said, the initialize function is not returning success or
  failure. it is returning # of devices registered.  if you cannot
  register any, you should return 0.  having the boot process fail because
  of network issues doesnt make much sense when u-boot can do quite a lot
  without the network. including updating itself via other means.
 
 Interesting.
 1. you talked about hang() in initialize function(not dev-init) and for me
 xilinx_axiemac_initialize Initialize function is called from 
 board_eth_init which is called from eth_initialize(eth.c)
 
 There is this part of code
   if (board_eth_init != __def_eth_init) {
   if (board_eth_init(bis)  0)
   printf(Board Net Initialization Failed\n);
 
 If initialization failed the return value is  0.
 That's why hang() should be changed to return -1 and doesn't matter how
 many device there are.

this detail isnt currently ironed out, so if you wanted to change the hang() 
into return -1 or return 0, that is fine.

 If you write:
   also, you should change the hang() to return 0 in the init func.
 
 (hang is only in xilinx_axiemac_initialize) and should be changed which I
 agree.
 
 If you propose any change which I should do, I expect that if you are focus
 on blackfin that you have done that changes in all blackfin eth drivers.
 For example in bfin_mac.c where hang is also used.

incorrect code in other drivers (including bfin_mac) is not justification for 
adding incorrect code to new drivers.  bfin_mac.c's call to hang() is wrong 
too in the current code base.

  I maintain emaclite driver and none tell me this that's why the process
  is so slow. I believe if you release that documentation, which you are
  talking about, then others will clean/test their drivers.
  
  the behavior i describe isnt a decision i made.  it was made by the
  previous net maintainer and agreed upon by others in the discussion.
 
 Ok. If that decision was made than I expect that should be written
 somewhere in doc. I know it is boring to write any documentation but I
 expect that if any decision was made then is common that general code will
 be changed.

obviously that is true, but docs only get written/updated when someone is so 
inclined to do the work.  the existing doc only exists because i felt like 
writing at the time.  ive never been the net maintainer and thus obligated 
to write net documentation.  i just got tired of people doing it wrong and no 
one knowing what should be going on.

 1. hang() - return -1

ok

 2. driver initialize function (setup dev functions, driver name, priv, etc)
 return -1 - if initialize failed
 return 0 - on success

no, return 1 when the device has successfully registered

 3. dev-init
 return -1 - if init failed
 return 0 - on success

ok

 (here you are saying should be return # of devices)

no, i think you confused initialize with init in my feedback

 4. dev-recv
 return -1 - failed
 return 0 - packet not received
 return 0 - success - packet lenght

return 0 is still success in the sense that there is nothing to do, but 
that nuance doesnt matter

 5. dev-send
 return -1 - failed
 return 0 - success
 
 6. dev-write_hwaddr
 return -1 - failed
 return 0 - success

ok
-mike


signature.asc
Description: This is a digitally signed message part.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH] ARM: Don't grab memory for LCD if FB address is defined

2011-03-03 Thread Wolfgang Denk
Dear Minkyu Kang,

In message 4d6f5611.40...@samsung.com you wrote:
 If FB address is defined as specific address then don't grab memory for LCD
 
 Signed-off-by: Minkyu Kang mk7.k...@samsung.com
 ---
  arch/arm/lib/board.c |4 
  1 files changed, 4 insertions(+), 0 deletions(-)

Sorry, but NAK.

You cannot make this change for ARM only.  It needs to be implemented
for all architectures.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH, MD: Wolfgang Denk  Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de
There comes to all races an ultimate crisis which  you  have  yet  to
face    One  day  our  minds became so powerful we dared think of
ourselves as gods.
-- Sargon, Return to Tomorrow, stardate 4768.3
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] uboot for MIPS: need help to skip relocate uboot and start uboot from RAM

2011-03-03 Thread Wolfgang Denk
Dear Pandurang Kale,

In message AANLkTikLJzuCSwOhMLz2sWy1j9a3LiV8zzY6=tjtf...@mail.gmail.com you 
wrote:

 But when primary bootloader copies the uboot image to the RAM and passes the
 control to the uboot, uboot (MIPS version of start.S and
 arch/mips/lib/borad.c) tries to relocate the
 already copied image from RAM (the primary bootloader copied it to start of
 the RAM+1MB address) to top of the RAM (0x87fc) region thinking that the
 uboot image is stored in flash.

U-Boot does not think it is stored in flash - this is what you
configured.  If you know you're always loading it to a fixed RAM
address, you can use this as reference for TEXT_BASE instead.

 All I need to do is skip the uboot relocate code in MIPS version of uboot

No, you do NOT want to do thjat, as it would cripple U-Boot and remove
basic functionality from it.

 I can see there is a switch for ARM processor, CONFIG_SKIP_RELOCATE_UBOOT,

Are you looking at recent code and working boards?

 I would really appreciate if you can guide me to overcome this issue to run
 the uboot cleanly skipping the relocation.

Do do not want to skip relocation.  U-Boot may need to auto-adjust
it's start address dynamically, depending on configuration, system
requirements and/or environment settings.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH, MD: Wolfgang Denk  Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de
If God wanted me to touch my toes, he'd have put them on my knees.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH 1/2 v2] rename _end to __bss_end__

2011-03-03 Thread Albert ARIBAUD
Le 02/03/2011 09:59, Po-Yu Chuang a écrit :
 From: Po-Yu Chuangratb...@faraday-tech.com

 Currently, _end is used for end of BSS section.  We want _end to mean
 end of u-boot image, so we rename _end to __bss_end__ first.

 Signed-off-by: Po-Yu Chuangratb...@faraday-tech.com
 ---
 This is done by the following command:
 $ for f in `find * -type f`; do sed -i 's/\_end\/__bss_end__/g' $f; done

 v2:
 modify commit message

Patch applied to u-boot-arm/master (as it is a bugfix), thanks!

Amicalement,
-- 
Albert.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] uboot for MIPS: need help to skip relocate uboot and start uboot from RAM

2011-03-03 Thread Pandurang Kale
Hi Wolfgang Denk,

 Thanks for the response. Please find my questions inline.

On Thu, Mar 3, 2011 at 11:11 PM, Wolfgang Denk w...@denx.de wrote:

 Dear Pandurang Kale,

 In message AANLkTikLJzuCSwOhMLz2sWy1j9a3LiV8zzY6=tjtf...@mail.gmail.com
 you wrote:
 
  But when primary bootloader copies the uboot image to the RAM and passes
 the
  control to the uboot, uboot (MIPS version of start.S and
  arch/mips/lib/borad.c) tries to relocate the
  already copied image from RAM (the primary bootloader copied it to start
 of
  the RAM+1MB address) to top of the RAM (0x87fc) region thinking that
 the
  uboot image is stored in flash.

 U-Boot does not think it is stored in flash - this is what you
 configured.  If you know you're always loading it to a fixed RAM
 address, you can use this as reference for TEXT_BASE instead

For MIPS I do not find the TEXT_BASE symbol, there is SYS_CFG_MONITOR_BASE
which it uses to relocate the code from the define symbol to high RAM
address. how can I avoid this?  As I see we have a switch defined for ARM,
CONFIG_SKIP_RELOCATE_UBOOT,  to skip the code relocation I cant find a
similar instance in MIPS code. Can you please throw some light on getting
the TEXT_BASE setting correctly for MIPS code? how can I do that?

 .

  All I need to do is skip the uboot relocate code in MIPS version of uboot

 No, you do NOT want to do thjat, as it would cripple U-Boot and remove
 basic functionality from it.


  I can see there is a switch for ARM processor,
 CONFIG_SKIP_RELOCATE_UBOOT,

 Are you looking at recent code and working boards?

I have recent uboot code for MIPS and I cant find any similar switch for
MIPS codebase. arch/mips/lib/board.c and arch/mips/cpu/start.S


  I would really appreciate if you can guide me to overcome this issue to
 run
  the uboot cleanly skipping the relocation.

 Do do not want to skip relocation.  U-Boot may need to auto-adjust
 it's start address dynamically, depending on configuration, system
 requirements and/or environment settings.

The uboot is already loaded in the RAM (by the primary boot loader) so I
dont want uboot to again relocate itself from one location of RAM to its
predefined high-memory region in RAM which I have explained in my first
mail.


 Best regards,

 Wolfgang Denk

 Thanks a lot,
Pandu

 --
 DENX Software Engineering GmbH, MD: Wolfgang Denk  Detlev Zundel
 HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
 Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de
 If God wanted me to touch my toes, he'd have put them on my knees.

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [beagleboard] Re: [PATCH v3] omap3_beagle: enable the use of a plain text file named uEnv.txt instead of boot.scr

2011-03-03 Thread Alexander Holler
Hello,

Am 03.03.2011 16:04, schrieb Jason Kridner:
 On Wed, Mar 2, 2011 at 6:48 PM, Robert Nelsonrobertcnel...@gmail.com  wrote:
 On Wed, Mar 2, 2011 at 5:41 PM, Alexander Hollerhol...@ahsoftware.de  
 wrote:
 Hello Jason,

 Am 02.03.2011 21:26, schrieb Jason Kridner:

 For backwards compatibility the use of boot.scr is still supported.


 Sorry, but I think that line in the description should get removed too.

 I'll submit a v4.



 So, just a thought..  Are you guys planning to push this same boot
 method to all the other omap devices that just finally got boot.scr
 boot support by default in u-boot?  It also seems's like it'll end up
 be the FAQ of the month for the beagleboard group.. ;)

 Indeed it is likely to be FAQ of the month, especially if it lands in
 the next software update that gets shipped with the board.  It is a
 case, however, in which I like the answer--no more need to run
 mkimage.  The conversion process of a boot.scr script (commands) to a
 uEnv.txt file (variable setting) won't be exactly trivial, so that has
 me a tiny bit concerned.  Still, most cases will be solved by a *much*
 simpler uEnv.txt script and an overall simpler process.

Hmm, if someone will write such an FAQ-entry, be sure to mention that 
people shouldn't use a windows-editor. I haven't tried it, but I don't 
believe env import likes carriage returns.

Regards,

Alexander
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH v3] omap3_beagle: enable the use of a plain text file named uEnv.txt instead of boot.scr

2011-03-03 Thread Alexander Holler
Am 03.03.2011 00:48, schrieb Robert Nelson:
 On Wed, Mar 2, 2011 at 5:41 PM, Alexander Hollerhol...@ahsoftware.de  wrote:
 Hello Jason,

 Am 02.03.2011 21:26, schrieb Jason Kridner:

 For backwards compatibility the use of boot.scr is still supported.


 Sorry, but I think that line in the description should get removed too.


 So, just a thought..  Are you guys planning to push this same boot
 method to all the other omap devices that just finally got boot.scr
 boot support by default in u-boot?  It also seems's like it'll end up
 be the FAQ of the month for the beagleboard group.. ;)

I would say that should be decided by every board-maintainer, just like 
the change from ttyS2 to ttyO2. E.g. I don't think the devkit8000-sdk 
will change as soon as the stuff the for the beagleboard.

Regards,

Alexander
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH v3] omap3_beagle: enable the use of a plain text file named uEnv.txt instead of boot.scr

2011-03-03 Thread Robert Nelson
On Thu, Mar 3, 2011 at 7:43 PM, Alexander Holler hol...@ahsoftware.de wrote:
 Am 03.03.2011 00:48, schrieb Robert Nelson:

 On Wed, Mar 2, 2011 at 5:41 PM, Alexander Hollerhol...@ahsoftware.de
  wrote:

 Hello Jason,

 Am 02.03.2011 21:26, schrieb Jason Kridner:

 For backwards compatibility the use of boot.scr is still supported.


 Sorry, but I think that line in the description should get removed too.


 So, just a thought..  Are you guys planning to push this same boot
 method to all the other omap devices that just finally got boot.scr
 boot support by default in u-boot?  It also seems's like it'll end up
 be the FAQ of the month for the beagleboard group.. ;)

 I would say that should be decided by every board-maintainer, just like the
 change from ttyS2 to ttyO2. E.g. I don't think the devkit8000-sdk will
 change as soon as the stuff the for the beagleboard.

Oh, we will work around it over the transition, so it's not a big deal..

It was just kinda nice, (if we assume all boards have xlo/u-boot in
nand) that most boards would boot on one boot.scr/kernel/rootfs
combination.  Since the mainline kernel can boot on all omap2/3/4
boards (in mainline) at this point..

But since both the xM/Panda don't have nand, my point's kinda moot as
they'll need a different xlo/u-boot...

Regards,
-- 
Robert Nelson
http://www.rcn-ee.com/
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


[U-Boot] add required macro

2011-03-03 Thread Kavin Lau
From a3fb0b578a6cbe57670c7363c0707fdb9e7e3bc4 Mon Sep 17 
00:00:00 2001
From: Kavin Lau liujingwe...@gmail.com
Date: Fri, 4 Mar 2011 09:52:36 +0800
Subject: [PATCH] arm1176: Added CONFIG_PRELOADER macro that is 
required

The callers of those labels are under covered of CONFIG_PRELOADER 
macro,
so those labels should be under covered too.
---
 arch/arm/cpu/arm1176/start.S |2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/arch/arm/cpu/arm1176/start.S 
b/arch/arm/cpu/arm1176/start.S
index 363329a..624f71c 100644
--- a/arch/arm/cpu/arm1176/start.S
+++ b/arch/arm/cpu/arm1176/start.S
@@ -379,12 +379,14 @@ _board_init_r_ofs:
.word board_init_r - _start
 #endif
 
+#ifndef CONFIG_PRELOADER
 _rel_dyn_start_ofs:
.word __rel_dyn_start - _start
 _rel_dyn_end_ofs:
.word __rel_dyn_end - _start
 _dynsym_start_ofs:
.word __dynsym_start - _start
+#endif
 
 #ifdef CONFIG_ENABLE_MMU
 _mmu_table_base:
-- 
1.7.1

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


[U-Boot] [PATCH v2] env: make import/export optional

2011-03-03 Thread Mike Frysinger
Signed-off-by: Mike Frysinger vap...@gentoo.org
---
 README|2 ++
 common/cmd_nvedit.c   |8 
 include/config_cmd_defaults.h |2 ++
 3 files changed, 12 insertions(+), 0 deletions(-)

diff --git a/README b/README
index faee6fb..1773f00 100644
--- a/README
+++ b/README
@@ -632,6 +632,7 @@ The following options need to be configured:
CONFIG_CMD_EDITENVedit env variable
CONFIG_CMD_EEPROM   * EEPROM read/write support
CONFIG_CMD_ELF  * bootelf, bootvx
+   CONFIG_CMD_EXPORTENV* export the environment
CONFIG_CMD_SAVEENVsaveenv
CONFIG_CMD_FDC  * Floppy Disk Support
CONFIG_CMD_FAT  * FAT partition support
@@ -644,6 +645,7 @@ The following options need to be configured:
CONFIG_CMD_IMIiminfo
CONFIG_CMD_IMLS   List all found images
CONFIG_CMD_IMMAP* IMMR dump support
+   CONFIG_CMD_IMPORTENV* import an environment
CONFIG_CMD_IRQ  * irqinfo
CONFIG_CMD_ITEST  Integer/string test of 2 values
CONFIG_CMD_JFFS2* JFFS2 Support
diff --git a/common/cmd_nvedit.c b/common/cmd_nvedit.c
index fb69c24..715dffd 100644
--- a/common/cmd_nvedit.c
+++ b/common/cmd_nvedit.c
@@ -559,6 +559,7 @@ static int do_env_delete(cmd_tbl_t * cmdtp, int flag, int 
argc, char * const arg
return 0;
 }
 
+#ifdef CONFIG_CMD_EXPORTENV
 /*
  * env export [-t | -b | -c] addr [size]
  * -t: export as text format; if size is given, data will be
@@ -695,7 +696,9 @@ sep_err:
cmd);
return 1;
 }
+#endif
 
+#ifdef CONFIG_CMD_IMPORTENV
 /*
  * env import [-d] [-t | -b | -c] addr [size]
  * -d: delete existing environment before importing;
@@ -805,6 +808,7 @@ sep_err:
cmd);
return 1;
 }
+#endif
 
 #if defined(CONFIG_CMD_RUN)
 extern int do_run (cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[]);
@@ -822,8 +826,12 @@ static cmd_tbl_t cmd_env_sub[] = {
 #if defined(CONFIG_CMD_EDITENV)
U_BOOT_CMD_MKENT(edit, 2, 0, do_env_edit, , ),
 #endif
+#if defined(CONFIG_CMD_EXPORTENV)
U_BOOT_CMD_MKENT(export, 4, 0, do_env_export, , ),
+#endif
+#if defined(CONFIG_CMD_IMPORTENV)
U_BOOT_CMD_MKENT(import, 5, 0, do_env_import, , ),
+#endif
U_BOOT_CMD_MKENT(print, CONFIG_SYS_MAXARGS, 1, do_env_print, , ),
 #if defined(CONFIG_CMD_RUN)
U_BOOT_CMD_MKENT(run, CONFIG_SYS_MAXARGS, 1, do_run, , ),
diff --git a/include/config_cmd_defaults.h b/include/config_cmd_defaults.h
index 9283daa..6adebdb 100644
--- a/include/config_cmd_defaults.h
+++ b/include/config_cmd_defaults.h
@@ -10,5 +10,7 @@
 #define _CONFIG_CMD_DEFAULTS_H_
 
 #define CONFIG_CMD_BOOTM 1
+#define CONFIG_CMD_EXPORTENV 1
+#define CONFIG_CMD_IMPORTENV 1
 
 #endif
-- 
1.7.4.1

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


[U-Boot] [PATCH] make `go` optional

2011-03-03 Thread Mike Frysinger
Signed-off-by: Mike Frysinger vap...@gentoo.org
---
 README|1 +
 common/cmd_boot.c |4 
 include/config_cmd_defaults.h |1 +
 3 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/README b/README
index 1773f00..49a5bb9 100644
--- a/README
+++ b/README
@@ -639,6 +639,7 @@ The following options need to be configured:
CONFIG_CMD_FDOS * Dos diskette Support
CONFIG_CMD_FLASH  flinfo, erase, protect
CONFIG_CMD_FPGA   FPGA device initialization support
+   CONFIG_CMD_GO   * the 'go' command (exec code)
CONFIG_CMD_HWFLOW   * RTS/CTS hw flow control
CONFIG_CMD_I2C  * I2C serial bus support
CONFIG_CMD_IDE  * IDE harddisk support
diff --git a/common/cmd_boot.c b/common/cmd_boot.c
index 7b603d3..0afd939 100644
--- a/common/cmd_boot.c
+++ b/common/cmd_boot.c
@@ -28,6 +28,8 @@
 #include command.h
 #include net.h
 
+#ifdef CONFIG_CMD_GO
+
 /* Allow ports to override the default behavior */
 __attribute__((weak))
 unsigned long do_go_exec (ulong (*entry)(int, char * const []), int argc, char 
* const argv[])
@@ -67,6 +69,8 @@ U_BOOT_CMD(
  passing 'arg' as arguments
 );
 
+#endif
+
 U_BOOT_CMD(
reset, 1, 0,do_reset,
Perform RESET of the CPU,
diff --git a/include/config_cmd_defaults.h b/include/config_cmd_defaults.h
index 6adebdb..79c0495 100644
--- a/include/config_cmd_defaults.h
+++ b/include/config_cmd_defaults.h
@@ -11,6 +11,7 @@
 
 #define CONFIG_CMD_BOOTM 1
 #define CONFIG_CMD_EXPORTENV 1
+#define CONFIG_CMD_GO 1
 #define CONFIG_CMD_IMPORTENV 1
 
 #endif
-- 
1.7.4.1

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH 01/22] mkimage: Add OMAP boot image support

2011-03-03 Thread Bedia, Vaibhav
Aneesh,

On Tuesday, March 01, 2011 8:34 PM, Bedia, Vaibhav wrote:
 On Tuesday, March 01, 2011 8:20 PM, V, Aneesh wrote:
 
 For OMAP4:
 1. An 8 byte GP header is enough for booting from external
 MMC FAT partition 
 2. A dummy CH with a dummy CHSETTINGS is essential for booting
 from the RAW partition of eMMC or external MMC. This
 works for FAT booting too. 
 3. A full configuration with proper CHSETTINGS and CHRAM will
 help us in directly booting from SDRAM avoiding the SPL,
 but this is not supported on all revisions of OMAP3/4
 
 IMHO, let's have one image type(what John has created now) for
 (1) and (2). It doesn't really harm to have 512 bytes of
 additional header attached to your image when it makes it
 suitable for different types of booting.
 
 For 3, if that is supported in U-Boot in future, we will need
 a new image type, maybe something like omapchimage.
 
 Let me know if you had any special considerations for your
 SoC. 
 
 I will have to check if the additional 512 bytes will cause a
 problem for TI81XX GP devices. We haven't tried with the extra
 512 bytes yet.  
 

I checked the image with the additional 512bytes on TI81XX. It does not work.

If its fine with you I'll work on using a version flag for attaching the 
512byte.
How about something on the lines of what was done for imximage did recently?

Regards,
Vaibhav
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] uboot for MIPS: need help to skip relocate uboot and start uboot from RAM

2011-03-03 Thread Wolfgang Denk
Dear Pandurang Kale,

In message AANLkTinTqxJPU9Gwye_8pT2PcUxR8E36=zm78ypc1...@mail.gmail.com you 
wrote:

 For MIPS I do not find the TEXT_BASE symbol, there is SYS_CFG_MONITOR_BASE

Please check again. MIPS uses CONFIG_SYS_TEXT_BASE like all other
architectures.

 which it uses to relocate the code from the define symbol to high RAM
 address. how can I avoid this?  As I see we have a switch defined for ARM,

You should not try to avoid this.  It is a useful feature, even if you
load U-Boot to RAM separately.

 CONFIG_SKIP_RELOCATE_UBOOT,  to skip the code relocation I cant find a
 similar instance in MIPS code. Can you please throw some light on getting
 the TEXT_BASE setting correctly for MIPS code? how can I do that?

You did not understand what I wrote:

   I can see there is a switch for ARM processor,
  CONFIG_SKIP_RELOCATE_UBOOT,
 
  Are you looking at recent code and working boards?
 
 I have recent uboot code for MIPS and I cant find any similar switch for
 MIPS codebase. arch/mips/lib/board.c and arch/mips/cpu/start.S

I meant: do you see CONFIG_SKIP_RELOCATE_UBOOT in recent ARM code, on
working (compilable) ARM boards?

  Do do not want to skip relocation.  U-Boot may need to auto-adjust
  it's start address dynamically, depending on configuration, system
  requirements and/or environment settings.
 
 The uboot is already loaded in the RAM (by the primary boot loader) so I
 dont want uboot to again relocate itself from one location of RAM to its
 predefined high-memory region in RAM which I have explained in my first
 mail.

Please re-read what I wrote.  In general, U-Boot's load address cannot
be determined at compile time, at least not without crippeling it from
some interesting features.  You should really not try doing things
differently to everybody else.  We had similar discussins not so long
ago for AMR, so please just re-read this in the archives.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH, MD: Wolfgang Denk  Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH 1/1] MX5: Enable flat-device-tree support on mx51/53 evk board

2011-03-03 Thread Jason Liu
Hi, Stefano,

2011/2/21 Jason Liu r64...@freescale.com:
 device tree for uboot arm support has already been enabled
 in the master branch. This patch enable device tree support
 for mx51/53 evk board for DT test.

 Signed-off-by: Jason Liu r64...@freescale.com
 ---
  include/configs/mx51evk.h |    3 +++
  include/configs/mx53evk.h |    3 +++
  2 files changed, 6 insertions(+), 0 deletions(-)

ping.


 ___
 U-Boot mailing list
 U-Boot@lists.denx.de
 http://lists.denx.de/mailman/listinfo/u-boot

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH 1/1] MX53: drop config.mk from mx53evk

2011-03-03 Thread Jason Liu
Hi, Stefano,

2011/2/23 Jason Liu r64...@freescale.com:
 The config.mk file in board directory is now obsolete and
 should be removed. Add option for the IMX image into
 boards.cfg

 Signed-off-by: Jason Liu r64...@freescale.com
 ---

ping..


 ___
 U-Boot mailing list
 U-Boot@lists.denx.de
 http://lists.denx.de/mailman/listinfo/u-boot

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


Re: [U-Boot] [PATCH V2 1/1] MX53: support for freescale MX53LOCO board

2011-03-03 Thread Jason Liu
Hi, Stefano,

2011/2/23 Jason Liu r64...@freescale.com:
 This patch add initial support for freescale MX53LOCO board.
 Network(FEC),SD/MMC, UART have been supported by this patch.

 Signed-off-by: Jason Liu r64...@freescale.com

 ---
 Changes for v2:
 - remove config.mk, instead add CONFIG_ options in boards.cfg
 - fix copyright issue, use freescale copyright.
 - rebase on u-boot-imx/next branch and resend.
 ---

ping..


 ___
 U-Boot mailing list
 U-Boot@lists.denx.de
 http://lists.denx.de/mailman/listinfo/u-boot

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


[U-Boot] DSN: failed (Delivery reports about your e-mail)

2011-03-03 Thread Mailbot for etexusa . com

This is a Delivery Status Notification (DSN).

I was unable to deliver your message to
c...@bigstring.com.

I said 
  RCPT TO:c...@bigstring.com

And they gave me the error;
  554 5.7.1 c...@bigstring.com: Recipient address rejected: Email not 
Found/Disabled

 
Reporting-MTA: dns; etexusa.com
Final-Recipient: RFC822; coo@bigstring.com
Action: failed
Status: 5.0.0
Received: from lists.denx.de ([122.178.168.174]) by etexusa.com for c...@bigstring.com; Thu, 3 Mar 2011 22:34:23 -0800
From: u-boot@lists.denx.de
To: c...@bigstring.com
Subject: Delivery reports about your e-mail
Date: Fri, 4 Mar 2011 12:03:20 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary==_NextPart_000_0013_BD601A83.E32D8D8B
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot