From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Eric Bénard" <eric@eukrea.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] cfi_flash_intel: support 1024b buffer write
Date: Wed, 4 Aug 2010 10:00:51 +0200 [thread overview]
Message-ID: <20100804080051.GT14113@pengutronix.de> (raw)
In-Reply-To: <4C591B60.7090204@eukrea.com>
On Wed, Aug 04, 2010 at 09:48:48AM +0200, Eric Bénard wrote:
> Hi Sascha,
>
> Le 04/08/2010 09:42, Sascha Hauer a écrit :
>> On Fri, Jul 30, 2010 at 11:49:55AM +0200, Eric Bénard wrote:
>>> newer Numonyx Strataflash P3x have 1024b buffer, thus, it's possible
>>> to write a buffer size of 0x200 which the actual flash_write_cmd
>>> doesn't permit as it's limited to a uchar parameter.
>>
>> So I guess these chips have 16 data lines?
>>
> actual flash_write_cmd is also used on chips with 16 data lines (like
> P30 or P33 Numonyx).
Yes. I meant that 8 wouldn't be enough because the command gets
wider than 8bit.
>
>>
> >Unfortunately this won't work when two of these are parallel. You'd have
>> to duplicate the command for the upper 16 bit.
>>
> Does actual flash_write_cmd works when 2 chips are parallel ?
At least it's supposed to ;)
See flash_make_cmd, it iterates over all bytes in info->portwidth and
writes cmd or 0 into the buffer depending on info->chipwidth.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-08-04 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 9:49 Eric Bénard
2010-08-04 7:42 ` Sascha Hauer
2010-08-04 7:48 ` Eric Bénard
2010-08-04 8:00 ` Sascha Hauer [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-05-17 16:14 Eric Bénard
2010-05-17 16:19 ` Eric Bénard
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=20100804080051.GT14113@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=eric@eukrea.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