public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Vitaly Bordug <vbordug@ru.mvista.com>
To: manboot@ureach.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: Intel NOR flash(P30) query
Date: Tue, 16 Aug 2005 19:11:46 +0400	[thread overview]
Message-ID: <43020232.60908@ru.mvista.com> (raw)
In-Reply-To: <200508161441.KAA07341@www21.ureach.com>

I'm not an MTD guru, but...
Manjula D wrote:
> Hi All,
> Iam a newbie to mtd. We have a MPC8272 custom board with INTEL
> TE28F640P30B85 (P30-CFI compilant)NOR boot Flash and NAND flash
> with JFFS2 filesystem running linux-2.4.20-8.
> The NOR Flash need not have any partition/filesystem.
> My requirement is to have an application to copy an image from
> the NAND Flash to the NOR Flash.
> My current understanding is 
> Under RAM/ROM/Flash chip drivers on selecting, 
> Detect flash chips by Common Flash Interface (CFI) probe :
>   cfi_probe_init() will register with the mtd_chip_driver.
> Support for Intel/Sharp flash chips:
>   cfi_cmdset_0001.c contains the list of commands supported by
>   Intel.
>   
> 1) I need to understand how the application views the NOR flash
>     once it is registered as a mtd device.
The answer is trivial - as mtd device. You can enable support for mtd as 
character or block devices - thus you will have say /dev/mtdchar1 to 
work from your application.
> 2) Once i register as mtd_chip_driver how can i call the
>     read/write commands of the flash from the application?
see upper. It can be treated as an ordinary character device.
> 3) What is do_map_probe for and how is it different from
>     cfi_probe?
If the flash is used for firmware storage as well, you need to 
"partition" it with independent accesss to each part, keeping some of 
them write-protected. do_map_probe will apply the map, and will probably 
call cfi_probe for certain flash region - refer to google for details.
> 
>   -Thanks
>   Manju
> 
> ________________________________________________
> Get your own "800" number
> Voicemail, fax, email, and a lot more
> http://www.ureach.com/reg/tag
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
> 
> 


-- 
Sincerely,
Vitaly

  reply	other threads:[~2005-08-16 15:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 14:41 Intel NOR flash(P30) query Manjula D
2005-08-16 15:11 ` Vitaly Bordug [this message]
2005-08-16 15:57   ` Jörn Engel
2005-08-16 16:41     ` Todd Poynor
2005-08-16 18:55       ` Ralph Siemsen
2005-08-16 21:14         ` Todd Poynor
2005-08-18 22:43           ` Josh Boyer

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=43020232.60908@ru.mvista.com \
    --to=vbordug@ru.mvista.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=manboot@ureach.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