I reverted my local change and the directory listing shows no duplicates
anymore which is surprising. An inspection of the generated assembly shows
more or less the same code with the exception of the early branch taken if
'dols' is 0. The 16/8 comparison is still awkward, but at this point I'm not
The following changes since commit c2e5e802ecb7ab668ce9911b210ed68c804b349f:
Merge branch 'master' of git://git.denx.de/u-boot-mips (2013-11-17
14:11:34 -0500)
are available in the git repository at:
git://git.denx.de/u-boot-net.git master
for you to fetch changes up to 2287286be4e268d3d4e
Dear Tom,
In message <20131122205046.GU420@bill-the-cat> you wrote:
>
> So, the last report said that they had a tree missing
> 6ad77d88e57f6ab815ec7e85c5ac329054318c73, but yours can't be. Can you
> add some debug prints and see what's going on? Having
> u8 foo = bar();
> if (a && foo == baz)
On Fri, Nov 22, 2013 at 11:31:29AM -0800, drambo wrote:
> Hello,
>
> If it helps, I would respectfully like to add that I reverted this change
> and it fixes my problem nicely. I'm on an ARM platform (not yet upstreamed
> to u-boot), with a microSD card inserted with valid files on it that I can
>
Hi Tom,
I've collected up some initial patches why I think are pretty
straightforward. buildman passes for all targets I build. The sandbox-only
error in patch 5 is unavoidable without squashing these unrelated patches.
./tools/buildman/buildman -b x86-push2 -s
Summary of 6 commits for 1182 board
The following changes since commit 63c4f17b2f8017d22241522a48c765073b8791b0:
cm_t35: use scf0403 driver (2013-11-12 10:12:07 +0100)
are available in the git repository at:
git://git.denx.de/u-boot-nand-flash.git master
for you to fetch changes up to 2c17e6d1d996a1b8b9325de15f253a13d5877dee:
Hello,
If it helps, I would respectfully like to add that I reverted this change
and it fixes my problem nicely. I'm on an ARM platform (not yet upstreamed
to u-boot), with a microSD card inserted with valid files on it that I can
read on other systems. I have an Oct 16, 2013 version of U-Boot 201
Hi Frank,
On Fri, Mar 1, 2013 at 4:05 AM, Frank Dols wrote:
> [[ ... to get attention again ... see below ...]]
> On 2/8/2013 6:22 PM, Frank Dols wrote:
>> Good afternoon Vipin and Albert,
>> I where wondering, is there any review/update news on the patches I
>> submitted a short while ago?
>>
Hi Mateusz,
On Fri, Nov 22, 2013 at 5:12 AM, Mateusz Zalega wrote:
> On 11/07/13 17:32, Simon Glass wrote:
> > Add driver model support for GPIOs. (...)
>
> Just a thought - what's keeping us from implementing 1:1 GPIO devicetree
> mapping with Linux?
>
Nothing, it is fully compatible with that
On Fri, Nov 22, 2013 at 10:56:05AM +, Marc Zyngier wrote:
> On 22/11/13 01:51, Christoffer Dall wrote:
> > On 21 November 2013 00:59, Marc Zyngier wrote:
> >> A CP15 instruction execution can be reordered, requiring an
> >> isb to be sure it is executed in program order.
> >>
> >> Signed-off-b
On Fri, Nov 22, 2013 at 02:30:27PM +0530, Anup Patel wrote:
> On Fri, Nov 22, 2013 at 2:12 PM, Ian Campbell wrote:
> > On Fri, 2013-11-22 at 09:28 +0530, Anup Patel wrote:
> >> An Independent binary of a secured firmware makes more sense here.
> >> Also, if secured firmware is an independent binar
Hi Christopher,
On Fri, Nov 22, 2013 at 5:56 AM, Christopher Preschern <
christopher.presch...@tugraz.at> wrote:
> Hi Simon,
>
>
> Well I suppose you can use the split version of the bootm command to do
>> this. Something like: 'bootm start ; bootm loados; bootm prep;
>> loadelf ...'
>>
>
> that
Mårten Wikman writes:
>> 0x41069265 is the CP15 ID register value for ARM926. I'd look into how
>> this value ended up where the machine ID should be.
>
> I tried do set the correct machine ID with setenv machid but I get the
> same result even if u-boot says it's using the new machine ID.
Stil
> 0x41069265 is the CP15 ID register value for ARM926. I'd look into how
> this value ended up where the machine ID should be.
I tried do set the correct machine ID with setenv machid but I get the
same result even if u-boot says it's using the new machine ID.
___
Hi Abraham,
Thank you very much for your detailed reply! But I think I can rule
out the three possible problems you mentioned.
1. The cross compiler should be fine. Because I use it all the time to
compile kernel for pandaboard and it has never been a problem
2. I'm doing exactly what you suggeste
On 22/11/13 08:40, Ian Campbell wrote:
> On Thu, 2013-11-21 at 15:04 +, Marc Zyngier wrote:
>> Hi Rob,
>>
>> On 21/11/13 14:28, Rob Herring wrote:
>>> On Thu, Nov 21, 2013 at 2:59 AM, Marc Zyngier wrote:
PSCI is an ARM standard that provides a generic interface that
supervisory softw
Update the CONFIG_BOOTCMD to adopt the common
boot command which parses through USB, MMC and NAND.
This patch is dependent on the series starting with
http://patchwork.ozlabs.org/patch/292986/
Signed-off-by: Dan Murphy
---
include/configs/am43xx_evm.h | 20 +---
1 file changed
Hello,
I'm 2010.06-rc3 which came with a board fitted with an MPC8377 power pc
processor. This version of uboot does not support the mmc controller in the
processor. Does anyone know if support has been added to a later version? Or at
least could someone please point me to a suitable change log
"Mårten Wikman" writes:
> Hello,
>
> I'm bringing up a custom board that includes a mx283 and 64MB DDR2
> memory, now I have some troubles with getting u-boot to properly boot
> the kernel. I have enabled kernel_debugging and with earlyprintk I get
> the following output:
>
> ## Booting kernel fr
Hi Simon,
Well I suppose you can use the split version of the bootm command to do
this. Something like: 'bootm start ; bootm loados; bootm prep;
loadelf ...'
that helped me out - it works. I use the following commands to check and
load my RTOS.
setenv checkrtos 'bootm start 0x4400'
tftp
On 11/07/13 17:32, Simon Glass wrote:
> Add driver model support for GPIOs. (...)
Just a thought - what's keeping us from implementing 1:1 GPIO devicetree
mapping with Linux?
--
Mateusz Zalega
Samsung R&D Institute Poland
___
U-Boot mailing list
U-Boot
Enable FDT support for all Siemens AM335x boards. To support
newer Linux kernels with DT booting.
Signed-off-by: Stefan Roese
Cc: Heiko Schocher
Cc: Roger Meier
Cc: Lukas Stockmann
Cc: Tom Rini
---
include/configs/siemens-am33x-common.h | 4
1 file changed, 4 insertions(+)
diff --git a
(resending *only* to u-boot maillist as earlier message was moderated as below)
[PATCH v1 0/5] mtd: nand: omap: clean omap_gpmc.h headers
Is being held until the list moderator can review it for approval.
The reason it is being held:
Too many recipients to the me
omap_elm.h is a generic header used by OMAP ELM driver for all TI platfoms.
Hence this file should be present in generic folder instead of architecture
specific include folder.
Build tested using: ./MAKEALL -s am33xx -s omap3 -s omap4 -s omap5
Signed-off-by: Pekon Gupta
---
drivers/mtd/nand/omap
Each SoC platform (AM33xx, OMAP3, OMAP4, OMAP5) has its own copy of GPMC related
defines and declarations scattered in SoC platform specific header files
like include/asm/arch-xx/cpu.h
However, GPMC hardware remains same across all platforms thus this patch merges
GPMC data scattered across differe
omap_gpmc.h is a generic header used by OMAP NAND driver for all TI platfoms.
Hence this file should be present in generic folder instead of architecture
specific include folder.
Build tested using: ./MAKEALL -s am33xx -s omap3 -s omap4 -s omap5
Signed-off-by: Pekon Gupta
---
arch/arm/include/as
Currently there are two sets of omap_gpmc.h header files
(a) arch/arm/include/asm/omap_gpmc.h
common header file for all platforms, containing defines and declarations used
by GPMC NAND driver.
(b) arch/arm/include/asm/arch-xx/omap_gpmc.h
SoC platform specific header file containing defines lik
Each SoC platform (AM33xx, OMAP3, OMAP4, OMAP5) has its own copy of GPMC related
defines and declarations scattered in SoC platform specific header files
like include/asm/arch-xx/cpu.h
However, GPMC hardware remains same across all platforms thus this patch merges
GPMC data scattered across differe
OMAP NAND driver can detect Page-size and OOB-size of NAND device from ONFI
params or nand_id[] table. And based on that it defines ECC layout.
This patch
1) removes following board configs used for defining NAND ECC layout
- GPMC_NAND_ECC_LP_x16_LAYOUT (for large page x16 NAND)
- G
omap_elm.h is a generic header used by OMAP ELM driver for all TI platfoms.
Hence this file should be present in generic folder instead of architecture
specific include folder.
Build tested using: ./MAKEALL -s am33xx -s omap3 -s omap4 -s omap5
Signed-off-by: Pekon Gupta
---
drivers/mtd/nand/omap
Currently there are two sets of omap_gpmc.h header files
(a) arch/arm/include/asm/omap_gpmc.h
common header file for all platforms, containing defines and declarations used
by GPMC NAND driver.
(b) arch/arm/include/asm/arch-xx/omap_gpmc.h
SoC platform specific header file containing defines lik
omap_gpmc.h is a generic header used by OMAP NAND driver for all TI platfoms.
Hence this file should be present in generic folder instead of architecture
specific include folder.
Build tested using: ./MAKEALL -s am33xx -s omap3 -s omap4 -s omap5
Signed-off-by: Pekon Gupta
---
arch/arm/include/as
OMAP NAND driver can detect Page-size and OOB-size of NAND device from ONFI
params or nand_id[] table. And based on that it defines ECC layout.
This patch
1) removes following board configs used for defining NAND ECC layout
- GPMC_NAND_ECC_LP_x16_LAYOUT (for large page x16 NAND)
- G
This patch series aims are cleaning and consolidationg GPMC declarations
and macros in common file by:
(1) Merges multiple omap_gpmc.h header files
- arch/arm/include/asm/arch-xx/omap_gpmc.h: for individual SoC platform
- arch/arm/include/asm/arch/omap_gpmc.h: common for all ARM SoC platform
(2
On 22/11/13 01:51, Christoffer Dall wrote:
> On 21 November 2013 00:59, Marc Zyngier wrote:
>> A CP15 instruction execution can be reordered, requiring an
>> isb to be sure it is executed in program order.
>>
>> Signed-off-by: Marc Zyngier
>> ---
>> arch/arm/cpu/armv7/nonsec_virt.S | 1 +
>> 1 f
On 22/11/13 01:54, Christoffer Dall wrote:
> On 21 November 2013 07:04, Marc Zyngier wrote:
>> Hi Rob,
>>
>> On 21/11/13 14:28, Rob Herring wrote:
>>> On Thu, Nov 21, 2013 at 2:59 AM, Marc Zyngier wrote:
PSCI is an ARM standard that provides a generic interface that
supervisory software
On Fri, 2013-11-22 at 14:26 +0530, Anup Patel wrote:
> If you link secure firmware inside u-boot image then we will have to reflash
> or update entire u-boot image whenever we want to update the secure
> firmware.
Only if you make your secure firmware part of u-boot. Nothing says you
have to. You
Add the default RCW(SerDes 0x66_0x16) and PBI configure file for
T2080QDS board, so we can use PBL tool to generate the ramboot
image to support boot from NAND/SPI/SD.
Signed-off-by: Shengzhou Liu
---
Against master branch of git://git.denx.de/u-boot.git
v2: resubmit for rebase.
board/freescale
There are more than two 10GEC in single FMAN in some SoCs(e.g. T2080).
This patch adds support for 10GEC3 and 10GEC4.
Signed-off-by: Shengzhou Liu
---
Against master branch of git://git.denx.de/u-boot.git
v2: Rebase and add more comments description.
arch/powerpc/include/asm/fsl_serdes.h | 2 +
Add support for Freescale T2080/T2081 SoC.
T2080 includes the following functions and features:
- Four dual-threads 64-bit Power architecture e6500 cores, up to 1.8GHz
- 2MB L2 cache and 512KB CoreNet platform cache (CPC)
- Hierarchical interconnect fabric
- One 32-/64-bit DDR3/3L SDRAM memory con
On 22/11/13 03:58, Anup Patel wrote:
> On 22 November 2013 07:24, Christoffer Dall
> wrote:
>> On 21 November 2013 07:04, Marc Zyngier wrote:
>>> Hi Rob,
>>>
>>> On 21/11/13 14:28, Rob Herring wrote:
On Thu, Nov 21, 2013 at 2:59 AM, Marc Zyngier wrote:
> PSCI is an ARM standard that pr
Hi Josh,
On 11/22/2013 02:58 PM, Josh Wu wrote:
This patch will save U-Boot environment as a file: uboot.env, in FAT partition
instead of saving it in raw sector of SD card.
Since saving environment in raw sector has risk of corrupting the SD card and
only can use very small size. Save as a FAT
On Fri, Nov 22, 2013 at 2:10 PM, Ian Campbell wrote:
> On Thu, 2013-11-21 at 15:04 +, Marc Zyngier wrote:
>> Hi Rob,
>>
>> On 21/11/13 14:28, Rob Herring wrote:
>> > On Thu, Nov 21, 2013 at 2:59 AM, Marc Zyngier wrote:
>> >> PSCI is an ARM standard that provides a generic interface that
>> >>
On Fri, Nov 22, 2013 at 2:12 PM, Ian Campbell wrote:
> On Fri, 2013-11-22 at 09:28 +0530, Anup Patel wrote:
>> An Independent binary of a secured firmware makes more sense here.
>> Also, if secured firmware is an independent binary then it need not be
>> open source.
>
> In which case it should/ca
My company is designing a custom board that can be thought of as a
derivative of the pandaboard. I believe we have Rev B1 with us in the
office.
Considering that you are not getting any debug messages on your serial
console, I suspect one of the following;
* your cross-compiler might have issues
*
Here is the link for more details-
http://www.denx.de/wiki/U-Boot/OpenSourceIndia2013
--
Thanks,
Jagan.
Jagannadha Sutradharudu Teki,
E: jagannadh.t...@gmail.com, P: +91-9676773388
Engineer - System Software Hacker
U-boot - SPI Custodian and Zynq APSOC
Ln: http://www.linkedin.com/in/jag
Hello,
I'm bringing up a custom board that includes a mx283 and 64MB DDR2
memory, now I have some troubles with getting u-boot to properly boot
the kernel. I have enabled kernel_debugging and with earlyprintk I get
the following output:
## Booting kernel from Legacy Image at 4200 ...
Ima
Hello All,
On 22 November 2013 14:18, Naveen Krishna Chatradhi
wrote:
> Each I2C channel must be inited during the probe and then set "active"
> instead of initing the channel for every time we select the bus
> using "i2c dev bus"
>
> Signed-off-by: Naveen Krishna Chatradhi
> ---
> drivers/i2c/
Each I2C channel must be inited during the probe and then set "active"
instead of initing the channel for every time we select the bus
using "i2c dev bus"
Signed-off-by: Naveen Krishna Chatradhi
---
drivers/i2c/s3c24x0_i2c.c | 29 +
1 file changed, 13 insertions(+),
On Fri, 2013-11-22 at 09:28 +0530, Anup Patel wrote:
> An Independent binary of a secured firmware makes more sense here.
> Also, if secured firmware is an independent binary then it need not be
> open source.
In which case it should/can not have anything to do with u-boot nor
reuse any GPL'd u-bo
On Thu, 2013-11-21 at 15:04 +, Marc Zyngier wrote:
> Hi Rob,
>
> On 21/11/13 14:28, Rob Herring wrote:
> > On Thu, Nov 21, 2013 at 2:59 AM, Marc Zyngier wrote:
> >> PSCI is an ARM standard that provides a generic interface that
> >> supervisory software can use to manage power in the followin
51 matches
Mail list logo
