From owner-freebsd-arm@FreeBSD.ORG Wed Dec 12 22:58:45 2012 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CEAB3B0E for ; Wed, 12 Dec 2012 22:58:45 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id 2F90A8FC18 for ; Wed, 12 Dec 2012 22:58:38 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.5/8.14.5) with ESMTP id qBCMwa1A042932 for ; Wed, 12 Dec 2012 15:58:37 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id qBCMwO3r057011; Wed, 12 Dec 2012 15:58:24 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) Subject: Re: sheevaplug nand type not recognized? From: Ian Lepore To: Ronald Klop In-Reply-To: References: Content-Type: multipart/mixed; boundary="=-Z/Sbi9iTNzcr0Cb0Nh7b" Date: Wed, 12 Dec 2012 15:58:24 -0700 Message-ID: <1355353104.87661.468.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Dec 2012 22:58:45 -0000 --=-Z/Sbi9iTNzcr0Cb0Nh7b Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Wed, 2012-12-12 at 23:41 +0100, Ronald Klop wrote: > Hello, > > I just compiled a FreeBSD-10-current (src from 22 Nov.) kernel+world and > installed it on a usb stick. > It has NAND support compiled in, but I see no nand devices in /dev. > Dmesg does not list a lnand0 device like the example in > http://wiki.freebsd.org/NAND#NAND_Framework. > > Booting Debian finds this: > ... > NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB > 3,3V 8-bit) > Scanning device for bad blocks > Bad eraseblock 168 at 0x000001500000 > Bad eraseblock 169 at 0x000001520000 > Bad eraseblock 1193 at 0x000009520000 > 2 cmdlinepart partitions found on MTD device orion_nand > Creating 2 MTD partitions on "orion_nand": > 0x000000100000-0x000000500000 : "uImage" > 0x000000500000-0x000020000000 : "rootfs" > UBI: attaching mtd1 to ubi0 > ... > > I don't see this Samsung version in sys/dev/nand/nand_id.c. > Would it be easy to add it? I understand the manufacturer id and chip id, > but I don't know what I should change more. That looks like the same chip that's in my DreamPlug 1001N, the attached diff should fix it for you. -- Ian --=-Z/Sbi9iTNzcr0Cb0Nh7b Content-Disposition: inline; filename="dreamplug_nand.diff" Content-Type: text/x-patch; name="dreamplug_nand.diff"; charset="us-ascii" Content-Transfer-Encoding: 7bit Index: sys/dev/nand/nand_id.c =================================================================== --- sys/dev/nand/nand_id.c (revision 243920) +++ sys/dev/nand/nand_id.c (working copy) @@ -37,6 +37,8 @@ 0x20, 0x200, 0x10, 0x20, 0 }, { { NAND_MAN_SAMSUNG, 0xd3 }, "Samsung NAND 1GiB 3,3V 8-bit", 0x400, 0x800, 0x40, 0x40, 0 }, + { { NAND_MAN_SAMSUNG, 0xdc }, "Samsung NAND 512MiB 3,3V 8-bit", + 0x200, 0x800, 0x40, 0x40, 0 }, { { NAND_MAN_HYNIX, 0x76 }, "Hynix NAND 64MiB 3,3V 8-bit", 0x40, 0x200, 0x10, 0x20, 0 }, { { NAND_MAN_HYNIX, 0xdc }, "Hynix NAND 512MiB 3,3V 8-bit", --=-Z/Sbi9iTNzcr0Cb0Nh7b--