From mint-bounce@lists.fishpool.fi  Wed May  4 20:04:06 2005
X-Original-To: fnaumann@mail.boerde.de
Delivered-To: fnaumann@mail.boerde.de
Subject: Re: [MiNT] Loopback device for MiNT, request for comments
From: Evan Langlois <Evan@CoolRunningConcepts.com>
To: Patrice Mandin <mandin.patrice@wanadoo.fr>
Cc: Mint list <mint@fishpool.com>
In-Reply-To: <20050504172657.20fca75b.mandin.patrice@wanadoo.fr>
References: <20050429203536.75299a02.mandin.patrice@wanadoo.fr>
	 <Pine.NEB.4.62.0504292042040.13874@wh58-508.st.uni-magdeburg.de>
	 <20050430112745.4f25da2b.mandin.patrice@wanadoo.fr>
	 <Pine.NEB.4.62.0505041436090.13874@wh58-508.st.uni-magdeburg.de>
	 <20050504172657.20fca75b.mandin.patrice@wanadoo.fr>
Content-Type: text/plain
Date: Wed, 04 May 2005 13:02:44 -0500
Message-Id: <1115229765.4007.25.camel@taro.coolrunningconcepts.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.3 
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - esc14.midphase.com
X-AntiAbuse: Original Domain - fishpool.com
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - CoolRunningConcepts.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-To: mint-bounce@lists.fishpool.fi
X-original-sender: Evan@CoolRunningConcepts.com
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
X-Virus-Scanned: by amavisd-new at relay.boerde.de
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de
X-Spam-Status: No, hits=-1.0 tagged_above=-50.5 required=7.0 tests=AWL,
 BAYES_00
X-Spam-Level: 

On Wed, 2005-05-04 at 17:26 +0200, Patrice Mandin wrote:

> > > If not, how can I access the kernel_* functions from a xdd ?
> > 
> > You are right, they are only exported to the new style kernel
> > interface  (not the old one as still used by xfs/xdd). Anyway, before
> > you can write a  loopback driver we require block device support in
> > the kernel too.
> 
> Even putting the loop device in the core kernel (like /kern, /shm,
> etc...) would not work without this block device ? So, I'm stuck with my
> idea, no loopback device for MiNT.

MiNT probably needs a block device driver eventually.  We may even be
able to gain a slight speed improvement.  However, doing it right might
require a certain integration with the as-yet-unwritten virtual address
space / virtual-memory system.