public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] post: new parallel nor flash test
Date: Tue, 10 May 2011 18:46:23 -0400	[thread overview]
Message-ID: <201105101846.24763.vapier@gentoo.org> (raw)
In-Reply-To: <20110510215942.18554D6F237@gemini.denx.de>

On Tuesday, May 10, 2011 17:59:42 Wolfgang Denk wrote:
> Mike Frysinger wrote:
> > > > This adds a simple parallel nor flash test to automatically verify
> > > > erasing/writing/reading of sectors.  The code is based on existing
> > > > Blackfin tests but generalized for everyone to use.
> > > 
> > > What exactly does the "parallel" in "parallel nor flash test" mean?
> > 
> > how it is connected to the processor
> 
> Are there any other types of NOR flashes?

"parallel" is the connection type to the processor meaning it may be directly 
addressed (has dedicated address and data lines).  "NOR" is simply the 
technology type.

serial flashes tend to be NOR flashes connected via a SPI bus.

then there are NAND flashes which tend to be connected via a dedicated NAND 
flash controller (NFC), but that isnt a hard line anymore either.  ive seen 
serial NAND flashes which means they connect via SPI.

> I mean, I have never heard anybody use this term before.  Maybe we can just
> omit it - I find it more confusing than helpful.

*shrug* i cant say i found that to be the same, but doesnt matter to me.  the 
point of saying "parallel nor" was to be explicit ... this post test is only 
for nor flashes connected directly to the processor using the u-boot 
include/flash.h standard.  it is not for spi nor flashes, nor is it for nand 
flashes of any type.

> > i didnt think calling malloc() would be OK since i need enough memory to
> > hold one sector ...
> 
> Just grabbing a random address in RAM is certainly not a proper way
> to allocate I/O buffers.  If you need them, and if your code design
> makes it even necessary to pass these buffers around (so you can not
> just put them on the stack which is what I would try to do) you have
> to use malloc().

considering the current test design blasts away at entire sectors, i didnt 
think putting a 128KiB buffer on the stack was kosher.  should be trivial to 
change it to malloc() ...
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20110510/9a819275/attachment.pgp 

  reply	other threads:[~2011-05-10 22:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10 20:08 [U-Boot] [PATCH] post: new parallel nor flash test Mike Frysinger
2011-05-10 20:17 ` Wolfgang Denk
2011-05-10 21:11   ` Mike Frysinger
2011-05-10 21:59     ` Wolfgang Denk
2011-05-10 22:46       ` Mike Frysinger [this message]
2011-05-10 23:35 ` [U-Boot] [PATCH v2] post: new " Mike Frysinger
2011-07-26 14:50   ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2012-02-01  7:47 [U-Boot] [PATCH] post: new parallel " Vaibhav Kothari
2012-02-01 16:59 ` Mike Frysinger
2013-05-18  6:40 Mathieu Clavette

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=201105101846.24763.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=u-boot@lists.denx.de \
    /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