From: Andrew Goodney <andrew@blueskylabs.com>
To: Vikram Mehta <vm6580@hotmail.com>
Cc: linux-mtd@lists.infradead.org
Cc: uclinux-dev@uclinux.org
Subject: Re: cfi_send_gen_cmd(0x98, 0x55, base, map, cfi, cfi->device_type, NULL); not workin
Date: Tue, 03 Jun 2003 11:20:08 -0700 [thread overview]
Message-ID: <3EDCE6D8.4010405@blueskylabs.com> (raw)
In-Reply-To: <1054633243.17921.34.camel@passion.cambridge.redhat.com>
David Woodhouse wrote:
>On Tue, 2003-06-03 at 10:23, Vikram Mehta wrote:
>
>
>>Hi joern,
>>Thanx
>>I agree this format was confusing. So let me put it simply
>>
>>in cfi_probe.c in cfi_probe_chip function
>>
>>cfi_send_gen_cmd(0xF0, 0, base, map, cfi, cfi->device_type, NULL);
>>Works
>>but
>>
>>cfi_send_gen_cmd(0x98, 0x55, base, map, cfi, cfi->device_type, NULL);
>>doesnot work.
>>It fails when __raw_writew(d, map->map_priv_1 +adr); is called in its
>>stack.
>>
>>
>
>>From the Cc I'm inferring you're using uCLinux. Are you running with
>your kernel in flash? Is your kernel in the _same_ flash chip as is
>being probed here?
>
>If so, it's not really surprising it doesn't work. As soon as you send
>the '0x98' command, your entire kernel turns into the CFI query results
>and it isn't really going to work too well :)
>
>
>
We had this problem as well on our uClinux systems. Once we changed to
running the kernel out of RAM our chips were detected properly.
The uClinux archives have a large amount of information on how to get
uClinux+MTD+JFFS(2) to play nicely together. I suggest searching the
online archive, as the subject comes up very often on that list.
Good luck,
Andrew Goodney
andrew@blueskylabs.com
-----------------------
www.blueskylabs.com
next prev parent reply other threads:[~2003-06-03 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 9:23 cfi_send_gen_cmd(0x98, 0x55, base, map, cfi, cfi->device_type, NULL); not workin Vikram Mehta
2003-06-03 9:40 ` David Woodhouse
2003-06-03 18:20 ` Andrew Goodney [this message]
2003-06-04 8:15 ` David Woodhouse
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=3EDCE6D8.4010405@blueskylabs.com \
--to=andrew@blueskylabs.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vm6580@hotmail.com \
/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