From: Xavier DEBREUIL (xde@inventel.fr)
Date: Mon Jul 10 2000 - 10:29:11 EDT
Hello Joe, when I started to work, I used a 256kbytes flash and the use of little boot sectors was interesting ; now, I think people use at least 1Mbytes ; as for me, I am using a 2Mbytes flash and I consider that a flash contains only 64kbytes sectors from 0 to 31 for example ; if the virtual 64kbytes sector 0 contains 4 little sectors, I erase the four sectors.... moreover, with this approach, you can use wathever flash you want since it is the same api for top or bottom boot block devices. Joe deBlaquiere wrote: > > I'm using blkmem.c to allow me to access and rewrite the flash memory. It > generally works very cleanly except that I couldn't figure out a nice way to > define a memory block device to be sectored heterogeneously. I'm using an > AMD flash that has a mixture of 8k and 64k blocks. As a workaround, I > defined two block devices with the same origin. one has small blocks and one > has big ones. This was good'nuff to get what I needed, but now I'm thinking > about doing it right. > > Am I missing something or is the current driver only for equal-sectored > (monolithic, right?) devices? > > Has anybody done this already, or should I start? > > Are there any other features I should be thinking about adding while I'm > under the hood? lock/unlock sectors? > > Joe deBlaquiere > WireSpeed Communications > 307 Wynn Drive > Huntsville, AL 35805 > voice : 256-704-9257 > fax : 256-837-3839 This message resent by the uclinux-dev@uclinux.org list server http://www.uClinux.org/
This archive was generated by hypermail 2.1.4 : Thu Sep 19 2002 - 13:19:14 EDT