public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Wolfgang Denk <wd@denx.de>
Cc: Paul Nash <paulnash@wildseed.com>,
	"Linux-MTD (E-mail)" <linux-mtd@lists.infradead.org>
Subject: Re: Intel sez: Synchronous Flash and XIP is the future -- thoughts?
Date: Mon, 16 Dec 2002 09:38:34 +0000	[thread overview]
Message-ID: <2466.1040031514@passion.cambridge.redhat.com> (raw)
In-Reply-To: <20021216092801.80539C6139@atlas.denx.de>

wd@denx.de said:
> Also you might find problems running recent (and future)  kernels  in
> XIP  mode  -  the kernel text segment is often not exactly read-only.
> Especially when you use one f the existing real-time extensions  (but
> not only then). It seems the amount of tweaking that is necessary for
> XIP  is  growing  with  each new kernel release - to a level where it
> becomes impractical. 

Also true. Of course we have to distinguish between XIP of file system 
pages and of the kernel -- I was ignoring the latter because it's even less 
sane than the former. If you ever want to write to the chip, you have to 
disable all interrupts and wait while the chip is busy. For up to 20 
seconds, in the case of a slow erase.

Of course, you could poll the interrupt controller while polling the flash
for completion, and suspend the flash operation to service pending
interrupts if they happen -- but that's really not the kind of thing that
should be encouraged. Until people start making flash chips were every part 
of the chip other than the part which is being erased/written is readable 
during an erase or write operation, XIP is just a silly buzzword, for any 
writable application.

--
dwmw2

  reply	other threads:[~2002-12-16  9:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-16  2:51 Intel sez: Synchronous Flash and XIP is the future -- thoughts? Paul Nash
2002-12-16  9:07 ` David Woodhouse
2002-12-16  9:27   ` Wolfgang Denk
2002-12-16  9:38     ` David Woodhouse [this message]
2002-12-16  9:56       ` Wolfgang Denk
2002-12-16 11:45         ` David Woodhouse
2002-12-16 17:21           ` Nicolas Pitre
2002-12-16 17:38             ` David Woodhouse
2002-12-16 18:06               ` Nicolas Pitre
2002-12-16 17:43             ` Wolfgang Denk
2002-12-16 18:07               ` Nicolas Pitre
2002-12-16 21:02           ` Charles Manning
2002-12-16 21:21             ` Russ Dill
2002-12-16 23:18               ` Charles Manning
2002-12-16 11:04     ` Michal Schulz
2002-12-16 11:16       ` Wolfgang Denk

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=2466.1040031514@passion.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=paulnash@wildseed.com \
    --cc=wd@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