All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Packham <judge.packham@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Handling dual die and single die flash on same board
Date: Tue, 07 Sep 2010 10:05:46 -0700	[thread overview]
Message-ID: <4C8670EA.5010501@gmail.com> (raw)

Hi,

I've run into a situation with a new design and I could use some pointers.

Our hardware designers have built prototypes with different flash
configurations. One possible configuration is a dual die 2x32MB the
other is a single die 1x64MB.

My u-boot config is currently setup for the 2x32MB case i.e.
CONFIG_SYS_MAX_FLASH_BANKS = 2, CONFIG_SYS_FLASH_BANKS_LIST = {base,
base+32MB}. The problem with this is that when flash_get_size is called
on the 1x64 chip it discovers the same chip the 2nd time around and
promptly walks off the end of the memory area I have allocated for it.

Is there any existing way to make the cfi_flash driver handle this
situation for me?

Thanks,
Chris Packham

             reply	other threads:[~2010-09-07 17:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-07 17:05 Chris Packham [this message]
2010-09-07 17:26 ` [U-Boot] Handling dual die and single die flash on same board Stefan Roese
2010-09-07 22:05   ` Chris Packham

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=4C8670EA.5010501@gmail.com \
    --to=judge.packham@gmail.com \
    --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.