public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Shane Nay <shane@agendacomputing.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Shane Nay <shane@agendacomputing.com>,
	Nicolas Pitre <nico@cam.org>,
	mtd@infradead.org
Subject: Re: XIP kernel + MTD polling interest
Date: Wed, 29 Nov 2000 10:19:17 +0000	[thread overview]
Message-ID: <20001129101917.H996@www.easysolutions.net> (raw)
In-Reply-To: <28079.975427082@redhat.com>; from dwmw2@infradead.org on Tue, Nov 28, 2000 at 15:58:02 +0000

MTD folk,

Okay, I've redone my stuff with the ELF section.  It's actually pretty
clean, and does full intialization up through the Intel command set.  I'm
still trying to figure out the best way to deal with calls to schedule. 
What I'm thinking is we already have the wrapper code for cfi_udelay, if we
were to replace all calls to schedule to this wrapper guy in
cfi_cmdset_0001.c, then it would be really clean, just get rid of that
if(current->need_resched) schedule(), to just go to udelay(us) #if defined
MTD_XIP.  That would be the only real change that would need to be made,
except flipping off interrupts when switching modes in MTD_XIP.

What do you guys think of doing this change?..., Any negatives?

Thanks,
Shane Nay.



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  parent reply	other threads:[~2000-11-29 17:16 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
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 [this message]
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=20001129101917.H996@www.easysolutions.net \
    --to=shane@agendacomputing.com \
    --cc=dwmw2@infradead.org \
    --cc=mtd@infradead.org \
    --cc=nico@cam.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