Dear Wolfgang Denk,
Wolfgang Denk wrote:
Dear Daniel Gorsulowski,
In message 1241619669338-git-send-email-daniel.gorsulow...@esd.eu you wrote:
This patch allows any at91 board, implementing the GPIO LED API,
to control the LEDs from the console.
led [ 1 | 2 | 3 | all ] [ on | off ]
Hi Daniel,
On Wednesday 06 May 2009, Daniel Gorsulowski wrote:
This patch allows any at91 board, implementing the GPIO LED API,
to control the LEDs from the console.
led [ 1 | 2 | 3 | all ] [ on | off ]
Why limit this to a max of 3 LED's? If this is a generic command (which I like
btw)
From: prafulla_wadaskar prafu...@marvell.com
This is Marvell's 88F6281_A0 based custom board developed
for wireless access point product
This patch is tested for-
1. Boot from DRAM/SPI flash/NFS
2. File transfer using tftp and loadb
3. SPI flash read/write/erase
4. Booting Linux kernel and RFS
-Original Message-
From: Dirk Behme [mailto:dirk.be...@googlemail.com]
Sent: Wednesday, May 06, 2009 8:25 PM
To: Matthias Ludwig; Pillai, Manikandan
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH] OMAP3EVM: net_chip uses CS5 not CS6
Matthias Ludwig wrote:
Signed-off-by: Matthias
This is not really a change. The cs configuration was correct, but not
the naming of it.
OMAP34XX_GPMC_BASE (0x6e00) + 0x150 = base address of configuration
registers for GPMC-CS5 not GPMC-CS6.
best regards,
Matthias
On Thu, May 07, 2009 at 12:34:01PM +0530, Pillai, Manikandan wrote:
Dear ffmm rrcc,
In message dbab92f10905062254s3bea0882y7d4ec546c4ddb...@mail.gmail.com you
wrote:
Hi all:
I have write a standalone application on U-Boot,it works well.but i
have to get the entry point address follow this article:
Dear Daniel Gorsulowski,
In message 4a02792b.8060...@esd.eu you wrote:
Ummm... common is for, well, for common stuff. If this code is
specific to AT91 only, it should not go into common.
IMHO this code is not specific to AT91 only. Well, other architectures does
not
support the
Dear Kazuaki Ichinohe,
In message 4a027e44.5080...@fsi.co.jp you wrote:
Hello Denk, Stefan,
Could you please rebase your patch against the current top-of-tree mainline
repository and resumbmit?
Thank you for the reply.
I made the patch from the source obtained with git in 5/7.
The
Dear Matthias Ludwig,
In message 20090507071155.ga8...@ultratronik.de you wrote:
This is not really a change. The cs configuration was correct, but not
the naming of it.
OMAP34XX_GPMC_BASE (0x6e00) + 0x150 = base address of configuration
registers for GPMC-CS5 not GPMC-CS6.
Can we
Cards which are not compatible with SD 2.0 standard, cat return response
for CMD8 command, but it will be invalid in terms of SD 2.0. We should
accept this case as admissible.
Signed-off-by: Yauhen Kharuzhy jek...@gmail.com
---
drivers/mmc/mmc.c |4
1 files changed, 0 insertions(+), 4
Signed-off-by: Detlev Zundel d...@denx.de
Cc: Sascha Hauer s.ha...@pengutronix.de
---
board/imx31_phycore/imx31_phycore.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/board/imx31_phycore/imx31_phycore.c
b/board/imx31_phycore/imx31_phycore.c
index 93a5c40..92aba96
Hi Jon,
Jon Smirl wrote:
On Wed, May 6, 2009 at 2:57 PM, Jon Smirl jonsm...@gmail.com wrote:
Why is speed selection = 10 Mbps when both sides support 100Mb?
Is uboot decoding this register correctly?
uboot mii dump 0 0
0. (1000) -- PHY control register --
(8000:)
Jonathan Haws wrote:
I need to generate an assembly listing that contains all the assembly
code generated by the compiler. I have tried putting the standard
GCC options in ppc_config.mk, but cannot get the results I am looking
for.
What I need is a listing file that contains the address
Hi Stefan,
This patch adds another build target for the AMCC Sequoia PPC440EPx
eval board. This RAM-booting version is targeted for boards without
NOR FLASH (NAND booting) which need a possibility to initially
program their NAND FLASH. Using a JTAG debugger (e.g. BDI2000/3000)
configured to
On Wed, May 6, 2009 at 2:33 AM, Felix Radensky fe...@embedded-sol.com wrote:
Hi,
I'm new to Xilinx world, so please bare with my ignorance.
Looking at u-boot Xilinx files I see that u-boot does not perform
SDRAM initialization. SDRAM is apparently initialized by FPGA
code. Is that correct ?
Hi Detlev,
On Thursday 07 May 2009, Detlev Zundel wrote:
int misc_init_r(void)
{
- uint pbcr;
- int size_val = 0;
- u32 reg;
+ __attribute__((unused)) uint pbcr;
+ __attribute__((unused)) int size_val = 0;
+ __attribute__((unused)) u32 reg;
Am I correct to assume
HI
I am working with Freescale MPC8313E-RDB and with it comes their BSP. This
provides a u-boot. I want to understand how the u-boot commands work as in
where are they defined and in which files.
My utlimate goal is to add new u-boot commands and to modify the exsisting
commands (if needed)
Im a
Deepak Gopalakrishnan wrote:
HI
I am working with Freescale MPC8313E-RDB and with it comes their BSP. This
provides a u-boot. I want to understand how the u-boot commands work as in
where are they defined and in which files.
My utlimate goal is to add new u-boot commands and to modify the
yes indeed...thanks a lot...
i can guess that adding a command wont be just a walk in the
park.could you tell me wat all this i will have to take care of if i
were supposed to writesay another date function...which would display
the date in another format
other than adding it into
Dirk,
I believe I caught and fixed these changes when rebasing my zoom2
patches to the latest arm/next
From my notes :
Remove SDP_3430_V1 and SDP_3430_V2 per upstream changes
These were removed in the zoom2.h file.
No other changes needed.
Tom
Dirk Behme wrote:
Hi Tom,
Tom wrote:
Here
Hi Stefan,
Hi Detlev,
On Thursday 07 May 2009, Detlev Zundel wrote:
int misc_init_r(void)
{
- uint pbcr;
- int size_val = 0;
- u32 reg;
+ __attribute__((unused)) uint pbcr;
+ __attribute__((unused)) int size_val = 0;
+ __attribute__((unused)) u32 reg;
Am I correct to
Dear Wolfgang,
Wolfgang Denk wrote:
Dear Matthias Ludwig,
In message 20090507071155.ga8...@ultratronik.de you wrote:
This is not really a change. The cs configuration was correct, but not
the naming of it.
OMAP34XX_GPMC_BASE (0x6e00) + 0x150 = base address of configuration
registers
Have you looked at code in common/cmd_date.c?
If you see at the end of the file there is macro U_BOOT_CMD() that adds the
command date, there is function do_date that is invoked, so if you wanted to
implement your own version of date command you will have to implement your
own do_date function.
On Thursday 07 May 2009, Detlev Zundel wrote:
If so, it still seems to be a somewhat rude way to do it. How
long will it take the gcc maintainers to produce a warning: unused
variable is used warning? ;)
I prefer to do it this way instead of encasing the variable declaration
into
Hi,
I have added OMAP3517EVM at:
http://www.arm.linux.org.uk/developer/machines/
What is the preferred way to bring this definition
into u-boot (include/asm-arm/mach-types.h)?
Best regards,
Sanjeev
___
U-Boot mailing list
U-Boot@lists.denx.de
Premi, Sanjeev wrote:
Hi,
I have added OMAP3517EVM at:
http://www.arm.linux.org.uk/developer/machines/
What is the preferred way to bring this definition
into u-boot (include/asm-arm/mach-types.h)?
Bad timing, mach-types.h was updated recently in U-Boot
-Original Message-
From: Dirk Behme [mailto:dirk.be...@googlemail.com]
Sent: Thursday, May 07, 2009 10:02 PM
To: Premi, Sanjeev
Cc: u-boot@lists.denx.de; Jean-Christophe PLAGNIOL-VILLARD
Subject: Re: [U-Boot] ARM: Updating mach-types.h
Premi, Sanjeev wrote:
Hi,
I have
Dear Stefan,
In message 200905071530.43940...@denx.de you wrote:
On Thursday 07 May 2009, Detlev Zundel wrote:
int misc_init_r(void)
{
- uint pbcr;
- int size_val = 0;
- u32 reg;
+ __attribute__((unused)) uint pbcr;
+ __attribute__((unused)) int size_val = 0;
+
Dear Dirk,
In message 4a02fb34.2090...@googlemail.com you wrote:
Please provide proper C structs!
Would you like to have a look to the code snippet visible in Matthias'
patch
http://lists.denx.de/pipermail/u-boot/2009-May/052157.html
?
Done.
It's my understanding that what's in
Dear Stefan,
in message 200905071739.56301...@denx.de you wrote:
Linux kernel btw. Here the macro __maybe_unsed is defined to
__attribute__((unused)).
In many cases? a rgrep on a recent kernel counts 84 incantations, which
is not much for the Linux kernel, I believe.
Perhaps it's
Wolfgang Denk wrote:
Finally, and this is what I really compalin about, is that there is no
big structure which includes all the blocks that make up the CPU into
one big structure (as it's done for example for PowerPC systems in the
include/asm-ppc/*immap* files) - you still use code like
Wolfgang Denk wrote:
Dear Stefan,
in message 200905071739.56301...@denx.de you wrote:
Linux kernel btw. Here the macro __maybe_unsed is defined to
__attribute__((unused)).
In many cases? a rgrep on a recent kernel counts 84 incantations, which
is not much for the Linux kernel, I believe.
On Thu, May 7, 2009 at 5:08 AM, Yauhen Kharuzhy jek...@gmail.com wrote:
Cards which are not compatible with SD 2.0 standard, cat return response
for CMD8 command, but it will be invalid in terms of SD 2.0. We should
accept this case as admissible.
Signed-off-by: Yauhen Kharuzhy
On 12:48 Tue 05 May , Daniel Mack wrote:
U-Boot does not currently build for PXA platforms with USB support
enabled. This is due to commit 24e37645e7378b20fa8f20e2996c8fb8e9
which introduced the usage of UP2OCR without defining it.
unfortunatly it's the invert this commit remove it
please
Dear Scott,
In message 4a0333fc.6090...@freescale.com you wrote:
Wolfgang Denk wrote:
Finally, and this is what I really compalin about, is that there is no
big structure which includes all the blocks that make up the CPU into
one big structure (as it's done for example for PowerPC systems
On 14:52 Tue 05 May , Sanjeev Premi wrote:
The current configuration doesn't define default
bootfile; leading to this warning at execution:
OMAP3_EVM # dhcp
...
...
DHCP client bound to address 192.168.1.11
*** Warning: no boot file name; using 'AC18BE16.img'
TFTP from server
On 17:41 Tue 05 May , Dirk Behme wrote:
After removal of dublicated interrupt code, rename file to what it
really does now.
I prefer to rename all files at the same time
Btw please use git to show that you only rename the file without change
Best Regards,
J.
On 17:41 Tue 05 May , Dirk Behme wrote:
Reformat COBJS handling.
please rebase against you first patch as the 2 will be handle by an otherone
Best Regards,
J.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
On 17:21 Wed 06 May , Dirk Behme wrote:
Some OMAP3 boards need control for external power companion
chips. Introduce a CONFIG option for this, to avoid Makefile
changes for each board.
please also move it to cpu/arm_cortexa8/omap3/
omap3 and davinci is not a vendor
so common code will
Wolfgang Denk wrote:
Dear Scott,
In message 4a0333fc.6090...@freescale.com you wrote:
Wolfgang Denk wrote:
Finally, and this is what I really compalin about, is that there is no
big structure which includes all the blocks that make up the CPU into
one big structure (as it's done for
Premi, Sanjeev wrote:
Hi,
I have added OMAP3517EVM at:
http://www.arm.linux.org.uk/developer/machines/
What is the preferred way to bring this definition
into u-boot (include/asm-arm/mach-types.h)?
Bad timing, mach-types.h was updated recently in U-Boot
:(
Dear Jean-Christophe PLAGNIOL-VILLARD,
In message 20090507203647.ga3...@game.jcrosoft.org you wrote:
On 12:48 Tue 05 May , Daniel Mack wrote:
U-Boot does not currently build for PXA platforms with USB support
enabled. This is due to commit 24e37645e7378b20fa8f20e2996c8fb8e9
which
On 09:11 Thu 07 May , Matthias Ludwig wrote:
This is not really a change. The cs configuration was correct, but not
the naming of it.
OMAP34XX_GPMC_BASE (0x6e00) + 0x150 = base address of configuration
registers for GPMC-CS5 not GPMC-CS6.
so please fix the comment
Best Regards,
J.
Dear Scott Wood,
In message 4a034b09.7030...@freescale.com you wrote:
Or what replaced the immr structs?
The device tree, mainly...
Right, of course.
... But #defines can work for u-boot.
Of course they _can_ work. But they can easily fail (as we just see
in this
On 23:00 Thu 07 May , Wolfgang Denk wrote:
Dear Jean-Christophe PLAGNIOL-VILLARD,
In message 20090507203647.ga3...@game.jcrosoft.org you wrote:
On 12:48 Tue 05 May , Daniel Mack wrote:
U-Boot does not currently build for PXA platforms with USB support
enabled. This is due to
Wolfgang Denk wrote:
Dear Scott Wood,
In message 4a034b09.7030...@freescale.com you wrote:
Or what replaced the immr structs?
The device tree, mainly...
Right, of course.
... But #defines can work for u-boot.
Of course they _can_ work. But they can easily fail
The u-boot.lds file is common for all omap boards.
Move a cleaned up version to the cpu layer and add makefile logic to use it.
Signed-off-by: Tom Rix tom@windriver.com
---
board/omap3/beagle/u-boot.lds | 63 -
board/omap3/evm/u-boot.lds|
Port the linux kernel's omap gpio interface to u-boot.
The orignal source is in linux/arch/arm/plat-omap/gpio.c
See doc/README.omap3 for instructions on use.
Signed-off-by: Tom Rix tom@windriver.com
---
cpu/arm_cortexa8/omap3/Makefile |1 +
cpu/arm_cortexa8/omap3/gpio.c | 185
The logicpd web site is a good source for general information on this board.
Please start looking here if the below links are broken.
http://www.logicpd.com
This is a pdf of the product
http://www.logicpd.com/sites/default/files/1012659A_Zoom_OMAP34x-II_MDP_Brief.pdf
This is a pdf of the product
Zoom2 serial is in general supplied by one of the 4 UARTS on the debug board.
The default serial is from the USB connector on left side of the debug board.
The USB connector will produce 2 of the 4 UARTS. On your host pick the first
enumeration.
The serial port set up is the same with Zoom1.
This patch controls the large LED on the top left of the zoom2.
Signed-off-by: Tom Rix tom@windriver.com
---
board/omap3/zoom2/Makefile|8 ++-
board/omap3/zoom2/led.c | 129 +
board/omap3/zoom2/zoom2.c |4 +-
On Thu, May 07, 2009 at 03:13:40PM -0500, Andy Fleming wrote:
On Thu, May 7, 2009 at 5:08 AM, Yauhen Kharuzhy jek...@gmail.com wrote:
Cards which are not compatible with SD 2.0 standard, cat return response
for CMD8 command, but it will be invalid in terms of SD 2.0. We should
accept this
On May 6, 2009, at 4:43 PM, Yauhen Kharuzhy wrote:
SCR switch data are read from card as big-endian words and should be
converted to CPU byte order.
Signed-off-by: Yauhen Kharuzhy jek...@gmail.com
---
- if ((switch_status[4] 0x0f00) == 0x0100)
+ if
On Thu, May 07, 2009 at 11:02:34PM +0200, Jean-Christophe PLAGNIOL-VILLARD
wrote:
Can you please run a git show 24e37645 again?
To me it seems that this commit
- removed the usage of UP2OCR from board/delta/delta.c
but also
- added the usage of UP2OCR to the new file cpu/pxa/usb.c
HI Ilya,
This is a port of Linux driver for SDHC host controller hardware
found on Freescale's MX2 and MX3 processors. Uses new generic MMC
framework (CONFIG_GENERIC_MMC) and it looks like there are some
problems with a framework (at least on LE cpus). Some of these
problems are addressed in
Hi Wolfgang,
On Thursday 07 May 2009, Wolfgang Denk wrote:
Perhaps it's quite new to the Linux kernel. I just spotted it the first
time a few weeks ago and thought: What a nice way to remove some of the
ugly #ifdef's in U-Boot!. :)
My understanding was that this is (only?) intended
Hi Stefan,
Stefan Roese wrote:
Hi Daniel,
On Wednesday 06 May 2009, Daniel Gorsulowski wrote:
This patch allows any at91 board, implementing the GPIO LED API,
to control the LEDs from the console.
led [ 1 | 2 | 3 | all ] [ on | off ]
Why limit this to a max of 3 LED's? If this is a
Wolfgang Denk schrieb:
Dear Daniel Gorsulowski,
In message 4a02792b.8060...@esd.eu you wrote:
Ummm... common is for, well, for common stuff. If this code is
specific to AT91 only, it should not go into common.
IMHO this code is not specific to AT91 only. Well, other architectures does
58 matches
Mail list logo
