Notes:
- assume device can only be opened once. ie. it's a bug to call
open() twice
I dont see why you should need to call any "open" routine since the dataflash is active before u-boot has even started and does not need any initialization sequence.
You load U-boot from the dataflash to the SDRAM so any initialization needed by the dataflash is already done before the first U-boot instruction is executed..
Thus you search for the dataflash at boot if support is enabled and then initialize the datastructures, and your done with it.
I'm going to do a trial implementation of that stuff discussed so far so I can post patches for review. At that point I'll be looking for feedback to decide if this is a direction worth pursuing further. If so, then I'll take a look at the protect/erase/etc features
I don't think anything trivial should be merged. It should be kept as a
Best Regards, Ulf Samuelsson ulf@atmel.com GSM: +46 (706) 22 44 57 Tel: +46 (8) 441 54 22 Fax: +46 (8) 441 54 29 Mail: Box 2033 174 02 Sundbyberg Visit: Kavallerivägen 24 174 58 Sundbyberg' Sweden