From owner-freebsd-embedded@freebsd.org Thu Jun 28 20:18:03 2018 Return-Path: Delivered-To: freebsd-embedded@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 C0E481026069 for ; Thu, 28 Jun 2018 20:18:03 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wr0-x241.google.com (mail-wr0-x241.google.com [IPv6:2a00:1450:400c:c0c::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 42B758C028 for ; Thu, 28 Jun 2018 20:18:03 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-wr0-x241.google.com with SMTP id p1-v6so6717723wrs.9 for ; Thu, 28 Jun 2018 13:18:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pdDzdZI1/Ka2OnXLTw7sKbAATtjN9vntfEnvbQqR7zE=; b=Iy0YWNr1nkgGUgjmYzjK5pyCG7PIdPpfU6uejWwE9t3jDCkQy/03CUC1m6s8u9UwYr V6AW/9ptOAaFQBAacBK4HWip8+KsKcmO6RjDAjjI+4uOICh2uNMNlOdKMGGGY/qaKJ4Q KyzTj7F0qjNPF0CPdrQnc49TFjxN8P3SCnYZz3yyCGy35DYXPXeegrR10ODtLe6Xv6ab /CZCkgEix3Y/BrhtwV1KZueuxDCfu64ApS4ia3SZZGbSxMTZcNuD34S06IV5o3WNIAxy 8i/yTJ9tA4Ws6nFaXWCmiwIm6HE3pEKbLdip/TApfgiRPH5rdYU/ERp+/qsgzqGS5vsm wLxw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pdDzdZI1/Ka2OnXLTw7sKbAATtjN9vntfEnvbQqR7zE=; b=dqV4nr5duEjeS6GXIKPczkjJd9+U2DAjQvUHHW85CkLbpuoGKAwT3pPVOR3cMWLeoD dYMOPmZ53nTAaqKgt8Cw9WAAlm/tIYK0Tkc8/75al2rWWU5oKUeQ2knNn/LKsAp9zUIY QueeIHde7S+oF8WjC+WbX5Sq8f2G5UZowoLIzFKBOE6JziL2d83EJ9DA4/D9ybWv17Cy KgPq7x0GU6FQU9a5j8wd7Tlrh5TXEbR35rU09UuAnA8AQ2/OnzQ7HOtzNNFL14Q3vX0h AST3qtzg2C5n5uB/Nj54C1BD/wLFC9iRISoiKrmRO9zyx+oIdkuxLHP71fEHbjE4181z VYMA== X-Gm-Message-State: APt69E2XfElslNAplY+5wWQ3Z3Kebr0eJ6M4/hPUxn948rKwVPNdPndk yEc8cKB4hSrcTTHlflA92a9RRLFgtV5GwKFoH/Y= X-Google-Smtp-Source: AAOMgpfgaMFE7ylgcBjW+2RvyZ9BRYRN1vBHqlS+nUho3H52dUk4xG+k2qWfWU1i6uk56MntnzrvXpPUB44IFtPsu5o= X-Received: by 2002:adf:acc3:: with SMTP id o61-v6mr10331142wrc.34.1530217082147; Thu, 28 Jun 2018 13:18:02 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Adrian Chadd Date: Thu, 28 Jun 2018 13:17:49 -0700 Message-ID: Subject: Re: Atheros AR93xx NAND support To: Gergely Kiss Cc: "freebsd-embedded@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2018 20:18:04 -0000 Hi, There's currently no support for the NAND chip. I started a driver, but i reached a point where I realised we'd have to churn our NAND layer a bit in order to get it working. The AR934X NAND controller isn't a dumb latch and wants to actually issue its own JEDEC commands and do DMA. -adrian On Wed, 9 May 2018 at 07:05, Gergely Kiss wrote: > > Hi, > > I have a home project about porting FreeBSD to my beloved Netgear > WNDR4300 V.1 board and would like to ask for a little bit of help. > > The board is basically an Atheros DB120 reference board with a few > minor modifications (eg. it does not have SPI flash on-board, only a > NAND chip and has custom designed, "patent pending" integrated > antennas) so I cloned the DB120 kernel configuration and modified to > match the parameters of the Netgear board. > > As the SPI flash chip is absent, I need to boot FreeBSD off the NAND > chip which works fine up to the point where the kernel is loaded but > the root filesystem (also residing on the NAND chip) cannot be mounted > because of the NAND controller not detected. > > I'm using FreeBSD CURRENT with the NAND framework and NANDFS support > enabled in the kernel configuration according to instructions found on > the NAND wiki page [1] but I still can't see the NAND controller > detected. > > Please advise. > > As per this [2] wiki page, the controller should be detected as > "ar934x_nfc0" but I can't see anything like that in the logs: > > "ar934x_nfc0: on apb0" > > Your help is much appreciated. > > Thanks, > Gergely > > [1] https://wiki.freebsd.org/NAND > [2] https://github.com/freebsd/freebsd-wifi-build/wiki/Atheros-ReferenceDB120 > _______________________________________________ > freebsd-embedded@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-embedded > To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@freebsd.org" From owner-freebsd-embedded@freebsd.org Thu Jun 28 20:46:18 2018 Return-Path: Delivered-To: freebsd-embedded@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 917EB1026D04 for ; Thu, 28 Jun 2018 20:46:18 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C17F8D3F6 for ; Thu, 28 Jun 2018 20:46:17 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22d.google.com with SMTP id q4-v6so6502617iob.2 for ; Thu, 28 Jun 2018 13:46:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=GGkGcbEYf0Ky9VjpIEvVFFehfhzDbhqGj4sa8IzbFUA=; b=rX4WIJB1vZvI1wHh/PpVIH2fIHlAtBsGXGD4pO/LS4SASubq7gK8FPPE2T8WK0THaK zsjFGmg52F+SD9vvS1poBiPxRYlYhHlIC8gz7FXcDwHdXB2lc6h8jC/abPL+RrtYh0Wu GLlBqLiJq4QDqBp7kWVAL8x+i/sCpnM+dnAdc3oHG3F/3oRyVPi0QiYXaASznKfSdmgN CgCS3+CKraHZxnqkisKwwSO2RegdQsa+WhQFCaTDDB7lNqdsRptnAZFiuhRFU3f72NW+ pppwo23y5Y2rZ54aNLdtNYJGs8nIEQ9PHC92AyK9bJb2caTLcRsuIJwPtVKONyzHRwtJ q+Vg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=GGkGcbEYf0Ky9VjpIEvVFFehfhzDbhqGj4sa8IzbFUA=; b=rUFfwsRfCVV6q8LqzbMvdK2oSAm4ijXGe7YCxqYQ3Nkk95qr1HP6cB3j8dy0REkg/n yQdlYb4ZyYxEkyHwFtnrjE5sublk8jRvm/xAME7bdA4FsbClRiLcskSGGxd+girZjtQE o09pVeDOuMPDMTdiAbmRESIR6uYDInvIThs6MaUX+dy8vOAYhlinbXoiY3Eo5E5nnRzc OL8VxPBpRq+ckDFo7yIgp2o13Jy+oVzuuNj+rpfLUDDeRhygLEhQ0HIYsfTwoBwJogrx hb+VhdWAkxQ/9yRCrg9wxlCyqctZN1Db5eBe5QMk6rnr2Z1x3aUM7dvE9eQ/KsH/5gVC 1TYw== X-Gm-Message-State: APt69E3XTXGzdt08x9W/9HYE6QhqBHa4yFkGlSNSgdPhrcEoxSaCHofx cSNe2ui2+xj6qiZxsV6irCBIJkaUcieEbxJwS4QRnQ== X-Google-Smtp-Source: AAOMgpcuYdOp2BStU0PnSq0pELrfQSpwTd3bIoBxSjrmEpZF37Sh8C120o8+MKReR9Km9UMRKqR2gJXD4phhK+j7t5U= X-Received: by 2002:a6b:29c4:: with SMTP id p187-v6mr9686300iop.299.1530218777101; Thu, 28 Jun 2018 13:46:17 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:5945:0:0:0:0:0 with HTTP; Thu, 28 Jun 2018 13:46:16 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: From: Warner Losh Date: Thu, 28 Jun 2018 14:46:16 -0600 X-Google-Sender-Auth: b0eYe-I9doKcwxS5Gy-u3cw50Qg Message-ID: Subject: Re: Atheros AR93xx NAND support To: Adrian Chadd Cc: Gergely Kiss , "freebsd-embedded@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2018 20:46:18 -0000 If you had good access to datasheets, plus errata, plus vendor support, you might be able to get a quality implementation in 3-4 months time, which would include time to revamp our NAND system. It doesn't include time to revamp NANDFS, though, which would be another 2-3 months to get rock solid. Warner On Thu, Jun 28, 2018 at 2:17 PM, Adrian Chadd wrote: > Hi, > > There's currently no support for the NAND chip. I started a driver, > but i reached a point where I realised we'd have to churn our NAND > layer a bit in order to get it working. The AR934X NAND controller > isn't a dumb latch and wants to actually issue its own JEDEC commands > and do DMA. > > > > -adrian > > On Wed, 9 May 2018 at 07:05, Gergely Kiss wrote: > > > > Hi, > > > > I have a home project about porting FreeBSD to my beloved Netgear > > WNDR4300 V.1 board and would like to ask for a little bit of help. > > > > The board is basically an Atheros DB120 reference board with a few > > minor modifications (eg. it does not have SPI flash on-board, only a > > NAND chip and has custom designed, "patent pending" integrated > > antennas) so I cloned the DB120 kernel configuration and modified to > > match the parameters of the Netgear board. > > > > As the SPI flash chip is absent, I need to boot FreeBSD off the NAND > > chip which works fine up to the point where the kernel is loaded but > > the root filesystem (also residing on the NAND chip) cannot be mounted > > because of the NAND controller not detected. > > > > I'm using FreeBSD CURRENT with the NAND framework and NANDFS support > > enabled in the kernel configuration according to instructions found on > > the NAND wiki page [1] but I still can't see the NAND controller > > detected. > > > > Please advise. > > > > As per this [2] wiki page, the controller should be detected as > > "ar934x_nfc0" but I can't see anything like that in the logs: > > > > "ar934x_nfc0: on apb0" > > > > Your help is much appreciated. > > > > Thanks, > > Gergely > > > > [1] https://wiki.freebsd.org/NAND > > [2] https://github.com/freebsd/freebsd-wifi-build/wiki/ > Atheros-ReferenceDB120 > > _______________________________________________ > > freebsd-embedded@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-embedded > > To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@ > freebsd.org" > _______________________________________________ > freebsd-embedded@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-embedded > To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@freebsd.org > " > From owner-freebsd-embedded@freebsd.org Thu Jun 28 23:10:45 2018 Return-Path: Delivered-To: freebsd-embedded@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 15F21102BED3 for ; Thu, 28 Jun 2018 23:10:45 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 807957357F for ; Thu, 28 Jun 2018 23:10:44 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id d48c1ea7; Fri, 29 Jun 2018 01:10:42 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=qrv84cRBmidrTc29IjRLI+XqkEs=; b=nqEsETXATqM4oWbFuP+CGi8R2lqt eONxdHzJcTXcp8rS5+fbafJUo0PMAWc1IACYchB2YPbiuebvXQQUnNDFqv4W2XLm OkjuqksM/xjjjv+TLFRULUMS/jz7g82TwZ7M4X5OzLsCna65lHoDHgPP3JNIYTNm GBkWHUfbgqB/lfg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=FNC72SYG38jb0wp3h0q2GmCSRSyfGciWeM0Kzx00bsNtlXhwTEO8B0RV yAyMPppMizSLKU0+S1KhImtGCgi5IzXE90h4wRNL578eYO1uLp/EcA9P+cODDO1i NxAa/7etZfWvUYLSelWcBvC19V3JHoVmeZQgO061mq9hYXvcQn4= Received: from skull.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 041807f6 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Fri, 29 Jun 2018 01:10:42 +0200 (CEST) Date: Fri, 29 Jun 2018 01:10:42 +0200 From: Emmanuel Vadot To: Warner Losh Cc: Adrian Chadd , "freebsd-embedded@freebsd.org" Subject: Re: Atheros AR93xx NAND support Message-Id: <20180629011042.6e72464d7fc3294d96dd093f@bidouilliste.com> In-Reply-To: References: X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2018 23:10:45 -0000 On Thu, 28 Jun 2018 14:46:16 -0600 Warner Losh wrote: > If you had good access to datasheets, plus errata, plus vendor support, you > might be able to get a quality implementation in 3-4 months time, which > would include time to revamp our NAND system. It doesn't include time to > revamp NANDFS, though, which would be another 2-3 months to get rock solid. > > Warner I don't know the state of NAND in MIPS world but in the ARM world it's clearly fading out. But I've always wondered if instead of NANDFS one could do a geom_ftl (Flash Transision Layer) that will do all the nand stuff and then we can use UFS on it ? > On Thu, Jun 28, 2018 at 2:17 PM, Adrian Chadd > wrote: > > > Hi, > > > > There's currently no support for the NAND chip. I started a driver, > > but i reached a point where I realised we'd have to churn our NAND > > layer a bit in order to get it working. The AR934X NAND controller > > isn't a dumb latch and wants to actually issue its own JEDEC commands > > and do DMA. > > > > > > > > -adrian > > > > On Wed, 9 May 2018 at 07:05, Gergely Kiss wrote: > > > > > > Hi, > > > > > > I have a home project about porting FreeBSD to my beloved Netgear > > > WNDR4300 V.1 board and would like to ask for a little bit of help. > > > > > > The board is basically an Atheros DB120 reference board with a few > > > minor modifications (eg. it does not have SPI flash on-board, only a > > > NAND chip and has custom designed, "patent pending" integrated > > > antennas) so I cloned the DB120 kernel configuration and modified to > > > match the parameters of the Netgear board. > > > > > > As the SPI flash chip is absent, I need to boot FreeBSD off the NAND > > > chip which works fine up to the point where the kernel is loaded but > > > the root filesystem (also residing on the NAND chip) cannot be mounted > > > because of the NAND controller not detected. > > > > > > I'm using FreeBSD CURRENT with the NAND framework and NANDFS support > > > enabled in the kernel configuration according to instructions found on > > > the NAND wiki page [1] but I still can't see the NAND controller > > > detected. > > > > > > Please advise. > > > > > > As per this [2] wiki page, the controller should be detected as > > > "ar934x_nfc0" but I can't see anything like that in the logs: > > > > > > "ar934x_nfc0: on apb0" > > > > > > Your help is much appreciated. > > > > > > Thanks, > > > Gergely > > > > > > [1] https://wiki.freebsd.org/NAND > > > [2] https://github.com/freebsd/freebsd-wifi-build/wiki/ > > Atheros-ReferenceDB120 > > > _______________________________________________ > > > freebsd-embedded@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-embedded > > > To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@ > > freebsd.org" > > _______________________________________________ > > freebsd-embedded@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-embedded > > To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@freebsd.org > > " > > > _______________________________________________ > freebsd-embedded@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-embedded > To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@freebsd.org" -- Emmanuel Vadot From owner-freebsd-embedded@freebsd.org Thu Jun 28 23:28:22 2018 Return-Path: Delivered-To: freebsd-embedded@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 8E776102C5A9 for ; Thu, 28 Jun 2018 23:28:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1D98673B1F for ; Thu, 28 Jun 2018 23:28:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22c.google.com with SMTP id g7-v6so6815860ioh.11 for ; Thu, 28 Jun 2018 16:28:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Fp/YJ9bVi1tj8CJF0UVD7aoPwbA5CJX76mWyrGpX6Mk=; b=t+Rw4YWOpYe62SNeypqhuLVaV6Gs0FEgiwMAYefl/QnhDR5CZ90Tyf2jagV+aKEyYX yyE8LDY0meiWthf/ddjBz4bm+Qx6Cpx+bVOHUFFhJpxviAHHJSXqJHUYSJOX9vSi3sBK DwyP6sVXwv+gKAng2ZbMMvash9HC3P8mYhhlFsuW3lEdMNp/+aifK5nfbrs549kuxFUz FBqszX3RSGniTNL8BAXp+ISZB6J1S6RxZLdyHZ3V96zqfa3AxbnfILY5S543E4IJiqB5 BdVjlOnx0GtgRqKehoxRsRgB3hC/oSORfd5B3vOx34Ccjea2BPlvbfKwCkI+elw2q+rZ QiRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=Fp/YJ9bVi1tj8CJF0UVD7aoPwbA5CJX76mWyrGpX6Mk=; b=Cy/RyR6v9O/bLpPWZSg8iv6tKCS3x4/ESH2ikKZQmT1FBQFEznT1iOtOe7HTuqN/MK DInO0BAm/fA3UmdAvSWBezLa7HtrNPU43WACmpbdb5im3rpDg3llkifutCDYEP/OckET LIkh2NDiGOqWFGY7OUo9+cF5e0r2r9fnX4rmY6T23cTzic8ZIx9XDxBWkLfjYYCjAX7N 6x1XABmKk8io94Vj6p5f1YY8I0L04GFt+BzTAM2LcXpiirFvniNxyukqZBpIq67kFAOQ Tfw0xZ2/yh8hEktCrh4TQYMKlh5O+mV8lJHW/V0R7DmYF4YKbdStqhvKnJV8JXircJqI lOqg== X-Gm-Message-State: APt69E0xNbkEP6PA6h0o5yzxNlciew5qY+izPUJAeli1WsPS/QAvr1sK FL/XVEOjRTcD8jCvXns1Bdb9wueh7WoelYmqhFvadg== X-Google-Smtp-Source: AAOMgpcgIAOZKTJQAhgIVDBFfUUm7z3dnqrX+hYfisvE6gfPnQzuEuCLXvxH0mabro95+YiqC+qvfKMy1NYnqAiRjEM= X-Received: by 2002:a6b:29c4:: with SMTP id p187-v6mr10070625iop.299.1530228501377; Thu, 28 Jun 2018 16:28:21 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:5945:0:0:0:0:0 with HTTP; Thu, 28 Jun 2018 16:28:20 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20180629011042.6e72464d7fc3294d96dd093f@bidouilliste.com> References: <20180629011042.6e72464d7fc3294d96dd093f@bidouilliste.com> From: Warner Losh Date: Thu, 28 Jun 2018 17:28:20 -0600 X-Google-Sender-Auth: TBstzIztkOL5HQRG9BaPwJ6Ytkg Message-ID: Subject: Re: Atheros AR93xx NAND support To: Emmanuel Vadot Cc: Adrian Chadd , "freebsd-embedded@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2018 23:28:22 -0000 On Thu, Jun 28, 2018 at 5:10 PM, Emmanuel Vadot wrote: > On Thu, 28 Jun 2018 14:46:16 -0600 > Warner Losh wrote: > > > If you had good access to datasheets, plus errata, plus vendor support, > you > > might be able to get a quality implementation in 3-4 months time, which > > would include time to revamp our NAND system. It doesn't include time to > > revamp NANDFS, though, which would be another 2-3 months to get rock > solid. > > > > Warner > > I don't know the state of NAND in MIPS world but in the ARM world it's > clearly fading out. But I've always wondered if instead of NANDFS one > could do a geom_ftl (Flash Transision Layer) that will do all the nand > stuff and then we can use UFS on it ? That's logically appealing, but inefficient.The tables needed get kinda big and/or you have to do a lot of NAND I/O to get the mappings since you are hiding things from the UFS layer. NANDFS is a log filesystem, so it knows how about how to interact with the append store that's NAND. It was one of the biggest problems with Fusion I/O's driver: it had to keep this translation table in memory. It made crash recovery difficult. It created points of contention that limited performance. It could be done, but experience suggests caution... Warner