public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Shawn Jin <shawnxjin@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Multiple Flash Devices
Date: Wed, 23 Feb 2005 00:17:07 -0800	[thread overview]
Message-ID: <c3d0340b0502230017be3ee50@mail.gmail.com> (raw)
In-Reply-To: <a04f56da05022109345c7fb8fc@mail.gmail.com>

Zachary,

> 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.

You can use the addresses to differentiate which flash device are
accessed. Keep the same interfaces uboot has already had and just
develop your own functions to do the actual jobs.

> 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.

Nah, I wouldn't do that.

> 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.

That's what I did before on a EP8245 board. This way shields all the
differences.

Good luck,
-Shawn.

  reply	other threads:[~2005-02-23  8:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21 17:34 [U-Boot-Users] Multiple Flash Devices Zachary Landau
2005-02-23  8:17 ` Shawn Jin [this message]
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=c3d0340b0502230017be3ee50@mail.gmail.com \
    --to=shawnxjin@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