From mboxrd@z Thu Jan 1 00:00:00 1970 From: Albert ARIBAUD Date: Wed, 02 Dec 2009 12:07:22 +0100 Subject: [U-Boot] Mixed 8/16 bits NOR FLASH support In-Reply-To: <20091202093819.CE0154C025@gemini.denx.de> References: <1258239796-21528-1-git-send-email-albert.aribaud@free.fr> <20091118222158.A05573F6C2@gemini.denx.de> <4B1625EF.7060707@free.fr> <200912021015.34183.sr@denx.de> <20091202093819.CE0154C025@gemini.denx.de> Message-ID: <4B164A6A.80303@free.fr> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Wolfgang Denk a ?crit : > Dear Stefan Roese, >> I have to admit, that I'm not totally sure about this problem. Perhaps it >> would be best, if you would try to "fix" to the CFI code. To verify, if your >> theory is correct. And then post the resulting fix to the list, so that we can >> discuss it here. > > Agreed. Eventually the READ ID could / should be combined with the > 8/16 bit test, at least for this specific device ID. That is 'should', really, because the only way to tell apart a real pure word mode QRY from this faulty miwed-mode QRY is to try the READ ID, because i) it *is* correclty mixed-mode and ii) the Mfg and device ID are needed for verifying that we indeed had a faulty part. > Um... what does the Linux kernel code do in this case? Not entierly sure yet. I'll look. Amicalement, -- Albert.