Re: [U-Boot] Adding a new board to U-Boot

2010-12-20 Thread Bedia, Vaibhav
On Monday, December 20, 2010 8:39 PM, Robert Mortimer wrote: > First off I aplogise for top posting. It is common on some of the > groups I am in You will be glad to know I have registerd our board > with the ARM registry I have updated my local git repo to reflect the > number we were given. None

Re: [U-Boot] Regarding the config.mk in U-boot TOP directory

2010-12-30 Thread Bedia, Vaibhav
On Thursday, December 30, 2010 6:51 PM, Asokan, Shyama Trikkadeeri wrote: > Hi Wolfgang, > I have been facing an issue while building u-boot for AT91SAM9263ek > board. The environment I am using is CYGWIN and toolchain is the > Code sourcery toolchain. > > > The make configuration step works f

Re: [U-Boot] [RFC PATCH 7/8] mkimage: Add OMAP boot image support

2011-01-04 Thread Bedia, Vaibhav
Hi John, On Tuesday, December 28, 2010 6:17 AM, John Rigby wrote: > Signed-off-by: John Rigby > --- > common/image.c|1 + > include/image.h |1 + > tools/Makefile|2 + > tools/mkimage.c |2 + > tools/omapimage.c | 226 > ++

Re: [U-Boot] BSS footprint of FAT very high - SPL issues

2011-01-31 Thread Bedia, Vaibhav
Hi Aneesh, On Tuesday, February 01, 2011 10:54 AM, Aneesh V wrote: > Dear Wolfgang, > > I had been working on creating an MMC SPL for OMAP4. OMAP boards > typically support booting from the FAT partition of a removable > SD/MMC card. So, we need to have FAT support in the SPL. But I am > having s

Re: [U-Boot] BSS footprint of FAT very high - SPL issues

2011-02-01 Thread Bedia, Vaibhav
On Tuesday, February 01, 2011 1:57 PM, V, Aneesh wrote: > Hi Vaibhav, > [...] >> >> I guess you will hit a similar issue with the networking related >> code is used (I am not sure if SPL uses it). That also requires a >> decent size of bss. > > Luckily we don't need networking related code in

Re: [U-Boot] BSS footprint of FAT very high - SPL issues

2011-02-01 Thread Bedia, Vaibhav
On Tuesday, February 01, 2011 1:48 PM, Aneesh V wrote: > Dear Wolfgang, > > On Tuesday 01 February 2011 01:25 PM, Wolfgang Denk wrote: >> Dear Aneesh V, >> >> In message<4d4798e2.3050...@ti.com> you wrote: >>> >>> I had been working on creating an MMC SPL for OMAP4. OMAP boards >>> typically su

Re: [U-Boot] BSS footprint of FAT very high - SPL issues

2011-02-01 Thread Bedia, Vaibhav
On Tuesday, February 01, 2011 3:35 PM, Wolfgang Denk wrote: > Dear "Bedia, Vaibhav", > > In message > you > wrote: >> >>> Luckily we don't need networking related code in SPL. >> >> It might be required later on :) > >

Re: [U-Boot] BSS footprint of FAT very high - SPL issues

2011-02-01 Thread Bedia, Vaibhav
On Tuesday, February 01, 2011 4:19 PM, Albert ARIBAUD wrote: [...] > That would be way outside of how U-Boot is supposed to work: the > assumption is that the SPL and U-Boot itself are present on-board > anyway -- the rationale being that the board should be able to get > to the U-Boot prompt with

Re: [U-Boot] The forbidden value in omap3-common timer.c code

2011-04-21 Thread Bedia, Vaibhav
On Thursday, April 21, 2011 5:44 PM, Simon Schwarz wrote: > Hi there, [...] > > It's about that part of code: > #define TIMER_LOAD_VAL 0x > IIRC there was a patch which corrected this reload value to 0. Regards, Vaibhav ___ U-Boot mailing lis

Re: [U-Boot] ttyO2 and ttyS2 in console bootcmd.

2011-05-01 Thread Bedia, Vaibhav
On Monday, May 02, 2011 4:46 AM, Chris Rodley wrote: > Hi, > > How does uboot specify whether it accepts ttySO or ttyS2 in > the console part of the boot cmd. I am trying to boot the > 2.6.39 kernel .. my new uboot works with 2.6.32 using ttyS2. > > It does not work with the new 2.6.39, but I

Re: [U-Boot] write to mcBsp address space

2011-02-15 Thread Bedia, Vaibhav
On Tuesday, February 15, 2011 12:05 PM, Ran Shalit wrote: > Hello, > > I'm working on OMAPL138 EVM board, with the U-BOOT. > I'm trying to access and write into the register (which have > write bits), but I always read 0 in all the map space of the > mcBSP0 and mcBSP1. (0x01d1 - 0x1d10800, 0x0

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

2011-03-01 Thread Bedia, Vaibhav
Aneesh, On Monday, February 28, 2011 5:16 PM, V, Aneesh wrote: > From: John Rigby > > Signed-off-by: John Rigby > --- > common/image.c|1 + > include/image.h |1 + > tools/Makefile|2 + > tools/mkimage.c |2 + > tools/mkimage.h |1 + > tools/omapimage.c | 229

Re: [U-Boot] [PATCH 04/22] armv7: start.S: provide a hook for saving boot params

2011-03-01 Thread Bedia, Vaibhav
On Monday, February 28, 2011 5:16 PM, V, Aneesh wrote: > Provide a means by which u-boot/SPL can save parameters passed > to it by ROM code or the pre-loader. > > A new function 'save_boot_params' has been defined and a > default implentation provided. Please note that we do not have > a stack ye

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

2011-03-01 Thread Bedia, Vaibhav
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 FA

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 CH

Re: [U-Boot] MACHINE ID

2010-11-23 Thread Bedia, Vaibhav
-Original Message- From: u-boot-boun...@lists.denx.de [mailto:u-boot-boun...@lists.denx.de] On Behalf Of Marek Vasut Sent: Tuesday, November 23, 2010 7:49 AM To: linux-...@lists.infradead.org Cc: u-boot@lists.denx.de; hong zhang; Oliver Schneidewind Subject: Re: [U-Boot] MACHINE ID On Sun

Re: [U-Boot] MACHINE ID

2010-11-23 Thread Bedia, Vaibhav
On Wednesday, November 24, 2010 1:24 AM, Wolfgang Denk wrote: > Dear "Bedia, Vaibhav", > > In message > you > wrote: >> >> This error is due to an incorrect machid being passed to the kernel. >> >> This can be fixed using the following command