Re: stdio.h and kernel space

[ebiederman@lnxi.com (Eric W. Biederman)]

Munira Ahmed <munira.ahmed@radixs.com> writes:

> Hi Ralph
> 
> The datasheet you are referring to is the right one and S29WSxxxN is
> using JEDEC 42.4 command set standard.
> 
> I am not sure which JEDEC standard is impelmented by jedec_prob.c.
> 
> Further if a separate driver is provided on AMD's website it must
> significantly be different otherwise they could simply have mentioned
> about the one in jedec_probe.c

jedec_probe is not a ``driver'' it is a method of identify the kind
of device you have.  Like a pci bus scan just a little less reliable.
Unless something is very strange it is almost certain either jedec_probe
or cfi_probe will be able to recognize the id on your part, and direct
the mtd code to the appropriate driver.  Which is almost certainly
cfi_cmdset_0002.c.  If the command set really is different or provides
significant new features writing a new chip driver may be in order.

> I believe that S29WSxxxN's MirrirBit technology provides many more
> security features as yet not available in other flash technologies.

Possibly.  Although I don't quite see how more silicon to audit translates
into more security.  In any event audit the code I have mentioned and see
if it appears to be doing the correct thing for your chip.  

Eric