public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org, David McCullough <davidm@snapgear.com>
Subject: Re: [PATCH]: uClinux (MMU-less) patches against 2.5.28
Date: Fri, 26 Jul 2002 11:20:36 +1000	[thread overview]
Message-ID: <3D40A3E4.9050703@snapgear.com> (raw)
In-Reply-To: 9309.1027608767@redhat.com

Hi David,

 >David Woodhouse wrote:
 > > gerg@snapgear.com said:
 > >
 > > A new set of uClinux (MMU-less) patches agains 2.5.28. You can get 
it at:
 > >
 > > 
http://www.uclinux.org/pub/uClinux/uClinux-2.5.x/linux-2.5.28uc0.patch.gz
 > >
 > >
 > > Perhaps drop drivers/block/blkmem.c or justify reinventing the wheel?
 >
 > Indeed. That blkmem driver is a complete mess.
 > I can't think of any justification for it existing :-)
 > I'll work on cleaning that out.

You may have noticed some MAGIC_ROM_PTR patches in the mtd
driver code in this patch. This is to allow XIP for applications.
We have been support XIP for quite some time on uClinux, it
works really well.

A problem we have experienced with MTD is that the nature of
asynchronous writing to FLASH does not play nice with apps
runing XIP.  Any thoughts on how to deal with this?

(blkmem does synchronous writes so it doesn't suffer any
problem. It just locks everyone out for an in-ordinate amount
of time while it does the FLASH write).

Regards
Greg



------------------------------------------------------------------------
Greg Ungerer  --  Chief Software Wizard        EMAIL:  gerg@snapgear.com
SnapGear Pty Ltd                               PHONE:    +61 7 3435 2888
825 Stanley St,                                  FAX:    +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia              WEB:   www.snapgear.com



  parent reply	other threads:[~2002-07-26  1:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-25  6:56 [PATCH]: uClinux (MMU-less) patches against 2.5.28 Greg Ungerer
2002-07-25 14:52 ` David Woodhouse
2002-07-26  0:08   ` Greg Ungerer
2002-07-26  1:20   ` Greg Ungerer [this message]
2002-07-26  8:19     ` David Woodhouse
2002-07-26 10:39       ` Alan Cox
2002-07-26  9:39         ` David Woodhouse
2002-07-26 10:56           ` Alan Cox
2002-07-26  9:58             ` David Woodhouse
2002-07-26 14:50               ` Alan Cox
2002-07-26 14:03                 ` David Woodhouse
2002-07-26 17:11                   ` Alan Cox
2002-07-26 16:01                     ` David Woodhouse
2002-07-26 17:27                       ` Alan Cox
2002-07-26 16:27                         ` David Woodhouse
2002-07-26 15:08       ` gerg
2002-07-26 15:45         ` 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=3D40A3E4.9050703@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=davidm@snapgear.com \
    --cc=dwmw2@infradead.org \
    --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