Hi Glenn,

do you use CFI to detect your SST-Flash? I stumbled on this problem half a year ago on 2.6.x, I found out that SST has quite an interesting interpretation of the CFI-Standard. Their devices have both sectors and eraseblocks, and their CFI-Struct lists both, so the sum of all sector sizes appears to be the double of what the devices reports as its capacity and the kernel rejects it.

Please find attached my patch for this, it is for 2.6.x but it will show the idea. It will partially disable CFI for the device and override the number of eraseblock sizes, then the detections works.

Greetings
  Peter

Attachment: cfi_cmdset_0002.patch
Description: Binary data

Attachment: cfi_probe.patch
Description: Binary data




On Jan 5, 2009, at 11:42 PM, Glenn Henshaw wrote:

I have just managed to update a system from an older 2.4 kernel to the most recent 2.4.34.5-uc0 version. It looks like there were some checks added to the AMD FLASH drivers that totally break SST FLASH devices.

1) Where is the best place to complain? Was the old functionality hidden somewhere? 2) Where is the best place to submit the patch to support SST 39VF320x and 39VF640x devices?

   ... Glenn

--
Glenn Henshaw                     Logical Outcome Ltd.
e: li...@logicaloutcome.ca     w: www.logicaloutcome.ca



_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev

_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev

Reply via email to