public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michael Schwingen <rincewind@discworld.dascon.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Mixing CFI and non-CFI flashs?
Date: Tue, 6 Nov 2007 09:26:39 +0100	[thread overview]
Message-ID: <20071106082639.GA18904@discworld.dascon.de> (raw)
In-Reply-To: <200711060848.39359.sr@denx.de>

On Tue, Nov 06, 2007 at 08:48:39AM +0100, Stefan Roese wrote:
> > Okey, next version. The board-specific code may either fill out the
> > complete flash_info struct as in the previous patch, or (preferred), only
> > set info->portwidth, info->chipwidth and info->interface, in which case the
> > code will probe the flash by jedec IDs and look up a table in
> > jedec_flash.c. The table is a near copy of the table in the Linux
> > jedec_flash.c, with the removal of some unused fields.
> 
> Wouldn't it be better not to remove those unused fields? This way porting of 
> new devices from Linux to U-Boot would be easier.

Right. I was concerned about the size of the table - the complete table from
Linux contains *lots* of devices and may take up quite some space, so
stripping out unused fields should help a bit. If there is a consensus to
keep the fields to ease porting new parts, that is fine with me.

I think in the future we may need some ifdefs in the table to select
sub-sets of supported parts - if a board has a 29LV040, it is useful to have
support for other flash ROMS with similar layout and pinout that may be used
as alternatives, but completely different parts (eg. 29LV160) may be left
out.

cu
Michael

  reply	other threads:[~2007-11-06  8:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-02 20:53 [U-Boot-Users] Mixing CFI and non-CFI flashs? Michael Schwingen
2007-11-03  7:13 ` Stefan Roese
2007-11-03 15:00   ` Michael Schwingen
2007-11-05 11:21     ` Stefan Roese
2007-11-05 23:24       ` Michael Schwingen
2007-11-06  7:48         ` Stefan Roese
2007-11-06  8:26           ` Michael Schwingen [this message]
2007-11-06  8:59             ` Stefan Roese
2007-11-12 20:19               ` Michael Schwingen

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=20071106082639.GA18904@discworld.dascon.de \
    --to=rincewind@discworld.dascon.de \
    --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