linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: kingseft@samsung.co.kr
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Flash Device Driver
Date: Sat, 24 Mar 2001 02:37:42 +0100	[thread overview]
Message-ID: <20010324013748.59BB7281DC@denx.denx.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1933 bytes --]

In message <H00002af04b2e173@MHS> kingseft wrote:
>
>  I found Flash Device driver related files in linux-2.4.3-pre3-2001-03-11
>  I have Intel TE28F160B3(2MBytes, 16bit port size, bottom boot type) flash memory.
>
>  Question1:
>  Can I use my intel flash memory for your flash device driver?

I think it should run without any modifications.

>  I got flash vendor id : CFI_VENDOR_INTEL_STANDARD
>  so , I modified your code like this.
>   } else if ((primary_vendor == CFI_VENDOR_INTEL_SHARP_EXTENDED) ||
>            (primary_vendor == CFI_VENDOR_INTEL_STANDARD) ) {
>  Is it possible ??

Where did you modify code? Please show the  output  of  a  "diff  -u"
command!

>  Question2:
>  when kernel booted, I found this messages.
>  Found 1x16bit 2MBytes CFI Flash device of type Intel Standard at 0xFFE00000
>  registered flash device /dev/flasha (minor 0, 4 partitions)
>  and when I got shell prompt. I made like this.

This looks good, the flash has correctly been recognized.

>  I tried like this.
>  ls -al >> result.txt
>  cat result.txt >> /dev/flasha4

To use the auto-erase feature of the driver, you must  write  with  a
blocksize  that  is  a  multiple of the erase block size of the flash
chips.

Try something like

	dd if=result.txt of=/dev/flasha4 bs=128k conv=sync

>  cat /dev/flasha4
>  but I coudn't find my result.txt contents..
>  Is it impossible??

Probably the flash was not erased? Were there any error messages?

>  Questions3:
>  I read your README but I had a question.
>  Where can I find flash_erase ??
>  W. Denx wrote flash_erase /dev/flasha start_addr end_addr
>  Thanks for any comments and replyings...

See attachment.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Not one hundred percent efficient, of course ... but nothing ever is.
	-- Kirk, "Metamorphosis", stardate 3219.8


[-- Attachment #2: flash_tools.tar.bz2 --]
[-- Type: application/x-bzip2 , Size: 2713 bytes --]

             reply	other threads:[~2001-03-24  1:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-24  1:37 Wolfgang Denk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-24  1:13 Flash Device Driver kingseft

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=20010324013748.59BB7281DC@denx.denx.de \
    --to=wd@denx.de \
    --cc=kingseft@samsung.co.kr \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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;
as well as URLs for NNTP newsgroup(s).