From: Tolunay Orkun <listmember@orkun.us>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] use CFI-Flash and board depended driver together
Date: Wed, 06 Dec 2006 10:57:10 -0600 [thread overview]
Message-ID: <4576F666.6030405@orkun.us> (raw)
In-Reply-To: <8496f91a0612051454h2da226c6w5f0f438a6f0a25c8@mail.gmail.com>
Matvejchikov Ilya wrote:
> Hi all,
>
> While I try to examine cfi_flash.c file I have found that
> flash_detect_cfi() function used uninitialized value of
> info->cmd_reset:
>
> flash_get_size()
> {
> ....
> if (flash_detect_cfi(info)) {
> ....
> switch (info->vendor) {
> ....
> info->cmd_reset = x_CMD_RESET;
> ....
> }
> }
> }
>
> flash_detect_cfi(info)
> {
> ....
> flash_write_cmd (info, 0, 0, info->cmd_reset);
> ....
> }
>
> Am I right? Or may be - 'Is it true?' :)
Good obvervation... It is true but mostly harmless (if the garbage in
cmd_reset does not happen to be a valid command). The reset command is
issued if the attempt to put flash in CFI mode has failed. The line
could be removed and it would still work. When I designed my last patch
flash_read_jedec_ids(), I've specifically avoided the info->cmd_reset
for this reason.
Actually, AMD_CMD_RESET should be applicable to most Intel parts as well
per CFI spec documents. I think the Linux MTD driver choose to send the
Intel sequence followed by AMD sequence back to back during the probe.
BTW, Were you able to read my proposals to extend the CFI flash driver
to handle non-cfi chips. I've only received one comment so far. I am
waiting to get more comments before I go ahead with coding effort....
Best regards,
Tolunay
next prev parent reply other threads:[~2006-12-06 16:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 11:30 [U-Boot-Users] [PATCH] use CFI-Flash and board depended driver together Yotam Admon
2006-12-05 22:54 ` Matvejchikov Ilya
2006-12-06 16:57 ` Tolunay Orkun [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-30 12:00 Jens Scharsig
2006-11-30 14:22 ` Timur Tabi
2006-11-30 14:52 ` Jens Scharsig
2006-11-30 17:24 ` Timur Tabi
2006-12-01 7:09 ` Jens Scharsig
2006-11-30 21:35 ` Tolunay Orkun
2006-12-05 0:55 ` Tolunay Orkun
2006-12-05 0:56 ` Tolunay Orkun
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=4576F666.6030405@orkun.us \
--to=listmember@orkun.us \
--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