lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 20 May 2015 16:43:41 +0200
From:	Antoine Tenart <antoine.tenart@...e-electrons.com>
To:	Ezequiel Garcia <ezequiel@...guardiasur.com.ar>
Cc:	Antoine Tenart <antoine.tenart@...e-electrons.com>,
	computersforpeace@...il.com, sebastian.hesselbarth@...il.com,
	dwmw2@...radead.org, boris.brezillon@...e-electrons.com,
	zmxu@...vell.com, jszhang@...vell.com,
	linux-arm-kernel@...ts.infradead.org,
	linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 07/12] mtd: nand: add Samsung K9GBG08U0A-M to nand_ids
 table

On Wed, May 20, 2015 at 04:24:09PM +0200, Antoine Tenart wrote:
> On Wed, May 20, 2015 at 11:09:08AM -0300, Ezequiel Garcia wrote:
> > On 05/20/2015 11:06 AM, Antoine Tenart wrote:
> > > On Sat, May 16, 2015 at 03:57:00PM -0300, Ezequiel Garcia wrote:
> > >> On 05/11/2015 11:58 AM, Antoine Tenart wrote:

snip.

> > >> I found a datasheet here for K9GBG08U0A that claims to support JEDEC
> > >> device identification (i.e. 0x90 0x40 and 0xEC 0x40 commands). Have you
> > >> tested it? Any reason you are adding full ID instead?
> > > 
> > > This nand looks like another one defined in this file, so a full ID make
> > > sure the right parameters applies here.
> > > 
> > 
> > Oh, so you say the NAND detects the device ID and uses those parameters,
> > instead of doing the JEDEC detection?
> 
> I just had a look on the datasheet, and I you're right, the nand should
> support JDEC. However I get a "No NAND device found" error when
> reverting this patch.
> 
> It seems nand_flash_detect_jedec() is not reading "JDEC" and is returning
> directly. I'm having a look at this.

So, I can read 'J', 'E', 'D' and 'E' but then I got 0xff's. So I tried
to only check of JEDE in nand_flash_detect_jedec() but the JEDEC
parameter page was then not valid.

Antoine

-- 
Antoine Ténart, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