On 28/02/13 04:11, Philip, Avinash wrote:
> On Wed, Feb 27, 2013 at 20:42:01, Mark Jackson wrote:
>>
>> Okay, just tested 3v8 plus:-
>>
>> https://patchwork.kernel.org/patch/1931251/
>> https://patchwork.kernel.org/patch/1931221/
>> https://patchwork.kernel.org/patch/1931201/
>> and changed drivers
On Wed, Feb 27, 2013 at 20:42:01, Mark Jackson wrote:
> On 26/02/13 23:18, Stephen Rothwell wrote:
> > Hi Mark,
> >
> > On Tue, 26 Feb 2013 15:50:18 + Mark Jackson
> > wrote:
> >>
> >> Just tested the current next-20130226 on a custom AM335X board, and if I
> >> mount
> >> our JFFS2 image a
On 26/02/13 23:18, Stephen Rothwell wrote:
> Hi Mark,
>
> On Tue, 26 Feb 2013 15:50:18 + Mark Jackson wrote:
>>
>> Just tested the current next-20130226 on a custom AM335X board, and if I
>> mount
>> our JFFS2 image as read/write, the next reboot shows the image as being
>> corrupt.
>>
>> I
Hi Mark,
On Tue, 26 Feb 2013 15:50:18 + Mark Jackson wrote:
>
> Just tested the current next-20130226 on a custom AM335X board, and if I mount
> our JFFS2 image as read/write, the next reboot shows the image as being
> corrupt.
>
> If I reprogram the jffs2 image into NAND and only mount the
Just tested the current next-20130226 on a custom AM335X board, and if I mount
our JFFS2 image as read/write, the next reboot shows the image as being corrupt.
If I reprogram the jffs2 image into NAND and only mount the volume as read-only,
no corruption occurs and the system remains intact.
I ha
5 matches
Mail list logo