maser | 1 Apr 06:22 2008
Picon

Is a JFFS2 image needed for dataflash ?


Per this:

http://mailman.uclinux.org/pipermail/uclinux-dev/2003-January/014455.html

It looks like a JFFS2 FS is created on the fly on the
following commands: 

eraseall /dev/mtd0
mount -t jffs /dev/mtdblock0 /mnt
cp /usr/ls /mnt

If the JFFS2 FS is created on the fly on mounting to a
dataflash partition, why do we need to invoke the
mkfs.jffs2 utility to make a JFFS2 image for a
dataflash such as the AT45DBxxx?

The sysinit script could have something on the lines
of this :

/bin/mount -t jffs2 /dev/mtdblock2 /mnt

Thanks,
iyer

      ____________________________________________________________________________________
Like movies? Here's a limited-time offer: Blockbuster Total Access for one month at no cost. 
http://tc.deals.yahoo.com/tc/blockbuster/text4.com

______________________________________________________
(Continue reading)

maser | 1 Apr 06:26 2008
Picon

Is an erased partition on a dataflash identical to a jffs2 image ?


Per this :

Also, with respect to the above link,
http://mailman.uclinux.org/pipermail/uclinux-dev/2003-January/014455.html,
is an erased partition identical to a jffs2 image ? 

Thanks,
iyer

      ____________________________________________________________________________________
No Cost - Get a month of Blockbuster Total Access now. Sweet deal for Yahoo! users and friends. 
http://tc.deals.yahoo.com/tc/blockbuster/text1.com

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

ffileppo | 1 Apr 08:49 2008
Picon

Problems mounting JFFS2 (linux 2.6.22.6)

Hi,

I'm running kernel 2.6.22.6 on a PXA270 based board (custom Mainstone).

I'm having some issue trying to mount JFFS2

This is the command I use to build my jffs2 filesystem (starting from a working ramdisk placed in /mnt/):

mkfs.jffs2 -n -l -e 0x20000 --pad=0x01000000 -s 0x8000 -d /mnt/ -o rootfs.img

(I'm using latest release of mkfs.jffs2)

After flashing the image, I try to mount jffs2 filesystem on my embedded system:

mount -t jffs2 /dev/mtdblock2 /mnt

and I get:

kernel BUG at arch/arm/mm/consistent.c:488!                                          
Unable to handle kernel NULL pointer dereference at virtual address 00000000                                                                           
pgd = c0004000             
[00000000] *pgd=00000000                       
Internal error: Oops: 817 [#1]                             
Modules linked in:                 
CPU: 0    Not tainted  (2.6.22.6 #54)                                    
PC is at __bug+0x20/0x2c                       
LR is at 0x60000013                  
pc : [<c0025288>]    lr : [<60000013>]    psr: 60000013                                                      
sp : c77d7d20  ip : c0216bf8  fp : c77d7d2c                                          
r10: 00000080  r9 : c77fcfb8  r8 : 000fa000                                          
(Continue reading)

Martin Creutziger | 1 Apr 09:36 2008

Re: JFFS2: Kernel 2.6.24.2 Ooops during excessive write test

On Mon, 2008-03-31 at 19:23 +0400, Damir Shayhutdinov wrote:
> Hi!
> 
> 2008/3/31, Martin Creutziger wrote:
> >  I did some searching in the archive already and did not find anything,
> >  so I just post it myself in the hope that somebody can help me.
> >
> >  I am doing some excessive write tests on a PPC405EP running kernel
> >  2.6.24.2 at the moment. At irregular intervals, the "space accounting
> >  superblock info" gets "screwed" and I'd like to know why this happens
> >  and if it is fixable. And if not, that information might help me to
> >  decide whether or not this affects the planned application.
> >
> >  Thanks for the help,
> 
> Can you test this patch with your system?
> http://lists.infradead.org/pipermail/linux-mtd/2007-November/019866.html

Yes, will do that. I also activated verbose info on BUG() now, maybe
that gives additional information in case it goes wrong again.

I have to add, however, that it can take up to a week until the oops
occurs again, so be patient :)

Thanks so far,
Martin

DISCLAIMER:
Unless indicated otherwise, the information contained in this message is privileged and confidential,
and is intended only for the use of the addressee(s) named above and others who have been specifically
(Continue reading)

Laurent Pinchart | 1 Apr 10:47 2008

Re: [PATCHv2] powerpc: Describe memory-mapped RAM&ROM chips OF bindings

On Monday 31 March 2008 19:06, Sergei Shtylyov wrote:
> Hello.
> 
> Laurent Pinchart wrote:
> 
> > Signed-off-by: Laurent Pinchart <laurentp <at> cse-semaphore.com>
> > ---
> >  Documentation/powerpc/booting-without-of.txt |   13 ++++++++++++-
> >  1 files changed, 12 insertions(+), 1 deletions(-)
> > 
> > diff --git a/Documentation/powerpc/booting-without-of.txt 
b/Documentation/powerpc/booting-without-of.txt
> > index 7b4e8a7..3e1963b 100644
> > --- a/Documentation/powerpc/booting-without-of.txt
> > +++ b/Documentation/powerpc/booting-without-of.txt
> >  <at>  <at>  -57,7 +57,8  <at>  <at>  Table of Contents
> >        n) 4xx/Axon EMAC ethernet nodes
> >        o) Xilinx IP cores
> >        p) Freescale Synchronous Serial Interface
> > -	  q) USB EHCI controllers
> > +      q) USB EHCI controllers
> > +      r) Memory-mapped RAM & ROM
> 
>     Memory-mapped RA/RO Memory again? Should better drop this. :-)

You're quite picky, aren't you ? :-)

I suppose "Memory-mapped RA & RO" won't be accepted, so what about "Auxiliary 
RAM & ROM" ?

