Le 05/09/2011 21:50, Marek Vasut a écrit :
Le 02/09/2011 13:57, Marek Vasut a écrit :
On Friday, September 02, 2011 01:43:39 PM Simon Guinot wrote:
On Fri, Sep 02, 2011 at 12:23:54PM +0200, Marek Vasut wrote:
On Friday, September 02, 2011 12:22:05 PM Simon Guinot wrote:
Hi Hong,
On Mon, Aug
On Tuesday, September 06, 2011 08:19:26 AM Albert ARIBAUD wrote:
Le 05/09/2011 21:50, Marek Vasut a écrit :
Le 02/09/2011 13:57, Marek Vasut a écrit :
On Friday, September 02, 2011 01:43:39 PM Simon Guinot wrote:
On Fri, Sep 02, 2011 at 12:23:54PM +0200, Marek Vasut wrote:
On Friday,
Hi, Mike and Wolfgang,
2011/9/1 Mike Frysinger vap...@gentoo.org:
On Thursday, September 01, 2011 01:52:46 Macpaul Lin wrote:
[... skipped and will discuss these later]
+void board_init_f(ulong bootflag)
+{
...
+ /* Pointer is writable since we allocated a register for it */
+ gd
Hello Wolfgang,
On Mon, 5 Sep 2011 21:51:33 +0200
Wolfgang Denk w...@denx.de wrote:
Fix build warning:
Configuring for jadecpu board...
mb86r0xgdc.c: In function 'dsp_init':
mb86r0xgdc.c:60: warning: unused variable 'i'
Signed-off-by: Wolfgang Denk w...@denx.de
Cc: Anatolij Gustschin
Hello Wolfgang,
The following changes since commit 99ffccbd3e5b7bc715e2eed6ea6d36f4020b56d8:
Flush cache after the OS image is loaded into the memory. (2011-09-05
16:07:44 +0200)
are available in the git repository at:
git://git.denx.de/u-boot-video.git master
Wolfgang Denk (1):
On 09/06/2011 06:29 AM, Teemu Keskinarkaus wrote:
Hi,
Hi Teemu,
-Original Message- From: Stefano Babic
[mailto:sba...@denx.de]
Take into account that the u-boot.bin in the last release must be
stored on the NOR flash of your board - the board has both NAND and
NOR flash. The
We have received a request to subscribe you to the discussion
annou...@tigris.org. If you wish to receive email notifications from this
discussion, please reply to this message.
If not, ignore this email.
___
U-Boot mailing list
U-Boot@lists.denx.de
On 09/05/2011 09:02 PM, Fabio Estevam wrote:
Hi,
Hi Fabio,
On a MX31PDK the only boot media is NAND flash, so I was trying to get
rid of the
conditional setting of CONFIG_SYS_TEXT_BASE.
CONFIG_NAND_SPL is set in nand_spl/board/freescale/mx31pdk/Makefile.
,so I tried the following:
On 09/05/2011 08:02 PM, Fabio Estevam wrote:
Add the initial support for MX25PDK booting from SD card via internal boot.
Signed-off-by: Fabio Estevam fabio.este...@freescale.com
---
Hi Fabio,
diff --git a/board/freescale/mx25pdk/mx25pdk.c
b/board/freescale/mx25pdk/mx25pdk.c
new file
(splitting this discussion between the patch and my longer term RFC,
here I follow the patch, keeping the subject line unchanged)
Le 06/09/2011 08:40, Marek Vasut a écrit :
This is completely out of scope for this patch. My proposal would be to merge
this, then start mucking with this moving
(splitting this discussion between the patch question and longer term
RFC, here I follow the RFC and update the subject line accordingly)
Seems like we're having two problems there:
1) at least some cpus or cores (xscale) do not implement all of what was
thought to be armv5 cache operations,
Hello U-booters
Hopefully someone can help me. I'm working on a tx25 target.
I need to start my linux system from nand flash. i can load the kernel-uImage
from tftp and start it directly without any problem. I stored the image to the
a mtd partition.
nand write.jffs2 0x8100 kernel1
To
NAND is sufferered from Bad blocks and bit errors. Thats why usually
exists a bad block handling and an ECC. Am I wrong, that I miss both
on uboot for it's environment?
Or is my uboot just to old (2010.06) and newer versions handle this?
Is there a special setting necessary to handle this?
I see
On Tuesday, September 06, 2011 01:43:33 PM Albert ARIBAUD wrote:
(splitting this discussion between the patch question and longer term
RFC, here I follow the RFC and update the subject line accordingly)
Seems like we're having two problems there:
1) at least some cpus or cores (xscale)
On Tuesday, September 06, 2011 01:38:46 PM Albert ARIBAUD wrote:
(splitting this discussion between the patch and my longer term RFC,
here I follow the patch, keeping the subject line unchanged)
Le 06/09/2011 08:40, Marek Vasut a écrit :
This is completely out of scope for this patch. My
Add support for SERIAL MULTI for uartlite.
Signed-off-by: Michal Simek mon...@monstr.eu
---
v2: Use in/out_be32 functions
---
common/serial.c | 14
drivers/serial/serial_xuartlite.c | 137 -
include/serial.h |7
Enable support for SERIAL_MULTI.
Microblaze can use uart16550 and uartlite drivers.
Signed-off-by: Michal Simek mon...@monstr.eu
---
arch/microblaze/lib/board.c |4
include/configs/microblaze-generic.h |2 ++
include/serial.h |2 +-
3 files changed,
On Tuesday, September 06, 2011 04:16:59 PM Arno Steffen wrote:
NAND is sufferered from Bad blocks and bit errors. Thats why usually
exists a bad block handling and an ECC. Am I wrong, that I miss both
on uboot for it's environment?
Or is my uboot just to old (2010.06) and newer versions
On Tuesday, September 06, 2011 04:05:23 PM philipp zaugg wrote:
Hello U-booters
Hopefully someone can help me. I'm working on a tx25 target.
I need to start my linux system from nand flash. i can load the
kernel-uImage from tftp and start it directly without any problem. I
stored the
Hi Arno,
On Tue, Sep 06, 2011 at 04:16:59PM +0200, Arno Steffen wrote:
NAND is sufferered from Bad blocks and bit errors. Thats why usually
exists a bad block handling and an ECC. Am I wrong, that I miss both
on uboot for it's environment?
U-Boot 2010.06 already has bad block handling in the
Most 85xx boards can be built as a 32-bit or a 36-bit. Current code sometimes
displays which of these is actually built, but it's inconsistent. This is
especially problematic since the default build for a given 85xx board can
be either one, so if you don't see a message, you can't always know
The macro CONFIG_ENABLE_36BIT_PHYS is used to indicate that the given SOC is
capable of 36-bit physical addresses, even if such large addresses are not
used. On two boards, this macro was enabled only when building a 36-bit
image.
Signed-off-by: Timur Tabi ti...@freescale.com
---
Hi Sandeep, Joel,
On Sun, Sep 4, 2011 at 11:10 PM, s-paul...@ti.com wrote:
From: Joel A Fernandes agnel.j...@gmail.com
Read directly from OMAP_GPIO_DATAOUT to get the output state of the GPIO pin
Signed-off-by: Joel A Fernandes agnel.j...@gmail.com
Signed-off-by: Jason Kridner
Tuning some IO settings for better performance and power.
And consolidate all such IO settings at one place.
Signed-off-by: Aneesh V ane...@ti.com
---
V2:
* Add one more IO setting(in CONTROL_LPDDR2IOi_3) that was
missing in the V1
* Move all LPDDR2IO regs related defines to omap4.h from
SDRAM init was not working on ES1.0 due to a programming
error. A pointer that was passed by value to a function
was set in function emif_get_device_details(), but the effect
wouldn't be seen in the calling function. The issue came
out while testing for ES1.0 because ES1.0 doesn't have any
SDRAM
Factor out common parts from omap4_sdp4430.h and omap4_panda.h
into a new file omap4_common.h
Signed-off-by: Aneesh V ane...@ti.com
---
V2:
* Rebased on latest HEAD of u-boot-ti master
---
include/configs/omap4_common.h | 275 +++
This patch added a build warning like this:
gpio.c: In function 'omap_get_gpio_dataout':
gpio.c:161: warning: assignment discards qualifiers from pointer target
type
The fix is this:
We will have to co ordinate the best way to move forward on this.
Sanjeev submitted a patch set to
On Mon, Sep 5, 2011 at 12:37 PM, Wolfgang Denk w...@denx.de wrote:
Out of tree building of the harmony and seaboard boards failed
like this:
Configuring for harmony board...
Assembler messages:
Fatal error: can't create
/work/wd/tmp-arm/board/nvidia/harmony/../common/board.o: No such file
Am 06.09.2011 16:24, schrieb Marek Vasut:
On Tuesday, September 06, 2011 04:05:23 PM wrote:
Hello U-booters
Hopefully someone can help me. I'm working on a tx25 target.
I need to start my linux system from nand flash. i can load the
kernel-uImage from tftp and start it directly without any
On Mon, Sep 5, 2011 at 11:25 AM, s-paul...@ti.com wrote:
From: Sandeep Paulraj s-paul...@ti.com
This patch removes a hardcoded MAC address
Signed-off-by: Sandeep Paulraj s-paul...@ti.com
---
include/configs/omap3_beagle.h | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff
Has anyone had any experience with a P4080 target which has more than 1
sodimm slot on each controller? I'm having some difficulties accessing
memory on the higher order dimms, but the SPD data are correctly
enumerated by the FSL ddr3 code.
Just wondering if this is a known problem before I
I don't remember seeing any errors/warnings after applying my patches... on all
boards listed in the cover letter.
...except for SMSC95x - in case of Panda.
Infact, once the patches are applied, this function shouldn't even exist.
~sanjeev
From:
Avoid the usage of extern in C file as pointed out by checkpatch.
Signed-off-by: Fabio Estevam fabio.este...@freescale.com
---
Changes since v5:
- Only place mx25_uart1_init_pins inside sys_proto.h
Changes since v4:
- No changes
Changes since v3:
- Place mx25_uart1_init_pins inside sys_proto.h
Add the initial support for MX25PDK booting from SD card via internal boot.
Signed-off-by: Fabio Estevam fabio.este...@freescale.com
---
Changes since v5:
- Include sys_proto.h
Changes since v4:
- No changes
Changes since v3:
- No changes
Changes since v2:
- No changes
Changes since v1:
- Keep
On Tue, Sep 6, 2011 at 12:07 PM, v...@vsbe.com wrote:
-- Forwarded message --
From: Rob Herring robherri...@gmail.com
Date: Tue, Jun 21, 2011 at 2:33 PM
Subject: [U-Boot] [PATCH 3/5] scsi/ahci: ata id little endian fix
To: u-boot@lists.denx.de
Cc: Rob Herring
On Tuesday, September 06, 2011 02:41:47 馬克泡 wrote:
2011/9/1 Mike Frysinger vap...@gentoo.org:
On Thursday, September 01, 2011 01:52:46 Macpaul Lin wrote:
+void board_init_f(ulong bootflag)
+{
...
+ /* Pointer is writable since we allocated a register for it */
+ gd = (gd_t *)
On Mon, Sep 5, 2011 at 6:25 AM, Sanjeev Premi pr...@ti.com wrote:
This patch fixes the warning dure to recent changes to the board
configuration:
cmd_i2c.o cmd_i2c.c -c
cmd_i2c.c:109:1: warning: missing braces around initializer
cmd_i2c.c:109:1: warning: (near initialization for
I'm using version 1.3.4.
It looks like I'm stuck with 4MB of flash when I fire up qemy-system-mips
with:
qemu-system-mips -M mips -L . -pflash flash -monitor null -nographic
No matter how I big the image is, nor if I change CFG_MAX_FLASH_BANKS to
more than 1 (it hangs), or CFG_MAX_FLASH_SECT
On Mon, Sep 05, 2011 at 02:37:29PM +0200, Wolfgang Denk wrote:
Signed-off-by: Wolfgang Denk w...@denx.de
Cc: Albert ARIBAUD albert.u.b...@aribaud.net
Cc: George G. Davis gda...@mvista.com
Ack, Thanks!
--
Regards,
George
---
MAINTAINERS |4 -
board/gcplus/Makefile
Playing some post-vacation catch-up
I just want to address this point real quick. Take a look at the board
conversion patches,
it's not a big deal to hook in to this, it's just a matter of calling the init
function, on top of any
normal hook up work you had to do.
--
Tom
Add generic header files support for nds32 architecture.
Cache, ptregs, data type and other definitions are included.
Signed-off-by: Macpaul Lin macp...@andestech.com
---
Changes for v1-v4:
- Code cleanup and style formatting.
Changes for v5-v6:
- This patch also updated the following
Add NDS32 support into common header file.
Signed-off-by: Macpaul Lin macp...@andestech.com
---
Changes for v1-v7:
- No change
Changes for v8:
- Fix the patch according to dependency of x86's Fix
Changes for v9-v12:
- No change
include/common.h |4
1 files changed, 4
Add N1213 cpu core (N12 Core family) support for NDS32 arch.
This patch includes start.S for the initialize procedure of N1213.
Start procedure:
start.S will start up the N1213 CPU core at first,
then jump to SoC dependent lowlevel_init.S and
watchdog.S to configure peripheral devices.
SoC ag101 is the first chip using NDS32 N1213 cpu core.
Add header file of device offset support for SoC ag101.
Add main function of SoC ag101 based on NDS32 n1213 core.
Add lowlevel_init.S and other periphal related code.
This version of lowlevel_init.S also replace hardcode value
by MARCO
Add Makefile, board.c, interrupts.c and bootm.c functions
to nds32 architecture.
Signed-off-by: Macpaul Lin macp...@andestech.com
---
Changes for v1-v4:
- code clean up and formatting style.
Changes for v5-v6:
- board.c
- Do some clean up and add code
- Remove display banner which
Add support of NDS32 to common commands bdinfo, bootm, and image format.
Signed-off-by: Macpaul Lin macp...@andestech.com
---
Changes for v1-v6:
- Code clean up
Changes for v7-v9:
- No Change.
Changes for v10:
- fix up according to the changes in master tree.
Changes for v11:
- No Change.
Add standalone program related support for nds32 architecture.
Signed-off-by: Macpaul Lin macp...@andestech.com
---
Changes for v1-v6:
- code clean up.
Changes for v7-v11:
- No change.
Changes for v12:
- clean up link script.
examples/standalone/nds32.lds | 56
Documents and READMEs for NDS32 architecture.
It patch also provides usage of SoC AG101 and board ADP-AG101.
Signed-off-by: Macpaul Lin macp...@andestech.com
---
Changes for v1-v10:
- The patch of documentation was not included.
Changes for v11:
- Add the documents of NDS32, ag101, N1213.
Add evaluation board adp-ag101 configuration file adp-ag101.h.
Add adp-ag101.c board config and related settings.
Add board adp-ag101 into boards.cfg
Signed-off-by: Macpaul Lin macp...@andestech.com
---
Changes for v1-v4:
- code clean up
Changes for v5-v6:
- Refine the definitions and
[This didn't go to the list due to too many recipients so I'm
sending it again]
Hi,
Here are some problems I see currently with the today's mainline
U-boot not seen with v2011.06 Just sharing them here.
HEAD: 05f64ae996a51e32ef47e0db2c806e704606606e: led: remove camel
casing of led identifiers
Email account User
Due to recent trace by our admin staff, we have noticed that different
computers have logged into your email, and multiple passwords failures
were present before the login. Therefore your account has been limited.
Access our portal management for the restoration of auditing
Hi,
I also see problems with eMMC with latest U-Boot (well, changes since
2011.03). I haven't had a chance to look at them closely though. From
memory it reads the device capabilities but doesn't seem to get a
useful response.
Regards,
Simon
On Tue, Sep 6, 2011 at 8:27 PM, Joel A Fernandes
On Monday, September 05, 2011 17:40:13 Luka Perkov wrote:
Patch fixes this issue:
fw_env.c: In function ‘fw_setenv’:
fw_env.c:492:5: warning: format ‘%u’ expects argument of type ‘unsigned
int’, but argument 3 has type ‘size_t’ [-Wformat] fw_env.c: In function
‘flash_write_buf’:
This is sitting here for more than 2 months, could someone please ACK
and/or apply.
Helmut
--
Scanned by MailScanner.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
54 matches
Mail list logo
