From: Brian Austin <brian@atllc.net>
To: <wolff@turnkiek.nl>
Cc: linux-mtd@lists.infradead.org
Subject: Re: problem using jffs2 on DiskOnChip
Date: Thu, 19 Dec 2002 06:21:38 -0600 [thread overview]
Message-ID: <200212190621.38374.brian@atllc.net> (raw)
In-Reply-To: <000301c2a773$6f5d5360$446410ac@lt-gw8l30j.turnkiek.nl>
On Thursday 19 December 2002 09:29, Carl Wolff wrote:
use ext3 instead. Depending onhow big your chip is.
or reiserfs
> Hello David,
>
> OK. Two questions:
> 1) Does JFFS2 actually work on a DiskOnChip?
> 2) Other alternatives? We need a powersafe filesystem on DiskOnChip.
>
>
> Thanks, and happy newyear, I'm going on holiday now.
>
> Carl.
>
> > -----Original Message-----
> > From: David Woodhouse [mailto:dwmw2@redhat.com]On Behalf Of David
> > Woodhouse
> > Sent: donderdag 19 december 2002 11:14
> > To: wolff@turnkiek.nl
> > Cc: linux-mtd@lists.infradead.org
> > Subject: Re: problem using jffs2 on DiskOnChip
> >
> > wolff@turnkiek.nl said:
> > > Short read: 0x10 bytes at 0x000001f0 instead of requested 44
> >
> > The DiskOnChip hardware driver hasn't been used much with
> > anything other
> > than NFTL. It appears not to do a full read if you ask it to
> > read a range
> > of data which crosses a page boundary. Fix it accordingly by
> > putting an
> > appropriate loop in instead of...
> >
> > /* Don't allow a single read to cross a 512-byte
> > block boundary */
> > if (from + len > ((from | 0x1ff) + 1))
> > len = ((from | 0x1ff) + 1) - from;
> >
> > --
> > dwmw2
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2002-12-19 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 19:03 problem using jffs2 on DiskOnChip Carl Wolff
2002-12-18 19:14 ` Russ Dill
2002-12-18 19:26 ` Carl Wolff
2002-12-19 10:14 ` David Woodhouse
2002-12-19 15:29 ` Carl Wolff
2002-12-19 12:21 ` Brian Austin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200212190621.38374.brian@atllc.net \
--to=brian@atllc.net \
--cc=linux-mtd@lists.infradead.org \
--cc=wolff@turnkiek.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.