Quoting Fabio Estevam :
> Hi Stefano,
>
Hi Fabio,
> I think that the BOOT_FROM command can be removed, right?
No, we can't if the processor boots from OneNand device. According to
the manual,
the offset must be set to 0x100 instead of 0x400.
>
> We can flash the same binary on a SD or NAND
Hi Richard,
> I a world post-ppc-relocation-patch, with gd->reloc_off removed,
>
> I seem to have lost my way of figuring out uboot's address in RAM at run time.
> Previously, I am able to use (gd->reloc_off+CONFIG_SYS_MONITOR_BASE) to get
> the answer.
>
> Knowing the address is very useful for
Support for LZARI compression mode was added based on a MTD CVS
snapshot of March 13, 2005. However, fs/jffs2/compr_lzari.c contains
contradictory licensing terms: the original copyright clause says "All
rights reserved. Permission granted for non-commercial use.", but
later reference to the file '
Support for LZARI compression mode was added based on a MTD CVS
snapshot of March 13, 2005. However, fs/jffs2/compr_lzari.c contains
contradictory licensing terms: the original copyright clause says "All
rights reserved. Permission granted for non-commercial use.", but
later reference to the file '
When malloc() was called before it was properly initialized
(as would happen if when used before relocation to RAM) it returned
random, non-NULL values, which called all kinds of difficult to debug
subsequent errors.
Make sure to return NULL when initialization was not done yet.
Signed-off-by: Wo
In message <1263551089-26100-1-git-send-email...@denx.de> I wrote:
> Support for LZARI compression mode was added based on a MTD CVS
> snapshot of March 13, 2005. However, fs/jffs2/compr_lzari.c contains
> contradictory licensing terms: the original copyright clause says "All
> rights reserved. Per
On Friday 15 January 2010 05:25:17 Wolfgang Denk wrote:
> + if ((mem_malloc_start == 0) && (mem_malloc_end ==0)) {
missing space ? "==0" -> "== 0" ?
-mike
signature.asc
Description: This is a digitally signed message part.
___
U-Boot mailing list
U-B
Hi Stefano,
...
> > I think that the BOOT_FROM command can be removed,
> right?
>
> No, we can't if the processor boots from OneNand device.
> According to
> the manual,
Yes, it is still the same binary, but just needs a different offset.
> the offset must be set to 0x100 instead of 0x40
Dear Mike Frysinger,
In message <201001150539.16650.vap...@gentoo.org> you wrote:
>
> On Friday 15 January 2010 05:25:17 Wolfgang Denk wrote:
> > + if ((mem_malloc_start == 0) && (mem_malloc_end ==0)) {
>
> missing space ? "==0" -> "== 0" ?
Right. Will fix this then applying.
Thanks for catch
I have pulled these two commits into arm/master
Thanks
Tom
Minkyu Kang wrote:
> Dear Tom,
>
> The following changes since commit 33bf447477ff38eda46529b346677856b53e0f87:
> kevin.morf...@fearnside-systems.co.uk (1):
> Add a unified s3c24x0 header file
>
> are available in the git repos
Hi Stefan,
In October 09 month, I had asked whether U-boot supports M29W128GH, a CFI
compilant chip and I got a yes reply. Please refer below URL for reference.
http://www.mail-archive.com/u-boot@lists.denx.de/msg24531.html.
So I have used Uboot for my PPC440 based board.
When I flashed U-boot
SPEAr320 SoC support contains basic spear320 support along with the
usage of following drivers
- serial driver(UART)
- i2c driver
- smi driver
- nand driver(FSMC)
- usbd driver
- emi driver(cfi support)
Signed-off-by: Vipin
---
MAKEALL |1 +
Makefile
SPEAr300 SoC support contains basic spear300 support along with the
usage of following drivers
- serial driver(UART)
- i2c driver
- smi driver
- nand driver(FSMC)
- usbd driver
Signed-off-by: Vipin
---
MAKEALL |1 +
Makefile|3 ++
board/spe
SPEAr310 SoC support contains basic spear310 support along with the
usage of following drivers
- serial driver(UART)
- i2c driver
- smi driver
- nand driver(FSMC)
- usbd driver
- emi driver(cfi support)
Signed-off-by: Vipin
---
MAKEALL |1 +
Makefile
This patch adds the support to read and write mac id from i2c
memory.
For reading:
if (env contains ethaddr)
pick env ethaddr
else
pick ethaddr from i2c memory
For writing:
chip_config ethaddr XX:XX:XX:XX:XX:XX writes the mac id
in i2
SPEAr Architecture support added. It contains the support for
following SPEAr blocks
- Timer
- System controller
- Misc registers
Signed-off-by: Vipin
---
cpu/arm926ejs/spear/Makefile | 52 ++
cpu/arm926ejs/spear/reset.c | 54 +++
cpu/arm926ejs/spear/
README.spear contains information about SPEAr architecture and
build options etc
Signed-off-by: Vipin
---
doc/README.spear | 48
1 files changed, 48 insertions(+), 0 deletions(-)
create mode 100644 doc/README.spear
diff --git a/doc/README.spea
SPEAr SoCs contain an FSMC controller which can be used to interface
with a range of memories eg. NAND, SRAM, NOR.
Currently, this driver supports interfacing FSMC with NAND memories
Signed-off-by: Vipin
---
drivers/mtd/nand/Makefile |1 +
drivers/mtd/nand/spr_nand.c |
Hello Tom,
Please consider the patchset version5 for mainline inclusion
This patchset contains the version5 for SPEAr SoCs support
Modifications
1. include/configs contins spear3xx.h for SPEAR300, SPEAR310 and SPEAr320
variants
2. include/configs contins spear6xx.h for SPEAR600 and any variants i
SPEAr600 SoC support contains basic spear600 support along with the
usage of following drivers
- serial driver(UART)
- i2c driver
- smi driver
- nand driver(FSMC)
- usbd driver
Signed-off-by: Vipin
---
MAKEALL|1 +
Makefile
SPEAr SoCs contain a synopsys usb device controller.
USB Device IP can work in 2 modes
- DMA mode
- Slave mode
The driver adds support only for slave mode operation of usb
device IP. This driver is used along with standard USBTTY
driver to obtain a tty interface over USB on the host
Signed-off-by
SPEAr310 and SPEAr320 SoCs contain an EMI controller to interface
Paraller NOR flashes. This patch adds the support for this IP
The standard CFI driver is used to interface with NOR flashes
Signed-off-by: Vipin
---
board/spear/common/spr_misc.c| 59 ++
SPEAr SoCs contain a serial memory interface controller. This
controller is used to interface with spi based memories.
This patch adds the driver for this IP.
Signed-off-by: Vipin
---
drivers/mtd/Makefile |1 +
drivers/mtd/spr_smi.c| 523 +
SPEAr SoCs contain a synopsys i2c controller.
This patch adds the driver for this IP.
Signed-off-by: Vipin
---
drivers/i2c/Makefile |1 +
drivers/i2c/spr_i2c.c| 331 ++
include/asm-arm/arch-spear/spr_i2c.h | 146 ++
Hi Alexander
Welcome on board :-)
Pls see my in lined answers
> -Original Message-
> From: Alexander Holler [mailto:hol...@ahsoftware.de]
> Sent: Friday, January 15, 2010 4:15 AM
> To: Prafulla Wadaskar
> Subject: Re: open u-boot on the DockStar
>
> Hello again,
>
> through painful de
File at91_pio.h inserts following line:
> +#define AT91_PORTPIN(PORT, PIN) ((0x0##PORT - 10)*32+((PIN) & 0x1F))
this is wrong, sorry about this.
I will resend this patch as soon as posible.
In the meantime you can manually change the line to
#define AT91_PORTPIN(PORT, PIN) ((0x0##PORT - 9
Fabio Estevam wrote:
> Hi Stefano,
>
Hi Fabio,
> Yes, it is still the same binary, but just needs a different offset.
>
This is not what I have understood from the manual. In the chapter
regarding the flash header ("Flash header structure", figure 2.9), there
is the field "app_dest_ptr". This
Dear John,
In message <1263357841-5100-1-git-send-email-jcri...@gmail.com> you wrote:
> The i.MX25 has the same ARM core and shares some ip blocks
> with i.MX27 but also borrows from i.MX31.
>
> The TX25 is an i.MX25 based board. It has only NAND flash
> so this port includes nand_spl and mtd/na
Dear John Rigby,
In message <1263357841-5100-1-git-send-email-jcri...@gmail.com> you wrote:
> The i.MX25 has the same ARM core and shares some ip blocks
> with i.MX27 but also borrows from i.MX31.
>
> The TX25 is an i.MX25 based board. It has only NAND flash
> so this port includes nand_spl and
Dear John Rigby,
In message <1263357841-5100-10-git-send-email-jcri...@gmail.com> you wrote:
> This is an i.MX25 base board with only NAND
> so it uses nand_spl to boot.
>
> Signed-off-by: John Rigby
>
> Tune configuration, add support for (redundant) environment in NAND.
> Signed-off-by: Wolfg
From a1d1f6fa9b579c4a766eea45c01224edd536880c Mon Sep 17 00:00:00 2001
From: Richard Retanubun
Date: Fri, 15 Jan 2010 10:06:06 -0500
Subject: [PATCH] PPC: Record uboot's relocated address in RAM and show in
bdinfo.
This commit uses gd->relocaddr variable to store uboot's relocated
address in RA
Dear Stefano Babic,
In message <1263376259-29764-2-git-send-email-sba...@denx.de> you wrote:
> This patch adds support for "imximage" (MX Boot Image)
> to the mkimage utility. The imximage is used on the Freescales's
> MX.51 processors.
>
> Further details under doc/README.imximage.
>
> This pat
Wolfgang Denk wrote:
> Can you please check the status of this patch:
> http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/61758
>
> Thanks.
>
> Best regards,
>
> Wolfgang Denk
>
Hello,
Wofgang, I believe at the time Ben made the comment that my patch's usage of
things like these:
-#if
Hi Richard,
> From a1d1f6fa9b579c4a766eea45c01224edd536880c Mon Sep 17 00:00:00 2001
> From: Richard Retanubun
> Date: Fri, 15 Jan 2010 10:06:06 -0500
> Subject: [PATCH] PPC: Record uboot's relocated address in RAM and show in
> bdinfo.
>
> This commit uses gd->relocaddr variable to store uboot'
Ok, I now understand your suggestion. I still think the kernel naming
is confusing since it does not match internal Freescale naming, but of
course that only exists in Redboot source so I suppose it does not
matter.
About your 5121 question, it is Freescale internal version 1.1 or
using the kerne
Detlev Zundel wrote:
>
> Please excuse my ignorance, but why not simply remove the #ifdef
> CONFIG_AMIGAONEG3SE in board_init_f? Actually I was hoping to remove
> the Amigaone special case.
>
> Cheers
> Detlev
>
I prefer getting the data from board_init_r because we really are running from
Hello Tom,
>>>
>>>
>>> +#include
>>> +#include
>>> +#include
>>> +
>>> +int board_init(void)
>>> +{
>>> + return spear_board_init(MACH_TYPE_SPEAR300);
>>> Does this need a new mach type ?
>>> I see there isn't a SPEAR310 define in mach-types.
>>
>> Actually, spear310 and spear320 are varian
* insert AT91 SoC access using c-stuctures
Signed-off-by: Jens Scharsig
---
diff --git a/cpu/arm926ejs/at91/at91sam9m10g45_devices.c
b/cpu/arm926ejs/at91/at91sam9m10g45_devices.c
index 98d90f2..274a135 100644
--- a/cpu/arm926ejs/at91/at91sam9m10g45_devices.c
+++ b/cpu/arm926ejs/at91/at91sam9m10
Hallo,
I have a question concerning standalone programs based on u-boot and GPL, since
I'm not really sure whether the way how the u-boot source files are set up
allows GPL free standalone programs.
u-boot allows the use of standalone applications which can be loaded and
executed by u-boot. Th
On Tue, Jan 12, 2010 at 09:44:00PM -0700, John Rigby wrote:
> From: Wolfgang Denk
>
> env_nand.c would crash silently if a malloc() for the environment
> buffers failed; make it print an error message and fail gracefully,
> i. e. use the default environment then.
>
> Signed-off-by: Wolfgang Denk
On Fri, Jan 15, 2010 at 09:49:30AM -0700, John Rigby wrote:
> Ok, I now understand your suggestion. I still think the kernel naming
> is confusing since it does not match internal Freescale naming, but of
> course that only exists in Redboot source so I suppose it does not
> matter.
I'd like to s
On Tue, Jan 12, 2010 at 09:43:55PM -0700, John Rigby wrote:
> struct fsl_nfc_regs {
> - u32 main_area0[128]; /* @0x000 */
> - u32 main_area1[128];
> - u32 main_area2[128];
> - u32 main_area3[128];
> - u32 spare_area0[4];
> - u32 spare_area1[4];
> - u32 spare_area2[4];
>
Thanks for the input Scott.
On Fri, Jan 15, 2010 at 4:13 PM, Scott Wood wrote:
> On Tue, Jan 12, 2010 at 09:43:55PM -0700, John Rigby wrote:
>> struct fsl_nfc_regs {
>> - u32 main_area0[128]; /* @0x000 */
>> - u32 main_area1[128];
>> - u32 main_area2[128];
>> - u32 main_area3[128
Not sure, I have not had access to the original freescale authored
kernel driver for sometime so I'm not sure what info is embedded
there.
My naming came from the Redboot sources which were authored by
Freescaler's. Also the numbering is consistent with what I recall
from my days there.
Perhaps
John Rigby wrote:
> No I have not tested on mx27. I don't have any hw. If someone could
> test it that would be great. Also I really don't know if the syndrome
> stuff is needed.
I was just about to comment on that. :-)
At a first glance it looks like you'll need either some custom read/write
What kind of CPU usage are you seeing? I am throughput of ~1.9MBs for writes
on a Samsung K9WBG08U1M 4GB with 4K page but with high cpu usage.
Nick Thompson-9 wrote:
>
> On 09/12/09 11:02, Wolfgang Denk wrote:
>> Dear Nick Thompson,
>>
>> In message <4b1e71d9.6080...@ge.com> you wrote:
>>> Im
On 07.01.2010 19:31, Ben Warren wrote:
> Dirk Behme wrote:
>> There are boards out there that do not have network support in
>> U-Boot (CONFIG_CMD_NET not set), but they do so in Linux. This
>> makes it desirable to be able to port network configuration (like
>> the IP address) to the Linux kernel.
47 matches
Mail list logo