linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jared Hulbert" <jaredeh@gmail.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: "Greg Ungerer" <gerg@snapgear.com>,
	Linux-kernel@vger.kernel.org, linux-embedded@vger.kernel.org,
	linux-mtd <linux-mtd@lists.infradead.org>,
	"Jörn Engel" <joern@logfs.org>,
	tim.bird@am.sony.com, cotte@de.ibm.com, nickpiggin@yahoo.com.au
Subject: Re: [PATCH 00/10] AXFS: Advanced XIP filesystem
Date: Mon, 15 Sep 2008 12:43:00 -0700	[thread overview]
Message-ID: <6934efce0809151243h60a6e48bpf0c7600d4badf3c4@mail.gmail.com> (raw)
In-Reply-To: <20080915163421.GA13631@shareable.org>

>> >> I'm using Spansion MirrorBit S29GL128N, which reads at about 0.6 MByte/s.
>>
>> If you are using a GL, you'll probably find our P33 a good fit and at
>> competitive prices to GL as I understand it.  That's I think 50Mhz.
>
> What's a GL?  Never heard of it - all I can think of is OpenGL :-)

S29_GL_128N

> I'm not sure if cache is an option with this device - but would it
> make a difference anyway?

Well the first read takes 100ns (plus the other chipset overhead
300ns) but other reads in a page are only an extra 25ns each.  So your
benefit is not from having the entire executable in cache it's from
having the next 7 instructions in the cacheline for only an extra 25ns
each instead of 400ns.

> Interesting, thanks.  I'm not sure it's possible to change the way NOR
> is being used with this chip, and it'll be a while before it's
> economical to replace the board with a new design.

Usually these things can be fixed in the bootloader or by hacking the
kernel to tweak the relevant chipset registers.

  reply	other threads:[~2008-09-15 19:43 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21  5:44 [PATCH 00/10] AXFS: Advanced XIP filesystem Jared Hulbert
2008-08-21  6:32 ` Frans Meulenbroeks
2008-08-21 19:32   ` Jared Hulbert
2008-08-22  2:04     ` Nick Piggin
2008-08-21  8:39 ` Dave Chinner
2008-08-21 14:19   ` Jared Hulbert
2008-08-21 14:31     ` Leon Woestenberg
2008-08-21 14:42       ` Jared Hulbert
2008-08-21 14:49       ` Geert Uytterhoeven
2008-08-21 10:25 ` Carsten Otte
2008-08-21 10:43   ` Nick Piggin
2008-08-21 12:53     ` Arnd Bergmann
2008-08-21 14:12       ` Jared Hulbert
2008-08-21 14:14         ` Arnd Bergmann
2008-08-21 14:13     ` Jared Hulbert
2008-08-22  2:32       ` Nick Piggin
2008-08-21 14:30   ` Jared Hulbert
2008-08-21 11:07 ` Jamie Lokier
2008-08-21 14:11   ` Jared Hulbert
2008-08-22  0:12     ` Greg Ungerer
2008-08-22  2:48       ` Jared Hulbert
2008-08-25  6:35         ` Greg Ungerer
2008-08-25 11:43           ` Jamie Lokier
2008-08-25 14:02             ` Greg Ungerer
2008-08-22 18:13       ` Jamie Lokier
2008-08-22 18:16         ` Jared Hulbert
2008-08-22 18:37           ` Jamie Lokier
2008-08-22 18:43             ` Jamie Lokier
2008-09-12 21:52               ` Jared Hulbert
2008-09-15 16:34                 ` Jamie Lokier
2008-09-15 19:43                   ` Jared Hulbert [this message]
2008-09-19 19:20                     ` Trent Piepho
2008-09-16  6:57                   ` Ricard Wanderlof
2008-09-16 15:30                     ` Jared Hulbert
2008-09-12 20:17             ` Jared Hulbert
2008-09-15 16:40               ` Jamie Lokier
2008-08-21 23:46   ` Greg Ungerer
2008-08-22 18:10     ` Jamie Lokier
2008-08-22 14:54 ` Geert Uytterhoeven
2008-08-22 15:19   ` Arnd Bergmann
2008-08-22 16:51   ` Jared Hulbert
2008-08-25  9:37     ` Geert Uytterhoeven
2008-08-25 10:52       ` Carsten Otte
2008-08-25 12:16     ` David Woodhouse
2008-08-28 15:40     ` Geert Uytterhoeven
2008-09-02 15:37       ` Geert Uytterhoeven
2008-09-02 16:44         ` Jared Hulbert
2008-09-02 17:15           ` Jörn Engel
2008-09-02 17:47             ` Jared Hulbert
2008-09-02 18:33           ` Geert Uytterhoeven
2008-08-22 22:09   ` Will Marone
2008-08-25  7:23     ` Geert Uytterhoeven

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=6934efce0809151243h60a6e48bpf0c7600d4badf3c4@mail.gmail.com \
    --to=jaredeh@gmail.com \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=cotte@de.ibm.com \
    --cc=gerg@snapgear.com \
    --cc=jamie@shareable.org \
    --cc=joern@logfs.org \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=tim.bird@am.sony.com \
    /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).