11 Mar, 2014
1 commit
-
The site-specific OOM messages are unnecessary, because they
duplicate the MM subsystem generic OOM message.Signed-off-by: Jingoo Han
Signed-off-by: Brian Norris
26 Oct, 2010
1 commit
-
Some old SST chips use 0x50 as sector erase command, instead
of 0x30. Make this value variable to handle such chips.Signed-off-by: Guillaume LECERF
Acked-by: Wolfram Sang
Signed-off-by: David Woodhouse
02 Aug, 2010
1 commit
-
Signed-off-by: Guillaume LECERF
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse
14 May, 2010
3 commits
-
SST 39VF160x and 39VF320x chips use vendorname id 0x0701 and alternative
unlock addresses. Add support for them in cfi_probe.c.Signed-off-by: Guillaume LECERF
Reviewed-by: Wolfram Sang
Signed-off-by: David Woodhouse -
Make the addresses used to enter Auto Select Mode variable to leave place
for handling chips using non-standard addresses.Signed-off-by: Guillaume LECERF
Reviewed-by: Wolfram Sang
Signed-off-by: David Woodhouse -
Move the code to enter Auto Select Mode down to be able to use cfi->cfiq
members to add support for chips using alternative sequence / unlock
addresses.Signed-off-by: Guillaume LECERF
Reviewed-by: Wolfram Sang
Signed-off-by: David Woodhouse
07 Aug, 2008
1 commit
-
They need to be exported, so let's give them less generic-sounding names
while we're at it.Original export patch, along with the suggestion about the nomenclature,
from Stephen Rothwell.Signed-off-by: David Woodhouse
06 Aug, 2008
1 commit
-
There are some CFI chips which require non standard procedures to get
into QRY mode. The possible way to support them would be trying
different modes till QRY will be read. This patch introduce two new
functions qry_mode_on qry_mode_off. qry_mode_on tries different commands
in order switch chip into QRY mode.So if we have one more "odd" chip - we just could add several lines to
qry_mode_on. Also using these functions remove unnecessary code
duplicaton in porbe procedure.Currently there are two "odd" cases
1. Some old intel chips which require 0xFF before 0x98
2. ST M29DW chip which requires 0x98 to be sent at 0x555 (according to
CFI should be 0x55)This patch is partialy based on the patch from Uwe
(see "[PATCH 2/4] [RFC][MTD] cfi_probe: remove Intel chip workaround"
thread )Signed-off-by: Alexey Korolev
Signed-off-by: Alexander Belyakov
Signed-off-by: David Woodhouse
05 Jun, 2008
1 commit
-
Once upon a time, the MTD repository was using CVS.
This patch therefore removes all usages of the no longer updated CVS
keywords from the MTD code.This also includes code that printed them to the user.
Signed-off-by: Adrian Bunk
Signed-off-by: David Woodhouse
23 Apr, 2008
2 commits
-
AMD/Spansion use a device id of 0x7e to indicate an extended device is
present at offset 0xe and 0xf in the query data.I've verified with Spansion that all their chips (mfr == 0x01) with an id
of 0x7e use it to indicate an extended id is present. What's more, there
are no chips with a NON-extended id that is the same as a different chip's
extended id. In other words, when the extended ID is present, one can
replace the normal id with the extended id without losing any information.
Which is what I've done.Signed-off-by: Trent Piepho
Signed-off-by: David Woodhouse -
Untested, but shouldn't break anything... Makes MTD_XIP arch
independent. I guess this is why xip_iprefetch() was made for.Signed-off-by: Paulius Zaleckas
Acked-by: Nicolas Pitre
Signed-off-by: David Woodhouse
11 Jan, 2008
1 commit
-
According to "Common Flash Memory Interface Publication 100" dated December 1,
2001, the interface code for x16/x32 chips is 0x0005, and not 0x0004 used so
far.Signed-off-by: Bartlomiej Sieka
Signed-off-by: David Woodhouse
01 Jul, 2006
1 commit
-
Signed-off-by: Jörn Engel
Signed-off-by: Adrian Bunk
14 May, 2006
1 commit
-
Signed-off-by: David Woodhouse
30 Nov, 2005
2 commits
-
This patch contains the following possible cleanups:
- every file should #include the headers containing the prototypes for
it's global functions
- make needlessly global functions staticSigned-off-by: Adrian Bunk
Signed-off-by: Andrew Morton
Signed-off-by: Thomas Gleixner -
Recent models of Intel/Sharp and Spansion CFI flash now have significant
bits in the upper byte of device ID codes, read via what Spansion calls
"autoselect" and Intel calls "read device identifier". Currently these
values are truncated to the low 8 bits in the mtd data structures, as
all CFI read query info has previously been read one byte at a time.
Add a new method for reading 16-bit info, currently just manufacturer
and device codes; datasheets hint at future uses for upper bytes in
other fields.Signed-off-by: Todd Poynor
Signed-off-by: Thomas Gleixner
07 Nov, 2005
1 commit
-
Signed-off-by: Thomas Gleixner
17 Apr, 2005
1 commit
-
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.Let it rip!
