Hi ML,
in my code (for now a stupid SMI interface) I'm using a jump table like this:
struct reg:{
callback_1 c1,
callback_2 c2,
...
};
struct reg mytable[100]={ . }
c1 and c2 are pointer to functions.
My problem is that U-boot relocates itself into ram and
mpc8536ds.c: In function 'is_sata_supported':
mpc8536ds.c:615: warning: unused variable 'devdisr'
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
board/freescale/mpc8536ds/mpc8536ds.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/board/freescale/mpc8536ds/mpc8536ds.c
This removes a bit of code and makes it easier for the upcoming sub bootm
command support to call into the proper OS specific handler.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
common/cmd_bootm.c | 67 +++
1 files changed, 30 insertions(+),
On Oct 18, 2008, at 1:07 PM, Wolfgang Denk wrote:
Dear Kumar,
In message [EMAIL PROTECTED]
you wrote:
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
board/stxssa/Makefile|9 --
board/stxssa/ddr.c | 70
++
Hello Wolfgang,
can you please check if all urgent patches have been added to the
U-Boot master branch?
If anything should still be missing, please respond *now*.
Shouldn't my USB (bugfix) patches not go in that Markus now has in his
USB branch ?
Kind Regards,
Remy
My intention is to
2008/10/19 Remy Bohmer [EMAIL PROTECTED]:
Hello Wolfgang,
can you please check if all urgent patches have been added to the
U-Boot master branch?
If anything should still be missing, please respond *now*.
Shouldn't my USB (bugfix) patches not go in that Markus now has in his
USB branch ?
Dear Remy,
In message [EMAIL PROTECTED] you wrote:
Hello Wolfgang,
can you please check if all urgent patches have been added to the
U-Boot master branch?
If anything should still be missing, please respond *now*.
Shouldn't my USB (bugfix) patches not go in that Markus now has in his
Dear Remy Bohmer,
In message [EMAIL PROTECTED] you wrote:
Shouldn't my USB (bugfix) patches not go in that Markus now has in his
USB branch ?
Oops, I see, already too late...
Only too late for 2008.10, but there will be another release coming
soon...
Best regards,
Wolfgang Denk
--
Hi,
while tryong to convert the TQM8260 board to using the CFI flash
driver (instead of a perfectly working legacy flash driver) I ran
into a strange problem: after an erase operation, the CFI driver
returns without any error indication, but the flash is not ready yet.
It takes some
From: Wolfgang Denk [EMAIL PROTECTED]
Several customers have reported problems with the environment in
EEPROM, including corrupted content after board reset. Probably the
code to prevent I2C Enge Conditions is not working sufficiently.
We move the environment to flash now, which allows to have a
On Tuesday 14 October 2008, Timur Tabi wrote:
Wolfgang Denk wrote:
What about resubmitting this patch, with adding a debug() to the new,
common i2c_reg_read() and i2c_reg_write() funtions?
I can do that. First, however, I need Mike Frysinger to help me resolve
the Blackfin version of
On Sun, Oct 19, 2008 at 4:18 PM, Mike Frysinger [EMAIL PROTECTED] wrote:
it's broken and i fixed it in the Blackfin i2c read write. feel free to make
the change and ignore the weirdness.
Ah, thank you! I'll do it after WD pulls your repo.
i havent been processing any @gentoo.org e-mail ...
Hi Wolfgang,
Why the heck does flash_is_busy() return 0 when the flashobviously is
still busy?
Does this use the toggle bit detection? I saw the same symptoms
with Nios II. Basically, the memory controller was reading the
16-bit flash twice to obtain a full 32-bit word, then returning just
the
Dear Scott,
In message [EMAIL PROTECTED] you wrote:
Why the heck does flash_is_busy() return 0 when the flashobviously is
still busy?
Does this use the toggle bit detection? I saw the same symptoms
Hm... how can I tell if it does?
The driver reports AMD Standard command set, so it
On Oct 19, 2008, at 1:44 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
On 13:07 Sun 19 Oct , Kumar Gala wrote:
This removes a bit of code and makes it easier for the upcoming sub
bootm
command support to call into the proper OS specific handler.
Signed-off-by: Kumar Gala [EMAIL
On Sunday 19 October 2008, Timur Tabi wrote:
On Sun, Oct 19, 2008 at 4:18 PM, Mike Frysinger [EMAIL PROTECTED] wrote:
it's broken and i fixed it in the Blackfin i2c read write. feel free to
make the change and ignore the weirdness.
Ah, thank you! I'll do it after WD pulls your repo.
dont
On Mon, Oct 20, 2008 at 12:01:59AM +0200, Wolfgang Denk wrote:
Hello,
on some systems (for example Fedora Core 4) U-Boot builds with the
following wanrings only:
...
In file included from /home/wd/git/u-boot/include/libfdt_env.h:33,
from fdt.c:51:
On Sunday 12 October 2008, Ben Warren wrote:
Wolfgang Denk wrote:
Dear Ben,
In message [EMAIL PROTECTED] you wrote:
I don't see any responses to this latest version of the driver.
Is there any special reason it was neither added nor rejected?
...
No specific reasons - I should
Hello Wolfgang,
Wolfgang Denk wrote:
Several customers have reported problems with the environment in
EEPROM, including corrupted content after board reset. Probably the
code to prevent I2C Enge Conditions is not working sufficiently.
Is this somewhere reproducible?
Maybe we can try my patch
19 matches
Mail list logo
