From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] M29EW flash is detected as 0xFF
Date: Fri, 01 Mar 2013 07:59:33 +0100 [thread overview]
Message-ID: <513051D5.6060807@denx.de> (raw)
In-Reply-To: <CAD6G_RSQM5h5mVLHzAXrykwEtZj8jKSguewGhbHxUFBk5SFAYw@mail.gmail.com>
Hi Jagan,
On 22.02.2013 16:32, Jagan Teki wrote:
>> I am able to detect the correct Manufacture ID and device ID with these changes.
>>
>> Bank # 1: CFI conformant flash (8 x 8) Size: 64 MB in 512 Sectors
>> AMD Standard command set, Manufacturer ID: 0x89, Device ID: 0x7E2301
>> Erase timeout: 4096 ms, write timeout: 2 ms
>> Buffer write timeout: 5 ms, buffer size: 1024 bytes
>>
>> But the 1024 bytes buffer size is another issues, as Numonyx CFI
>> wrongly mentioned 1024 instead of 256.
>> Any way that we can fix I guess for N29EW flashes..
>>
>> but how these changes impacts the other flashes i don't ..
>>
>> Please find the log message.
>
> I made a fix for hw cfi issue when device is operating in 8-bit mode,
> If the above changes are looks fine we may have this fix will solve
> the M29EW flashes operates under 8-bit mode.
>
> Could send your comments/views.
Not sure if I understood you correctly. So I have to ask some questions:
Did you use this patch?
http://patchwork.ozlabs.org/patch/140863/
Did it apply without issues to mainline U-Boot? Or did you have to make
some changes so that it can be applied? And did it fix the issues you
have seen before?
And did you have some make some further changes as well?
Thanks,
Stefan
next prev parent reply other threads:[~2013-03-01 6:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 11:51 [U-Boot] M29EW flash is detected as 0xFF Jagan Teki
2013-02-18 9:04 ` Jagan Teki
2013-02-18 9:57 ` Jagan Teki
2013-02-20 13:57 ` Stefan Roese
2013-02-20 17:25 ` Jagan Teki
2013-02-20 17:31 ` Jagan Teki
2013-02-20 18:14 ` Stefan Roese
2013-02-21 11:57 ` Jagan Teki
2013-02-22 15:32 ` Jagan Teki
2013-02-28 19:28 ` Jagan Teki
2013-03-01 6:59 ` Stefan Roese [this message]
2013-03-01 7:12 ` Jagan Teki
2013-03-01 7:18 ` Stefan Roese
2013-03-01 11:28 ` Jagan Teki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=513051D5.6060807@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox