All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add some second source legacy flash chips 256x8
Date: Wed, 26 Aug 2009 22:10:42 +0200	[thread overview]
Message-ID: <20090826201042.8FCDD833DBD2@gemini.denx.de> (raw)
In-Reply-To: <1248205624-17062-1-git-send-email-niklaus.giger@member.fsf.org>

Dear Stefan,

In message <1248205624-17062-1-git-send-email-niklaus.giger@member.fsf.org> Niklaus Giger wrote:
> Signed-off-by: Niklaus Giger <niklaus.giger@member.fsf.org>
> ---
> 
> We tested some boot flashes as possible second source.
> As some had ids above 0x7f, we had to implement JEDEC JEP106Z in cfi_flash.c.
> I now that I just missed the merge window, but the patches are not urgent
> and I was away for a three week
> 
>  drivers/mtd/cfi_flash.c   |   16 +++++++++--
>  drivers/mtd/jedec_flash.c |   67 +++++++++++++++++++++++++++++++++++++++++++++
>  include/flash.h           |   10 ++++++-
>  3 files changed, 89 insertions(+), 4 deletions(-)

Any chance to pick this up for "next"?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Ever try. Ever fail. No matter. Try again. Fail again.  Fail  better.
                                                        -- S. Beckett

  reply	other threads:[~2009-08-26 20:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 19:47 [U-Boot] [PATCH] Add some second source legacy flash chips 256x8 Niklaus Giger
2009-08-26 20:10 ` Wolfgang Denk [this message]
2009-08-27  4:54   ` Stefan Roese
  -- strict thread matches above, loose matches on Subject: below --
2009-07-22  6:41 Niklaus Giger
2009-07-22  7:02 ` Wolfgang Denk
2009-07-22  8:01 ` Stefan Roese

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=20090826201042.8FCDD833DBD2@gemini.denx.de \
    --to=wd@denx.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 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.