public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Zachary Landau <kapheine@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Multiple Flash Devices
Date: Mon, 21 Feb 2005 12:34:56 -0500	[thread overview]
Message-ID: <a04f56da05022109345c7fb8fc@mail.gmail.com> (raw)

Hello,

I'm currently working on getting u-boot to work from the internal
flash of the 5282.  I have it booting. and now I am working on getting
all the flash programming stuff setup.

I want to be able to access two (very different) flash devices.  I
want to be able to write to the internal flash device so that I can
save environmental variables, but I also want to be able to write to
the external flash so I can program data into it.

Is there a good method of setting up two flash devices at once?  As
far as I can tell, all the flash functions (like flash_print_info, for
example) can only be defined for one type of flash at a time.

There are two solutions I have thought of so far.  One of them is pick
whichever flash device is used the most and set that up normally.  For
the other flash, I could create different functions for it and in the
code that calls it I can make the necessary changes to call the right
functions.  I don't like this as much, because I'd have to put special
code various commands/ files to handle this.

The other option might be to create my own flash function wrappers
that call the appropriate flash function based on, for example, the
address passed into the function.

Has anyone else ran into this problem?  Perhaps that is another board
config that already deals with this?  I looked around, but there are a
lot of configs and I easily could have missed what I was looking for.

-- 
Zachary P. Landau <kapheine@gmail.com>

             reply	other threads:[~2005-02-21 17:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21 17:34 Zachary Landau [this message]
2005-02-23  8:17 ` [U-Boot-Users] Multiple Flash Devices Shawn Jin
2005-02-23 15:30   ` Zachary Landau
2005-02-24 22:33     ` Wolfgang Denk
2005-02-24 22:31 ` Wolfgang Denk
2005-02-25  2:20   ` Zachary Landau

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=a04f56da05022109345c7fb8fc@mail.gmail.com \
    --to=kapheine@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox