mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jared Hulbert" <jaredeh@gmail.com>
To: "Josh Boyer" <jwboyer@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Advanced XIP File System
Date: Tue, 2 May 2006 22:11:06 -0700	[thread overview]
Message-ID: <6934efce0605022211q7b265ef5o76faf27cd421dab5@mail.gmail.com> (raw)
In-Reply-To: <625fc13d0605021756v7a8e0d7p1e9d8e4c810bc092@mail.gmail.com>

Accidentally replied just to Josh, sorry.  Included what was offline.

>>> From what I recall, XIP of the kernel off of MTD is limited to ARM.  I
>>> assume AXFS suffers the same restriction?
>>
>> I'm fairly certian it won't.  I don't see anything in the code (that
>> we aren't going to remove) that would cause that.  All it needs is
>> direct memory access to the volume.  I'll find out soon, I'm trying to
>> test it on a X86 UML system.
>>
>> The XIP awareness in the MTD isn't a requirement for XIP, it's a
>> requirement to XIP from flash you are going to write, erase or
>> otherwise mess with.
>
>So you're relying on the fact that the underlying flash chip won't
>change from the Read Array state?  What happens if someone tries to
>use AXFS on an MTD partition, which can cover only a portion of a
>chip.  That is a fairly common occurance for read-only root
>filesystems.  Other partitions (say JFFS2) on that chip will cause the
>chip state to change...

Right.  So that is exactly the case XIP Awareness is in the MTD to
fix, and it does so such that AXFS doesn't have to worry about it.

  parent reply	other threads:[~2006-05-03  5:11 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-02 21:53 Jared Hulbert
2006-05-03  0:00 ` Arnd Bergmann
2006-05-03  1:59   ` Jared Hulbert
2006-05-03  2:27     ` Josh Boyer
2006-05-03  5:04       ` Jared Hulbert
2006-05-03  8:31         ` David Woodhouse
2006-05-03 19:14     ` Pavel Machek
2006-05-04 16:32       ` Jared Hulbert
2006-05-03  0:56 ` Josh Boyer
2006-05-03  3:17   ` Nicolas Pitre
2006-05-03 10:41     ` Josh Boyer
2006-05-03 12:11       ` David Woodhouse
2006-05-03 15:45         ` Jared Hulbert
2006-05-03 15:52           ` David Woodhouse
2006-05-03 15:57           ` Nicolas Pitre
2006-05-03 16:01             ` David Woodhouse
2006-05-03 16:10               ` Nicolas Pitre
2006-05-03  5:11   ` Jared Hulbert [this message]
2006-05-03 12:50 ` Mark Lord
2006-05-03 15:33   ` Jared Hulbert
2006-05-03 13:05 ` Jörn Engel
2006-05-03 15:31   ` Jared Hulbert
2006-05-03 15:47     ` Jörn Engel
2006-05-03 15:58       ` Jared Hulbert
2006-05-03 17:03         ` Jörn Engel
2006-05-03 18:58           ` Jared Hulbert
2006-05-03 16:38 ` Jan Engelhardt
2006-05-03 18:54   ` Jared Hulbert
2006-05-03 23:17     ` Josh Boyer
2006-05-03 23:48       ` Jared Hulbert
2006-05-04  0:21         ` Josh Boyer
2006-05-03 22:49   ` David Woodhouse

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=6934efce0605022211q7b265ef5o76faf27cd421dab5@mail.gmail.com \
    --to=jaredeh@gmail.com \
    --cc=jwboyer@gmail.com \
    --cc=linux-kernel@vger.kernel.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®