Date: Wed, 6 Apr 2016 22:05:27 +0100 From: Craig Butler <craig001@lerwick.hopto.org> To: Russell Haley <russ.haley@gmail.com> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: information on accessing nand Message-ID: <57057A17.30709@lerwick.hopto.org> In-Reply-To: <CABx9NuQ5_2huROQzLYVh3JGfo=ho=neOyznj%2BR4KY-aia8Lusg@mail.gmail.com> References: <20160406214115.784b8a1f@zbox.lerwick.hopto.org> <CABx9NuQvEEUw1sBu_oUgOfRrvuWk1azMygPyYMmagSRhp=zSsQ@mail.gmail.com> <CABx9NuQ5_2huROQzLYVh3JGfo=ho=neOyznj%2BR4KY-aia8Lusg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/04/2016 21:55, Russell Haley wrote: > Sorry, hit the send key somehow. Did you see this: > https://wiki.freebsd.org/NAND ? > Hello Russ Thank you for your reply, yes I have seen that and looks very useful for the userland steps after this. The current problem is the nand on the dev board isn't recognised at all so I don't get the nand character devices populating /dev I think its something to do with the lack of ti,omap2 (compatible = "ti,omap2" in the dts) ... which needs the nfc_omap2 driver coding Unless I am barking up the wrong tree Regards Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57057A17.30709>