[PATCH] add access to AMD secure silicon area

David Woodhouse dwmw2 at infradead.org
Tue Oct 15 06:36:44 EDT 2002


cdavies at altera.com said:
>  It should be, it matches the command sequence in the data sheet for
> the  AM29DL322D/323D/324D devices.  

And CFI_DEVICETYPE_X8 is always correct? No X16 devices?

>  Unfortunately not. There's no mention of it at all in the AMD primary
> vendor  specific extended query table v1.1 which is used on these
> devices. I don't  like this method either but in the absence of CFI
> info I don't have any  better ideas.

Argh. FFS. So AMD can't manage to get the fscking erasesize table correct 
in the CFI data, and they can't manage to add the appropriate fields to 
their own vendor-specific table to remove the need to keep the device ID 
tables which CFI was supposed to eliminate?

Would someone from AMD care to either contradict me or promise me 
faithfully that they've taken a baseball bat to whoever is responsible?

I suspect we need a new 'amd_is_bloody_stupid_probe' alongside jedec_probe 
and cfi_probe :)

--
dwmw2






More information about the linux-mtd mailing list