From owner-freebsd-arch@freebsd.org Fri Nov 2 17:07:53 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF5A510FDE66 for ; Fri, 2 Nov 2018 17:07:53 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 516C475AEE for ; Fri, 2 Nov 2018 17:07:53 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1541178466; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=Vjki2+LbXQMvhwEylXgmLkFNSjygSoIRwg7gN0Tbc1DJs2qhSeW6gWbf35xAnHrXBfyWvqlM0FPKY B7OOXzMYZq8rv7umuFeRVqYfhcGho4TJ1KlmXsDP2HH5+4Zoeovpx175+pjOYIBX0LWPRovjNQ9vnB R2jiobJD6t6GXR3nxvTG+J5r42Q3U1jfQiOzcAfYGbdQec7nDAUT6fOf7ASZ9zkrcahoTZ3+LjOnlX wgVSK6JmXJ6zegauX5rzJLn4AN0oExVULs1L19on69+kwztKe9Dm1pWk9mx75uGJSWaOMpZWj1o/57 OvXXzt+FA3ur8r2ujH6B9E8ok2Fl8/Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:dkim-signature:from; bh=X07b3TrA8p1dBOZnDlen92ftMtUBD2lerV0gpTftu68=; b=jyJkKkNClG+68KkouLOKGh/If4R2m9PwCQW2ffUotCipXuGIM60GAUi87aPnhHBchW6AtUuRtAZaC kY/iiB7CuHHuGRhfQZJnrd6GLARCrbOQyWbs9vxFRN3wWk7OKnx1W2b/AHgfAPAHIiu6GHi6wAiwkE o4XeznGYCHjAIs5AJQrtzAKmK+34zO7mHsHeDe7CrTlGPXJ8BVbqa8Yzq3K2Yp2qN7LwAzouah6GEv +6UDXTSUSVlhVVrChzi/HYqowKcx2YCn0l4S6Szmxm8f8a3rPBEsuEvJdPIWxxXgneCmmicvRIBDnu 3Z4A4PzeOULkl1A32+Cw7UJdwNUokZw== ARC-Authentication-Results: i=1; outbound1.eu.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:from; bh=X07b3TrA8p1dBOZnDlen92ftMtUBD2lerV0gpTftu68=; b=T/rqcECnG1X6DosWq5u4v7oc00WU0axwqVUGPuaRsp49QYQ1s5Rpanwu045s95Xlo3TMqRdtcRvrb sFt5ZXJARExTZeSlbgYwLbs1EGRrvTJk2Y5hiAO3PuDArkeOYgNKr82NE7kuY7BXjH639/IBm7Vtld IdLH0vrNnynqZif+aWzvXahHAld85GK5lYy5a0qlgTVbYu9qjXWpdNuqH9m9qbHzAFayIGEJO702wG gI7koOgn4udTx6pkjfPnMtK+pzS72oiA97dnX8UGwttpEPCZC20yWqrzZVxDYe1VPdgt112lnZ4/yk P/9Ztn0Ptfechs3julB09IwZDJh+G3A== X-MHO-RoutePath: aGlwcGll X-MHO-User: cd50f87a-dec1-11e8-9048-075f73944867 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id cd50f87a-dec1-11e8-9048-075f73944867; Fri, 02 Nov 2018 17:07:42 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id wA2H7cMi072257; Fri, 2 Nov 2018 11:07:38 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1541178458.22340.242.camel@freebsd.org> Subject: Re: NANDFS -- Any current users? From: Ian Lepore To: Warner Losh , "freebsd-arch@freebsd.org" Date: Fri, 02 Nov 2018 11:07:38 -0600 In-Reply-To: References: Content-Type: text/plain; charset="ASCII" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2018 17:07:54 -0000 On Fri, 2018-11-02 at 11:01 -0600, Warner Losh wrote: > Are there any current users of NANDFS? This may be a good thing to ask in arm@ and mips@. Some old arm kernel configs include it, because some of the *Plug line of armv5 systems come with compatible nand parts on the board (but of course just having it in the kernel doesn't mean anyone is actually using it). We tried to use it at $work a few years ago, but it was too buggy to deploy. Fixes have been done to it since then, but I/we never re-tested because we had an alternate homebrew solution. -- Ian