All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] "stacked" memory mapped flash assisted with GPIOs
Date: Sun, 20 Jan 2008 05:56:08 -0500	[thread overview]
Message-ID: <200801200556.11352.vapier@gentoo.org> (raw)

some Blackfin processors have an optional async memory controller which allows 
for up to 4 megs of memory to be mapped.  sometimes these 4 megs are not 
enough, so people extend this by hooking up the higher address pins to GPIOs.  
so if you want to map 8 megs of memory, the highest address pin would be tied 
to a GPIO line while the remaining address pins would be hooked up like 
normal directly to the processor.

there are a few ways i can implement this in u-boot (and ive prototyped a 
couple), but the question is which way to go.  i obviously dont want to pick 
one which will be rejected for $whatever-reason.

possibilities:
- add a command to manually toggle the GPIO lines
 * pros: simple to implement and requires no change to existing code
 * cons: requires user to manually toggle the address lines.  cannot access 
multiple flashes in a single command.  not sure if this would work with 
different types of flashes as the CFI code would only detect the first.
- have memory display / flash write commands toggle the GPIO lines
 * pros: user interface is transparent and not confusing by making it seem 
like 1 flash exists (think software raid 0).  able to use 1 write command and 
the lower layers will automatically split it across multiple flashes.  should 
work with multiple types of flashes.
 * cons: requires modification to cmd_mem.c and cfi_flash.c.

maybe someone else has other/better ideas for how to approach the issue.  i 
didnt seem to find anything relevant from google / bundled docs / wiki.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20080120/7f73af19/attachment.pgp 

             reply	other threads:[~2008-01-20 10:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-20 10:56 Mike Frysinger [this message]
2008-01-20 11:26 ` [U-Boot-Users] "stacked" memory mapped flash assisted with GPIOs Michael Schwingen
2008-01-20 20:04   ` Mike Frysinger
2008-01-20 21:28     ` Michael Schwingen
2008-01-21  5:57       ` Mike Frysinger
2008-01-21 12:00 ` Haavard Skinnemoen
2008-01-21 13:01   ` Mike Frysinger
2008-01-21 22:20     ` Haavard Skinnemoen

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=200801200556.11352.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.