| Message ID | 4C149152.9090501@freemail.hu |
|---|---|
| State | Accepted |
| Commit | 8c47161d67445b94df5e321117c4b27952a9e65a |
| Headers | show |
On Sun, 2010-06-13 at 10:05 +0200, Németh Márton wrote: > Signed-off-by: Márton Németh <nm127@freemail.hu> > --- > diff --git a/faq/general.xml b/faq/general.xml > index 1c0551f..be1a0d4 100644 > --- a/faq/general.xml > +++ b/faq/general.xml > @@ -225,7 +225,7 @@ release the chip again. > Some NOR chips power on with all of the eraseblocks in a locked state. > The MTD layer doesn't unlock these devices by default. If you are accessing > these devices from user-space, you can use the <CODE>flash_unlock</CODE> tool to > -unlock the MTD device(s). If you are using the MTD device as aw rite-able root > +unlock the MTD device(s). If you are using the MTD device as a write-able root > file-system you will either need to have the boot loader unlock the eraseblocks > before booting the kernel, or add code to the MTD map driver for your board to > unlock them. Pushed, thank you!
diff --git a/faq/general.xml b/faq/general.xml index 1c0551f..be1a0d4 100644 --- a/faq/general.xml +++ b/faq/general.xml @@ -225,7 +225,7 @@ release the chip again. Some NOR chips power on with all of the eraseblocks in a locked state. The MTD layer doesn't unlock these devices by default. If you are accessing these devices from user-space, you can use the <CODE>flash_unlock</CODE> tool to -unlock the MTD device(s). If you are using the MTD device as aw rite-able root +unlock the MTD device(s). If you are using the MTD device as a write-able root file-system you will either need to have the boot loader unlock the eraseblocks before booting the kernel, or add code to the MTD map driver for your board to unlock them.
Signed-off-by: Márton Németh <nm127@freemail.hu> ---