diff for duplicates of <4E5319E8.50903@freescale.com> diff --git a/a/1.txt b/N1/1.txt index e60c331..99903a3 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,7 +1,9 @@ -于 2011年08月23日 00:19, Scott Wood 写道: +=E4=BA=8E 2011=E5=B9=B408=E6=9C=8823=E6=97=A5 00:19, Scott Wood =E5=86=99= +=E9=81=93: > On 08/22/2011 11:13 AM, Matthieu CASTET wrote: ->> Scott Wood a écrit : ->>> To eliminate it we'd need to do an extra data transfer without reissuing +>> Scott Wood a =C3=A9crit : +>>> To eliminate it we'd need to do an extra data transfer without reissu= +ing >>> the command, which Shuo was unable to get to work. >>> >> That's weird because our controller seems quite flexible [1]. @@ -27,16 +29,18 @@ > Shuo, what specifically did you try, and what did you see happen? > > -Scott -First, if we want to read 4K data with once command issuing, we can't +First, if we want to read 4K data with once command issuing, we can't=20 use HW_ECC. -Even if we use SW_ECC, we always get lots of weird '0xFF's between 1st +Even if we use SW_ECC, we always get lots of weird '0xFF's between 1st=20 2k and 2nd 2k data. They will cover the data in the head of 2nd 2K. - ------------------------------------------------------------------------------------- + -----------------------------------------------------------------------= +-------------- | xxxxxx ... 1st 2k xxxxxxx ... | ff ff ff ... ff xxxxxx 2nd 2k xxxxxxx | - ------------------------------------------------------------------------------------- + -----------------------------------------------------------------------= +-------------- -It is worse to write 4k data with once command issuing. It can't write +It is worse to write 4k data with once command issuing. It can't write=20 the 2nd data correctly. -Liu Shuo diff --git a/a/content_digest b/N1/content_digest index eaae7a0..50e0f2a 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -21,10 +21,12 @@ " dwmw2@infradead.org <dwmw2@infradead.org>\0" "\00:1\0" "b\0" - "\344\272\216 2011\345\271\26408\346\234\21023\346\227\245 00:19, Scott Wood \345\206\231\351\201\223:\n" + "=E4=BA=8E 2011=E5=B9=B408=E6=9C=8823=E6=97=A5 00:19, Scott Wood =E5=86=99=\n" + "=E9=81=93:\n" "> On 08/22/2011 11:13 AM, Matthieu CASTET wrote:\n" - ">> Scott Wood a \303\251crit :\n" - ">>> To eliminate it we'd need to do an extra data transfer without reissuing\n" + ">> Scott Wood a =C3=A9crit :\n" + ">>> To eliminate it we'd need to do an extra data transfer without reissu=\n" + "ing\n" ">>> the command, which Shuo was unable to get to work.\n" ">>>\n" ">> That's weird because our controller seems quite flexible [1].\n" @@ -50,18 +52,20 @@ "> Shuo, what specifically did you try, and what did you see happen?\n" ">\n" "> -Scott\n" - "First, if we want to read 4K data with once command issuing, we can't \n" + "First, if we want to read 4K data with once command issuing, we can't=20\n" "use HW_ECC.\n" - "Even if we use SW_ECC, we always get lots of weird '0xFF's between 1st \n" + "Even if we use SW_ECC, we always get lots of weird '0xFF's between 1st=20\n" "2k and 2nd 2k data.\n" "They will cover the data in the head of 2nd 2K.\n" - " -------------------------------------------------------------------------------------\n" + " -----------------------------------------------------------------------=\n" + "--------------\n" "| xxxxxx ... 1st 2k xxxxxxx ... | ff ff ff ... ff xxxxxx 2nd 2k xxxxxxx |\n" - " -------------------------------------------------------------------------------------\n" + " -----------------------------------------------------------------------=\n" + "--------------\n" "\n" - "It is worse to write 4k data with once command issuing. It can't write \n" + "It is worse to write 4k data with once command issuing. It can't write=20\n" "the 2nd data correctly.\n" "\n" -Liu Shuo -9ac6204e8771368d807d0be3cbef6f901048fe2013849ef0ed0fbdf923a4bb70 +9b4eb8989dace4af76cfee5679e9cec51d70c1fc70d9bb6c7423911f7b9edf00
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.