From: David Woodhouse <dwmw2@infradead.org>
To: Shane Nay <shane@agendacomputing.com>
Cc: mtd@infradead.org
Subject: Re: XIP kernel + MTD polling interest
Date: Tue, 28 Nov 2000 14:08:22 +0000 [thread overview]
Message-ID: <6193.975420502@redhat.com> (raw)
In-Reply-To: <20001128070007.E17376@www.easysolutions.net>
shane@agendacomputing.com said:
> What I'm really wondering is whether I should move to make patches
> off of the present versions of cfi_probe.c, cfi.h, cfi_cmdset_0001.c,
> or whether I should just fork them? (Basically, it follows the same
> logic, I just use macros to build copies of functions in memory also
> the code gets messy because I can't use else, can't use switch, and
> can't use return until the bottom of the function. Also can't use
> printk, or any kernel function while the flash is in query, or write
> mode)
If it can be cleanly merged with macros then it's probably worth doing.
Otherwise, it's best to fork it. The former is preferable.
Show me the code. Do you have a filesystem working XIP from flash yet?
I'm about to start looking at hacking romfs to prepopulate the page cache
with pages directly from the flash chip.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-11-28 14:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-28 7:00 XIP kernel + MTD polling interest Shane Nay
2000-11-28 14:08 ` David Woodhouse [this message]
2000-11-28 7:22 ` Shane Nay
2000-11-29 1:44 ` Nicolas Pitre
2000-11-28 8:53 ` Shane Nay
2000-11-28 15:58 ` David Woodhouse
2000-11-28 9:31 ` Shane Nay
2000-11-29 10:19 ` Shane Nay
2000-11-29 17:18 ` David Woodhouse
2000-11-29 11:19 ` Shane Nay
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=6193.975420502@redhat.com \
--to=dwmw2@infradead.org \
--cc=mtd@infradead.org \
--cc=shane@agendacomputing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.