Hi Felix,
On Thursday 16 October 2008, Felix Radensky wrote:
I'm looking at GPIO setup code for Canyonlands, and
it looks like some initializations mentioned in the 460EX
manual are missing. When pin is configured as alternate
input, the corresponding bits in TSRL/H registers should
be set.
On 14:44 Wed 15 Oct , Alan Carvalho de Assis wrote:
Hi Jean-Christophe,
On Wed, Oct 15, 2008 at 2:04 PM, Jean-Christophe PLAGNIOL-VILLARD
[EMAIL PROTECTED] wrote:
On 08:51 Wed 15 Oct , Alan Carvalho de Assis wrote:
Hi Jean-Christophe,
On Mon, Oct 13, 2008 at 5:49 AM,
As ppc44x: Unification of virtex5 pp440 boards did for the xilinx
ppc440 boards, this patch presents a common architecture for all the
xilinx ppc405 boards.
Any custom xilinx ppc405 board can be added very easily with no code
duplicity.
This patch also adds a simple generic board, that can be
Hi Ricardo,
On Thursday 16 October 2008, Ricardo Ribalda Delgado wrote:
As ppc44x: Unification of virtex5 pp440 boards did for the xilinx
ppc440 boards, this patch presents a common architecture for all the
xilinx ppc405 boards.
Any custom xilinx ppc405 board can be added very easily with no
Hello Stefan
Thanks for your comments. I have just uploaded v2 of the patch.
How about the existing Xilinx PPC405 boards like ml300? Should they somehow
use this new infrastructure?
Yes, that is the idea, adapt them to use this. So we have less work to
support them in the future. This
On Wed, Oct 15, 2008 at 7:35 AM, Fabio Estevam [EMAIL PROTECTED]wrote:
Kishore,
--- On Wed, 10/15/08, kishore choudhari [EMAIL PROTECTED] wrote:
From: kishore choudhari [EMAIL PROTECTED]
Subject: [U-Boot] code for DDR
To: u-boot@lists.denx.de
Date: Wednesday, October 15, 2008, 9:26 AM
Hi, Stefan
Stefan Roese wrote:
Hi Felix,
On Thursday 16 October 2008, Felix Radensky wrote:
I'm looking at GPIO setup code for Canyonlands, and
it looks like some initializations mentioned in the 460EX
manual are missing. When pin is configured as alternate
input, the corresponding
Ilya Yanok said the following:
Hi Wolfgang,
Wolfgang Denk wrote:
here is a set of changes we made to improve U-Boot JFFS2 code
performance. We still can't reach Linux's performance but improvements
are significant.
Any comments are welcome.
Are these patches independent of each
Hello Ben,
Ben Warren wrote:
Heiko Schocher wrote:
With this Command it is possible to add new I2C Busses,
which are behind 1 .. n I2C Muxes. Details see README.
While this is pretty cool, I'm curious what circumstances lead to
needing to add I2C buses at run-time via command line.
Hello Ben,
Ben Warren wrote:
Heiko Schocher wrote:
[...]
i2c probe - show devices on the I2C bus\n
+i2c reset - reinit the I2C Controller\n
re-init or re-initialize would be better.
You are right (as I wrote in the help text ...)
Is i2c reinit as commandname ok?
bye
Heiko
--
add same check on all board at MAKEALL start
it can be disable by CHECK=no as
$ CHECK=no ./MAKEALL
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD [EMAIL PROTECTED]
---
MAKEALL |5 +++
Makefile |4 ++
tools/find_config_errors | 87
Hi Heiko,
Heiko Schocher wrote:
Hello Ben,
Ben Warren wrote:
Heiko Schocher wrote:
[...]
i2c probe - show devices on the I2C bus\n
+i2c reset - reinit the I2C Controller\n
re-init or re-initialize would be better.
You are right (as I wrote in the
Hello Ben,
Ben Warren wrote:
Heiko Schocher wrote:
Hello Ben,
Ben Warren wrote:
Heiko Schocher wrote:
[...]
i2c probe - show devices on the I2C bus\n
+i2c reset - reinit the I2C Controller\n
re-init or re-initialize would be better.
You are right
following patch solves the compiler warning for the
mgsuvd board, using the soft_i2c driver:
[EMAIL PROTECTED] u-boot]$ ./MAKEALL mgsuvd
Configuring for mgsuvd board...
soft_i2c.c: In function 'write_byte':
soft_i2c.c:209: warning: implicit declaration of function 'i2c_soft_read_pin'
text
Hi Heiko,
Heiko Schocher wrote:
Hello Ben,
Ben Warren wrote:
Heiko Schocher wrote:
With this Command it is possible to add new I2C Busses,
which are behind 1 .. n I2C Muxes. Details see README.
While this is pretty cool, I'm curious what circumstances lead to
needing
Signed-off-by: Heiko Schocher [EMAIL PROTECTED]
---
board/keymile/mgcoge/mgcoge.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/board/keymile/mgcoge/mgcoge.c b/board/keymile/mgcoge/mgcoge.c
index 099e77b..5931f17 100644
--- a/board/keymile/mgcoge/mgcoge.c
+++
Removed #ifdef CONFIG_MPC834X dependency on upmconfig function.
Signed-off-by: Richard Retanubun [EMAIL PROTECTED]
---
cpu/mpc83xx/cpu.c |5 -
1 files changed, 0 insertions(+), 5 deletions(-)
diff --git a/cpu/mpc83xx/cpu.c b/cpu/mpc83xx/cpu.c
index 99ab216..848b8fd 100644
---
On Tue, Oct 14, 2008 at 01:24:09PM -0700, Ron Madrid wrote:
1. I don't see anywhere that the AL (address length, or number of
address cycles) can be set to anything other than 2. It appears to be
hard coded in both files.
Correct. AFAICT, setting AL to anything less than 2 is just an
Dear Jean-Christophe PLAGNIOL-VILLARD,
In message [EMAIL PROTECTED] you wrote:
add same check on all board at MAKEALL start
it can be disable by CHECK=no as
$ CHECK=no ./MAKEALL
NAK.
As discussed before, please remove the CHECK stuff from MAKEALL.
Best regards,
Wolfgang Denk
--
DENX
Currently in Practice: Medical Doctors in the United States
Data for the many various medical specialties
Sort by over a dozen different fields
Price for this week only = $398
{}{}{} Order this week and get the additional data below for free {}{}{}
Optometrists
Visiting Nurses RN's
run make find_config_errors to performed it.
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD [EMAIL PROTECTED]
---
Makefile |4 ++
tools/find_config_errors | 87 ++
2 files changed, 91 insertions(+), 0 deletions(-)
create mode
Dear Jean-Christophe PLAGNIOL-VILLARD,
In message [EMAIL PROTECTED] you wrote:
+find_config_errors:
+ @echo Search for config errors
+ @git-grep CFG_ | cut -d: -f1 | sort -u | xargs -I {}
tools/find_config_errors -f {}
+
Hm... should we not just use grep -r * so this will also
So is there a particular convention for which bytes should be used within the
OOB area for an ECC? I've looked for information on this but haven't been able
to come up with anything.
--- On Thu, 10/16/08, Scott Wood [EMAIL PROTECTED] wrote:
From: Scott Wood [EMAIL PROTECTED]
Subject: Re:
Ron Madrid wrote:
So is there a particular convention for which bytes should be used
within the OOB area for an ECC? I've looked for information on this
but haven't been able to come up with anything.
The 8313 manual says that when booting from NAND, it expects ECCM 0 on
small page and ECCM
On Thu, 16 Oct 2008 13:49:42 -0400
richardretanubun [EMAIL PROTECTED] wrote:
Hi Richard,
Removed #ifdef CONFIG_MPC834X dependency on upmconfig function.
please elaborate your commit messages to include /why/ this change is
needed, not only what it does (in this particular case we can easily
Dear Heiko Schocher,
In message [EMAIL PROTECTED] you wrote:
following patch solves the compiler warning for the
mgsuvd board, using the soft_i2c driver:
[EMAIL PROTECTED] u-boot]$ ./MAKEALL mgsuvd
Configuring for mgsuvd board...
soft_i2c.c: In function 'write_byte':
soft_i2c.c:209:
BTW, can you get your e-mail client to wrap long lines?
I've tried. I think there's a problem with yahoo's web mail.
Ron
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Dear Kumar Gala,
In message [EMAIL PROTECTED] you wrote:
mpc8536ds.c: In function 'is_sata_supported':
mpc8536ds.c:614: warning: unused variable 'devdisr'
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
board/freescale/mpc8536ds/mpc8536ds.c |1 -
1 files changed, 0 insertions(+), 1
Each architecture has different ways of determine what regions of memory
might not be valid to get overwritten when we boot. This provides a
hook to allow them to reserve any regions they care about. Currently
only ppc, m68k and sparc need/use this.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
This reverts commit dffd2446fb041f38ef034b0fcf41e51e5e489159.
The fix introduced by this patch is not correct. The problem is
that the documentation is not correct for the MPC8544 with regards
to which bit in PORDEVSR2 is for the SEC_CFG.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
The MPC8544 RM incorrect shows the SEC_CFG bit in PORDEVSR2 as being
bit 26, instead it should be bit 28. This caused in incorrect
interpretation of the i2c_clk which is the same as the SEC clk on
MPC8544. The SEC clk is controlled by cfg_sec_freq that is reported
in PORDEVSR2.
Signed-off-by:
31 matches
Mail list logo
