From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Sector size with CFI driver?
Date: Wed, 01 Nov 2006 10:34:23 -0600 [thread overview]
Message-ID: <4548CC8F.1040001@freescale.com> (raw)
In-Reply-To: <200611011406.36814.sr@denx.de>
Stefan Roese wrote:
> Hmmm. I have never seen this message in U-Boot and can't find it in the
> current source code (something like "Command set is AMD/Fujitsu standard").
> Could be that I am missing something here.
>
> Please confirm that you are using the "official" git version of U-Boot and not
> any other repository. I suspect that you have an "updated" CFI driver not
> available in the official U-Boot version or a board specific FLASH driver.
That message is from a hacked up version of 1.1.3. Here's the code that
produces it:
void flash_print_info (flash_info_t * info)
{
int i;
if (info->flash_id != FLASH_MAN_CFI) {
puts ("missing or unknown FLASH type\n");
return;
}
printf ("CFI compatible FLASH (%d port width with %d chip width)\n",
(info->portwidth << 3), (info->chipwidth << 3));
printf ("Command set is ");
switch (info->vendor) {
case CFI_CMDSET_INTEL_EXTENDED:
printf ("Intel/Sharp extended\n");
break;
case CFI_CMDSET_AMD_STANDARD:
printf ("AMD/Fujitsu standard. ");
#ifdef POLLING_AMD_DQ7
printf ("Driver is polling DQ7 for status checking.\n");
#else
printf ("Driver is polling DQ6 for status checking.\n");
#endif
break;
I believe this code was part of the official 1.1.3.
However, looking at our patch for 1.1.3 (I didn't write that code), I see this
juicy tidbit for flash_get_size:
+
+#ifdef CONFIG_MPC8349ITX
+ for (i = num_erase_regions-1; i >= 0; i--) { /* top boot */
+#else
for (i = 0; i < num_erase_regions; i++) {
+#endif
+
Can someone explain this top boot vs bottom boot thing?
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2006-11-01 16:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 20:00 [U-Boot-Users] Sector size with CFI driver? Timur Tabi
2006-10-31 20:53 ` Tolunay Orkun
2006-10-31 21:40 ` Timur Tabi
2006-10-31 21:59 ` Tolunay Orkun
2006-10-31 23:08 ` Timur Tabi
2006-11-01 13:05 ` Stefan Roese
2006-11-01 16:34 ` Timur Tabi [this message]
2006-11-01 16:44 ` Ben Warren
2006-11-01 16:58 ` Timur Tabi
2006-11-01 17:02 ` Stefan Roese
2006-11-01 17:08 ` Timur Tabi
2006-11-01 17:41 ` Tolunay Orkun
2006-11-01 17:52 ` Timur Tabi
2006-11-01 17:47 ` Tolunay Orkun
-- strict thread matches above, loose matches on Subject: below --
2006-11-01 17:47 Yogi
2006-11-01 18:29 Yogi
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=4548CC8F.1040001@freescale.com \
--to=timur@freescale.com \
--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