From owner-freebsd-current@FreeBSD.ORG Thu May 25 20:12:59 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A16D16B642; Thu, 25 May 2006 20:12:59 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 794F443D4C; Thu, 25 May 2006 20:12:53 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k4PKCoeM020869; Thu, 25 May 2006 15:12:51 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44760FC6.9080906@centtech.com> Date: Thu, 25 May 2006 15:12:54 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.2 (X11/20060506) MIME-Version: 1.0 To: Poul-Henning Kamp References: <4637.1148585085@critter.freebsd.dk> In-Reply-To: <4637.1148585085@critter.freebsd.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1484/Thu May 25 10:19:23 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: Alexander Leidinger , small@freebsd.org, current@freebsd.org Subject: Re: FreeBSD's embedded agenda X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 20:13:09 -0000 Poul-Henning Kamp wrote: > In message <4476036F.4090302@centtech.com>, Eric Anderson writes: > >> This sounds like an awefuly fun project to me. Is anyone (PHK?) willing >> to help me with some of the FreeBSD kernel related issues? If so, I'd >> like to work on this. > > As I said earlier, I'm still constrained by a NDA in this area. Being filesystems, or flash, or both? > It's not rocket science however, so if you sit down and read a couple > of flash-chip data-sheets carefully and think about the restrictions > and limitations, it shouldn't be too hard to come up with a good design. A pointer to a decent commonly used flash chip would help, although I'm sure I can find something with enough time plus google. > You can do most of the work in userland in a simulation, and once you > have the read/write/erase ratio where you want it, migrate the result > to the kernel. Good point.. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------