Hi,
> -Original Message-
> From: Wolfgang Denk [mailto:[EMAIL PROTECTED]
> Subject: Re: [U-Boot] how can i change u-boot load address?
>
> > U wouldnt see mapping the vector on (most) ARM Platforms
> because they
> > use u-boot as secondary bootloader
>
> I don't have reliable stati
Hi,
>I seem to understand that remapping, being a CPU specific and
>depending on a way U-Boot starts (either from ROM or RAM), is taken
>away in 'lowlevel_init' function, defined either in in
>$(uboot)/cpu/arm/$(soc)/lowlevel_init.S (for example,
>$(uboot)/cpu/arm920t/ks8695/) or in
>$(uboot)/boar
Hi,
> From: Roman Mashak [mailto:[EMAIL PROTECTED]
> Subject: Re: [U-Boot] PrimeCell Peripherals
> I must've confused you with the question.
No u havent. Sorry to say that u havent checked the code properly
> suppose we build U-Boot for arm920t based target, in such a
> case, two files defini
Hi,
> From: Roman Mashak [mailto:[EMAIL PROTECTED]
> Subject: Re: [U-Boot] PrimeCell Peripherals
>
> I'm a bit confused: 'do_irq' is defined in several files,
> including CPU-specific (arm920t, 720t etc.) and ARM
> architecture library ($(U_BOOT)/lib_arm). So if we build for
> arm920t-based
HI,
> From: Roman Mashak [mailto:[EMAIL PROTECTED]
> Subject: Re: [U-Boot] PrimeCell Peripherals
>
> To add a bit to my previous message.
>
> As far as I understood from U-Boot's README, a standalone
> mode can and may want to use interrupts -- so it'd reasonable
> to have interrupts controll
Hi,
> In U-Boot source tree there are number of drivers with
> interrupt service routines running (for example,
> $(U_BOOT)/drivers/net/bcm570x.c) as well as various
> interrupts related macros (some of them not used thought), if
> this is what you mean.
> Perhaps these definitions are for fut
Hi,
> From: Roman Mashak [mailto:[EMAIL PROTECTED]
> Subject: Re: [U-Boot] PrimeCell Peripherals
>
> Right, that's what I've found in the U-Boot sources. How come
> that widely used interrupt controllers like PL19x are not
> supported by default?
Thats because Most of the ARM based boards doe
Hmm,
Interestingly i had sent a patch for the same for both
integrator[ap/cp].
http://article.gmane.org/gmane.comp.boot-loaders.u-boot/46044.
i had sent it to Jean-Christophe PLAGNIOL-VILLARD & Peter Pearse & also
to U-Boot user list.
Don't know y it didn't reach there.
Regards
Gururaja
___
Hi,
I was going through the i2c module support in u-boot-1.3.4 source & found few
duplicate calls to i2c_init.
For the below target platform,
uboot-1.3.4\lib_ppc\board.c
1. Initially, during init_sequence, init_func_i2c() is called which in
turn calls i2c_init() (uboot-1.3.4\lib_ppc\b
Hi,
- CONFIG_INIT_CRITICAL is deprecated
- remove all references to CONFIG_INIT_CRITICAL for ARM based boards
- replace by CONFIG_SKIP_LOWLEVEL_INIT
Signed-off-by: Gururaja Hebbar <[EMAIL PROTECTED]>
---
cpu/arm946es/start.S|6 +++---
cpu/arm_intcm/start.S |2 +-
i
Hi,
> From: "Roman Mashak" <[EMAIL PROTECTED]>
> Subject: [U-Boot] U-Boot version for a new port
> I'm planning to make a port on a ARM926EJ-S based board. What is the
> recommended way: take release or GIT version as a base ?
Depends on what processor you are using, atmel at91sam9 series or omap
Hi,
Any update on this patch. I even checked Linux Source for this define & way
back in Linux 2.6.11, same kind of patch was applied.
More info @
http://www.linuxhq.com/kernel/v2.6/11/include/asm-arm/arch-omap/hardware.h
TIA
Regards
Gururaja
___
U-B
Hi,
- Correct Improper ulong division. This patch take care of
multiple definition of `__udivsi3' & undefined reference to `raise' Error
when compiling [ap/cp]926ejs_config with CodeSourcery arm toolchain
Signed-off-by: Gururaja Hebbar <[EMAIL PROTECTED]>
---
board/integratorap/integrator
Hi,
- memsetup.s is changed/merged to lowlevel_init.S
memsetup.S has a global label memsetup that just returns back to caller
- memsetup global label is changed/merged to lowlevel_init
This label is not called from anywhere.
Signed-off-by: Gururaja Hebbar <[EMAIL PROTECTED]>
---
board/integ
Hi,
I am using CodeSourcery Arm Toolchain to compile U-boot-1.3.3 for integrator cp
board.
1. I set the proper environment variables (BUILD_DIR, PATH, CROSS_COMPILE)
export PATH=/home/user/project/arm-2007q1/bin:$PATH
export CROSS_COMPILE=arm-none-linux-gnueabi-
export BUILD_DIR=/home/user/pr
Hi,
I was going through ARM integrator[cp/ap] (u-boot-1.3.3) board files & found
occurrences of memsetup global variables & file memsetup.s
But according to a changelog entry, memsetup global label is changed/merged to
lowlevel_init & memsetup.s is changed/merged to lowlevel_init.S.
Below are
Hi,
Acked-by : Gururaja Hebbar <[EMAIL PROTECTED]>
Regards
Gururaja
> -Original Message-
> From: Jean-Christophe PLAGNIOL-VILLARD [mailto:[EMAIL PROTECTED]
> Subject: [PATCH 1/1] Correct ARM Versatile Timer Initialization
>
> From: Gururaja Hebbar
Hi,
Resend - Subject Corrected. Sorry for the mistake
I searched the Entire u-boot-1.3.4\ directory for "PTV_BIT" declaration &
couldn't find any.
Rather MPUTIM_PTV_BIT is defined which is the correct declaration.
Below Patch Corrects the declaration of MPUTIM_PTV_MASK bit in both omap1510.h
- According to ARM Dual-Timer Module (SP804) TRM (ARM DDI0271),
-- Timer Value Register @ TIMER Base + 4 is Read-only.
-- Prescale Value (Bits 3-2 of TIMER Control register)
can only be one of 00,01,10. 11 is undefined.
-- CFG_HZ for Versatile board is set to
#define CFG_H
Hi,
I would like to know the status of below patches that i submitted.
I would like to contribute as much as possible to uboot & i am really sorry if
my patch are incorrect/invalid.
Kindly le me know in such situations & i will update/correct/change it &
re-submit.
Sorry for the trouble & Tha
Hi,
According to the Maintainer file,
Kshitij Gupta <[EMAIL PROTECTED]> is the maintainer for omap1510inn board &
Dave Peverley <[EMAIL PROTECTED]> for omap730p2
I had submitted a patch for OMAP 1510 & OMAP 730 Boards. (
http://www.nabble.com/-U-Boot---PATCHCorrect-Invalid-Timer-Register-
- Remove unused global variable os_data_count.
This was long back deprecated but still in use.
The only reference for this in google is
http://cvs.tuxbox.org/cgi-bin/viewcvs.cgi/*checkout*/tuxbox/boot/ppcboot/common/Attic/cmd_boot.c?content-type=text%2Fplain
- Remove unused variable z.
Hi,
Today I download u-boot-1.3.4 and checked drivers\rtc directory with
u-boot-1.3.3\drivers\rtc .
There is change in the files that this patch touches. So I think the same
patch can be applied to u-boot-1.3.4 also.
Kindly update me if any changes is needed
Regards
Gururaja
Hi,
> > So my doubt is, Shouldn't erase_grp_size come before sector size.
>
> No. But sometimes, erase_grp_size just isn't there at all,
> and you have a 1-bit flag right before sector_size instead.
>
> Currently, these values aren't actually used by u-boot, but I
> guess ideally, we should e
Hi,
Could some please let me know whether this patch is correct.
TIA
Regards
Gururaja
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Hi,
> Hi,
>
> I need few clarification regarding mmc csd structure
> declaration. I was taking Atmel mci as reference.
>
> In ProductManualSDCardv2.2.pdf @ page 34 &
> ProdManualSDCardv1.9[1].pdf @ page 39, says
>
> ...
> ...
> ...
> C_SIZE_MULT 3 bit width
> ERASE_BLK_EN 1 bit width
> S
Hi,
I need few clarification regarding mmc csd structure declaration. I was taking
Atmel mci as reference.
In ProductManualSDCardv2.2.pdf @ page 34 & ProdManualSDCardv1.9[1].pdf @ page
39, says
...
...
...
C_SIZE_MULT 3 bit width
ERASE_BLK_EN1 bit width
SECTOR_SIZE 7 bit width
WP_
Hi,
I searched the Entire u-boot-1.3.4\ directory for "PTV_BIT" declaration &
couldn't find any.
Rather MPUTIM_PTV_BIT is defined which is the correct declaration.
Below Patch Corrects the declaration of MPUTIM_PTV_MASK bit in both omap1510.h
& omap730.h.
Kindly update me if i am wrong.
TIA
Hi<
> > > Hi,
> > >
> > > > according to datasheet for the register TimerXControl
> > > > we are supposed to not modify the bits [31:8] and [4]
> > > > so we are suppose to read the register and modify only
> the others registers/register/bits/
> > >
> > > Does this mean i need to resend the e
Hi,
> according to datasheet for the register TimerXControl
>
> we are supposed to not modify the bits [31:8] and [4]
>
> so we are suppose to read the register and modify only the
> others register.
Does this mean i need to resend the earlier patch. Writing 00 to these
bits ( 31:8 & 4) is u
Hi,
There was a bug in my previous submitted patch. I think its still not applied
to master.
Kindly ignore that patch. See comments for reason
TIA
Regards
Gururaja
- According to ARM Dual-Timer Module (SP804) TRM (ARM DDI0271),
-- Timer Value Register @ TIMER Base + 4 is Read-only.
-- Pres
31 matches
Mail list logo
