Richard,
On Friday 01 May 2009 23:29:22 Richard Retanubun wrote:
Would I be foolish to hope that this can be merged in for 2009.06? :)
I just sent a patch with the weak default for this reset function. Please give
it a try on your system and let me know if this works for you.
Thanks.
Cheers,
Stefan Roese wrote:
Richard,
I just sent a patch with the weak default for this reset function. Please
give
it a try on your system and let me know if this works for you.
Thanks.
Cheers,
Stefan
Tested and works, thanks!
- Richard
___
Dear Stefan,
In message 4ae7303e.3000...@ruggedcom.com Richard Retanubun wrote:
Stefan Roese wrote:
Richard,
I just sent a patch with the weak default for this reset function. Please
give
it a try on your system and let me know if this works for you.
Thanks.
Cheers,
Stefan
Stefan Roese wrote:
On Wednesday 15 April 2009, Stefan Roese wrote:
I don't like both versions. We should implement something which doesn't
change the current behavior probably needed on some other boards. So
how about something like this:
I took your proposal and tried to implement it, hit a
Richard,
On Wednesday 15 April 2009, Richard Retanubun wrote:
Did you take a look at the CONFIG_SYS_FLASH_CFI_AMD_RESET define? I
suggest
you give it a try and let me know if this helps.
This does help but for the wrong reason:
#ifdef CONFIG_SYS_FLASH_CFI_AMD_RESET /* needed for
Hi Stefan,
Thanks for working through this with me,
And do you need an Intel reset command on your board? Is there an option
for Intel command style FLASH chips?
Maybe I am young and naive, but I am hoping to give the HW guys flexibility in
choosing
the command sets for their flash.
I
On Wednesday 15 April 2009, Richard Retanubun wrote:
And do you need an Intel reset command on your board? Is there an option
for Intel command style FLASH chips?
Maybe I am young and naive, but I am hoping to give the HW guys flexibility
in choosing the command sets for their flash.
I
On Wednesday 15 April 2009, Stefan Roese wrote:
I don't like both versions. We should implement something which doesn't
change the current behavior probably needed on some other boards. So
how about something like this:
I took your proposal and tried to implement it, hit a snag with
Hi Richard,
On Monday 13 April 2009, Richard Retanubun wrote:
As a follow up, This hack seems to fix the issue.
diff --git a/drivers/mtd/cfi_flash.c b/drivers/mtd/cfi_flash.c
index 631b969..d386143 100644
--- a/drivers/mtd/cfi_flash.c
+++ b/drivers/mtd/cfi_flash.c
@@ -1691,7 +1691,7 @@
Hi Stefan,
Did you take a look at the CONFIG_SYS_FLASH_CFI_AMD_RESET define? I suggest
you give it a try and let me know if this helps.
This does help but for the wrong reason:
#ifdef CONFIG_SYS_FLASH_CFI_AMD_RESET /* needed for STM_ID_29W320DB on UC100 */
# undef FLASH_CMD_RESET
# define
Hi Stefan,
As a follow up, This hack seems to fix the issue.
diff --git a/drivers/mtd/cfi_flash.c b/drivers/mtd/cfi_flash.c
index 631b969..d386143 100644
--- a/drivers/mtd/cfi_flash.c
+++ b/drivers/mtd/cfi_flash.c
@@ -1691,7 +1691,7 @@ static int __flash_detect_cfi (flash_info_t * info,
struct
Hi Stefan,
I'm trying to get u-boot 2009.03 on coldfire to boot on flash part M29W128G.
I think I am getting hit by this bug in the flash chip
http://lists.infradead.org/pipermail/linux-mtd/2008-July/022252.html
The debug output is as follows:
U-Boot 2009.03dvl-00087-gd53876a-dirty (Apr 09
12 matches
Mail list logo
