linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Do we remove from jedec_probe.c?
Date: Thu, 03 Jun 2010 16:44:00 +0200	[thread overview]
Message-ID: <4C07BFB0.2060107@gmx.net> (raw)
In-Reply-To: <20100526175320.GD24167@pengutronix.de>

Hi,

On 26.05.2010 19:53, Wolfram Sang wrote:
> now that Guillaume introduced cfi-support for some SST-flashes, I wonder if
> those can be removed from jedec_probe.c? Or should they stay for
> backward-compatibility?
>   

The userspace flashrom utility is getting support for those big SST NOR
flashes soon, so depending on whether you want these chips to host a
file system, flashrom may be an option.

Regards,
Carl-Daniel

-- 
http://www.hailfinger.org/

      parent reply	other threads:[~2010-06-03 14:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26 17:53 Do we remove from jedec_probe.c? Wolfram Sang
2010-06-01  9:55 ` Wolfram Sang
2010-06-01 10:13   ` Guillaume LECERF
2010-06-03 14:44 ` Carl-Daniel Hailfinger [this message]

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=4C07BFB0.2060107@gmx.net \
    --to=c-d.hailfinger.devel.2006@gmx.net \
    --cc=linux-mtd@lists.infradead.org \
    --cc=w.sang@pengutronix.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;
as well as URLs for NNTP newsgroup(s).