mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Jared Hulbert <jaredeh@gmail.com>
Cc: Josh Boyer <jwboyer@gmail.com>, Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] Advanced XIP File System
Date: Wed, 03 May 2006 09:31:19 +0100	[thread overview]
Message-ID: <1146645079.16449.35.camel@shinybook.infradead.org> (raw)
In-Reply-To: <6934efce0605022204n233a6b04u4fafee8e07c0b594@mail.gmail.com>

On Tue, 2006-05-02 at 22:04 -0700, Jared Hulbert wrote:
> I plan to could do 'mount -t axfs /dev/mtdblock2 /mnt/axfs' and use
> the mtd to get the address to flash from map->cached or maybe
> mtd->point.  Personally I think this is a clean approach to mounting
> this fs.  Right now we do it like linear cramfs 'mount -t cramfs -o
> physaddr=0xDEADBEEF /dev/null /mnt/axfs' and then map flash ourselves
> with ioremap().  I'd like to enable a mode like this to in case you
> don't have MTD.   But I prefer the former. 

It makes sense. If you're going to use MTD drivers for other partitions
of the flash, you want to be able to co-ordinate with it so you know
when the flash is being written to. You want to be able to use its
partitioning rather than hard-coding the physical address and length of
what might be a dynamic partition. You want the MTD driver to know that
the device in question is in use.

-- 
dwmw2


  reply	other threads:[~2006-05-03  8:30 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 [this message]
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
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=1146645079.16449.35.camel@shinybook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=arnd@arndb.de \
    --cc=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®