From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Roese Date: Tue, 11 Nov 2008 10:16:06 +0100 Subject: [U-Boot] OneNAND: Continuous locking scheme? In-Reply-To: <9c9fda240811110104v758544d6y72547a302d567c99@mail.gmail.com> References: <200811110943.22244.sr@denx.de> <9c9fda240811110104v758544d6y72547a302d567c99@mail.gmail.com> Message-ID: <200811111016.07132.sr@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Tuesday 11 November 2008, Kyungmin Park wrote: > > I'm still new to OneNAND and I couldn't > > find any reference to this continuous locking scheme in the OneNAND chip > > used here. Do you have any idea why this is not working for us? Do you > > know for sure if the KFG1216U2B (Dev-ID 0x25) really supports this > > continuous locking scheme? > > In onenand_check_features() > > default: > /* Some OneNAND has continuous lock scheme */ > if (!process) > this->options |= ONENAND_HAS_CONT_LOCK; > > It's some strange. As your version id is 0x22e. then process is 0x2. > umm maybe options field is not cleared before. please check this one. No, that's not the problem. The problem is that version_id was never saved in the onenand_chip structure. This is missing: @@ -1972,6 +1972,7 @@ static int onenand_probe(struct mtd_info *mtd) /* Flash device information */ mtd->name = onenand_print_device_info(dev_id, ver_id); this->device_id = dev_id; + this->version_id = ver_id; I'll submit a patch in a short while to fix this. Thanks. Best regards, Stefan ===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de =====================================================================