public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "J B" <mad_flasher@hotmail.com>
To: Wolfram.Gettert@fci.com, linux-mtd@lists.infradead.org
Subject: Re: Problem writing to flash with writeb()
Date: Tue, 12 Nov 2002 13:02:27 -0600	[thread overview]
Message-ID: <F132Y30kkZIhTrBoe2U00000281@hotmail.com> (raw)

>   	physmap_map.map_priv_1 = (unsigned 
>long)ioremap_nocache(WINDOW_ADDR,WINDOW_SIZE);
>
>	...
>
>	//Read Manufacturer and Device code
>	physmap_write8(&physmap_map,0x90,physmap_map.map_priv_1);

Are you sure you want to pass physmap_map.map_priv_1 as the address?  That 
would imply that the address you are writing 0x90 to is (2 * 
physmap_map.map_priv_1) because physmap_writeX will add map->map_priv_1 to 
whatever address you pass it.  If that is bigger than WINDOW_SIZE, I don't 
think the command will actually reach the flash chip because the address 
isn't mapped to a flash chip.  I am assuming you are using a cfi compliant 
flash chip and 0x90 is putting it into "Read Identifier Codes".  Try using 0 
for the address instead, which is what you did below.

>If I do it like this:
>
>	p = physmap_map.map_priv_1;
>	p[0] = 0x90;

Looks like this is the equivalent of:
physmap_write8(&physmap_map,0x90,0);


I could be very wrong however.  I still consider myself a newbie, so sorry 
if this doesn't make any sense.  Hope it helps though.


Josh

_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail

             reply	other threads:[~2002-11-12 18:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-12 19:02 J B [this message]
2002-11-12 19:26 ` Problem writing to flash with writeb() David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2002-11-13  8:12 Gettert, Wolfram
2002-11-12 16:18 Gettert, Wolfram

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=F132Y30kkZIhTrBoe2U00000281@hotmail.com \
    --to=mad_flasher@hotmail.com \
    --cc=Wolfram.Gettert@fci.com \
    --cc=linux-mtd@lists.infradead.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