mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Josh Boyer" <jwboyer@gmail.com>
To: "Robin Getz" <rgetz@blackfin.uclinux.org>
Cc: "Mike Frysinger" <vapier@gentoo.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-mtd@lists.infradead.org
Subject: Re: [patch] update CFI URI n mtd kconfig
Date: Thu, 13 Sep 2007 18:09:39 -0500	[thread overview]
Message-ID: <625fc13d0709131609t94b9fcbtc66c87ebe6e8f1e0@mail.gmail.com> (raw)
In-Reply-To: <200709131631.56867.rgetz@blackfin.uclinux.org>

On 9/13/07, Robin Getz <rgetz@blackfin.uclinux.org> wrote:
> On Thu 13 Sep 2007 14:28, Josh Boyer pondered:
> > On 9/12/07, Mike Frysinger <vapier@gentoo.org> wrote:
> > > Since AMD shunted its flash memory division, the URI in the mtd Kconfig is now
> > > broken, so the attached patch points people to Wikipedia.
> > >
> > > Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> > > ---
> > > diff --git a/drivers/mtd/chips/Kconfig b/drivers/mtd/chips/Kconfig
> > > index 479d32b..980117a 100644
> > > --- a/drivers/mtd/chips/Kconfig
> > > +++ b/drivers/mtd/chips/Kconfig
> > > @@ -11,8 +11,8 @@ config MTD_CFI
> > >           AMD and other flash manufactures that provides a universal method
>
> Even on the Intel page, it gives "Intel, AMD, Sharp, and Fujitsu" credit - why
> limit Sharp, and Fujitsu to "others"? (I would just take out everyone's name).

He wasn't changing that part of the option.  I'm fairly certain that
description has been there for years.  If you want to change it to be
a bit more "fair", feel free.

> > >           for probing the capabilities of flash devices. If you wish to
> > >           support any device that is CFI-compliant, you need to enable this
> > > -         option. Visit <http://www.amd.com/products/nvd/overview/cfi.html>
> > > -         for more information on CFI.
> > > +         option. For more information on CFI, visit:
> > > +         <http://wikipedia.org/wiki/Common_Flash_Memory_Interface>
> >
> > Erm, I'd rather not point to wikipedia.  Can you change it to point to:
> >
> > http://www.intel.com/design/flash/swb/cfi.htm
>
> Why not from the place that you can get the standard? http://jedec.org/
>
> or http://www.jedec.org/download/search/jesd68-01.pdf
>
> There isn't any point to pick one vendor - unless you work there, own
> stock, or one provides outstanding support (free hardware) for driver
> development. :)

I wasn't picking a vendor.  I was pointing out a well laid out webpage
that describes what CFI is and provides the spec for it.  If you want
to link directly to jedec, ok.

And no, I don't work at Intel, own stock in it, or know of them giving
out free hardware on a regular basis.  I do happen to like what Intel
is doing in regards to opening their drivers, but that has nothing to
do with this :).

josh

      parent reply	other threads:[~2007-09-13 23:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13  3:39 Mike Frysinger
2007-09-13 18:28 ` Josh Boyer
2007-09-13 20:31   ` Robin Getz
2007-09-13 21:01     ` Mike Frysinger
2007-09-14  9:07       ` Clemens Koller
2007-09-13 23:09     ` Josh Boyer [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=625fc13d0709131609t94b9fcbtc66c87ebe6e8f1e0@mail.gmail.com \
    --to=jwboyer@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rgetz@blackfin.uclinux.org \
    --cc=vapier@gentoo.org \
    /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

all inboxes | Powered by JetHome®