(Continue reading)

Trent Piepho | 1 Apr 11:18 2008
Picon

Re: [PATCHv2] powerpc: Describe memory-mapped RAM&ROM chips OF bindings

On Tue, 1 Apr 2008, Laurent Pinchart wrote:
> On Monday 31 March 2008 19:06, Sergei Shtylyov wrote:
>>>        p) Freescale Synchronous Serial Interface
>>> -	  q) USB EHCI controllers
>>> +      q) USB EHCI controllers
>>> +      r) Memory-mapped RAM & ROM
>>
>>     Memory-mapped RA/RO Memory again? Should better drop this. :-)
>
> You're quite picky, aren't you ? :-)
>
> I suppose "Memory-mapped RA & RO" won't be accepted, so what about "Auxiliary
> RAM & ROM" ?

Direct-mapped?

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

Laurent Pinchart | 1 Apr 14:39 2008

Re: [PATCHv2] powerpc: Describe memory-mapped RAM&ROM chips OF bindings

On Tuesday 01 April 2008 11:18, Trent Piepho wrote:
> On Tue, 1 Apr 2008, Laurent Pinchart wrote:
> > On Monday 31 March 2008 19:06, Sergei Shtylyov wrote:
> >>>        p) Freescale Synchronous Serial Interface
> >>> -	  q) USB EHCI controllers
> >>> +      q) USB EHCI controllers
> >>> +      r) Memory-mapped RAM & ROM
> >>
> >>     Memory-mapped RA/RO Memory again? Should better drop this. :-)
> >
> > You're quite picky, aren't you ? :-)
> >
> > I suppose "Memory-mapped RA & RO" won't be accepted, so what about "Auxiliary
> > RAM & ROM" ?
> 
> Direct-mapped?

Fine with me. Sergei ?

--

-- 
Laurent Pinchart
CSE Semaphore Belgium

Chaussée de Bruxelles, 732A
B-1410 Waterloo
Belgium

T +32 (2) 387 42 59
F +32 (2) 387 42 75
(Continue reading)

Sergei Shtylyov | 1 Apr 15:04 2008

Re: [PATCHv2] powerpc: Describe memory-mapped RAM&ROM chips OF bindings

Laurent Pinchart wrote:

>>>On Monday 31 March 2008 19:06, Sergei Shtylyov wrote:

>>>>>       p) Freescale Synchronous Serial Interface
>>>>>-	  q) USB EHCI controllers
>>>>>+      q) USB EHCI controllers
>>>>>+      r) Memory-mapped RAM & ROM

>>>>    Memory-mapped RA/RO Memory again? Should better drop this. :-)

>>>You're quite picky, aren't you ? :-)

>>>I suppose "Memory-mapped RA & RO" won't be accepted, so what about "Auxiliary
>>>RAM & ROM" ?

>>Direct-mapped?

> Fine with me. Sergei ?

    I agree. The only thing that somewhat worries me it that it will have no 
"compatible" prop...

WBR, Sergei
Grant Likely | 1 Apr 15:16 2008
Picon

Re: [PATCHv2] powerpc: Describe memory-mapped RAM&ROM chips OF bindings

On Mon, Mar 31, 2008 at 10:39 AM, Laurent Pinchart
<laurentp <at> cse-semaphore.com> wrote:
>
>  Signed-off-by: Laurent Pinchart <laurentp <at> cse-semaphore.com>
>  ---
>   Documentation/powerpc/booting-without-of.txt |   13 ++++++++++++-
>   1 files changed, 12 insertions(+), 1 deletions(-)
>
>  diff --git a/Documentation/powerpc/booting-without-of.txt b/Documentation/powerpc/booting-without-of.txt
>  index 7b4e8a7..3e1963b 100644
>  --- a/Documentation/powerpc/booting-without-of.txt
>  +++ b/Documentation/powerpc/booting-without-of.txt
>   <at>  <at>  -57,7 +57,8  <at>  <at>  Table of Contents
>        n) 4xx/Axon EMAC ethernet nodes
>        o) Xilinx IP cores
>        p) Freescale Synchronous Serial Interface
>  -         q) USB EHCI controllers
>  +      q) USB EHCI controllers
>  +      r) Memory-mapped RAM & ROM
>
>    VII - Specifying interrupt information for devices
>      1) interrupts property
>   <at>  <at>  -2816,6 +2817,16  <at>  <at>  platforms are moved over to use the flattened-device-tree model.
>                    big-endian;
>            };
>
>  +   r) Memory-mapped RAM & ROM
>  +
>  +    Dedicated RAM and ROM chips are often used as storage for temporary or
>  +    permanent data in embedded devices. Possible usage include non-volatile
(Continue reading)

Ram | 1 Apr 18:07 2008
Picon

nand tests causes "uninterruptible sleep"

Hi,
  I am using linux 2.6.22. I am testing my nand driver/nand device.
  I am using a arm based processor.

  To test my nand device, i am using fs-tests package that comes
  with mtd-utils git tree.

  These are standard filesystem regression tests.

  I am running the test to test a particular partition.

  During one of the tests: The test process hangs.
  When i do a ps -eal i get a -D against that process.
  That particular process remains in that state forever.

  I have eliminated all the infinte loops (checks for busy/read pin/nand reset)
  in my nand driver. I have tried to put debug prints to print
failures in my nand
  device. I dont see any failure prints when i run the tests.

  I tried doing "echo t > /proc/sysrq-trigger" i am appending the results.

  Basically, i am trying to isolate the code that is causing the process
  to go into an uniterruptible sleep state.

  It is to be noted that - When the fs-tests process has gone into
"uninterruptible
  sleep state" accessing the partion under test makes that process
  also go into the uninterruptible sleep state"

(Continue reading)


Gmane