From: David Woodhouse <dwmw2@infradead.org>
To: "Frederick Lefebvre" <flefebvre@irg.ca>
Cc: "linux-mtd" <linux-mtd@lists.infradead.org>
Subject: Re: build_fs failed
Date: Thu, 25 Apr 2002 09:31:06 +0100 [thread overview]
Message-ID: <4272.1019723466@redhat.com> (raw)
In-Reply-To: <001c01c1ebfc$00fea960$0201000a@flefebvre>
flefebvre@irg.ca said:
> Sorry, I included the full log in a message last week but did not get
> any answers so I tought I would ask a more precise question. I am
> including it below. Here are some of the problems I had that I think
> could be relevent in this case.
Sorry; I was away for a week and then I got distracted by real work :)
> Apr 19 14:50:59 junior kernel: Short read: 0x3c bytes at 0x000003c4
> instead of requested 44
That's the DiskOnChip driver refusing to perform a read command crossing
from one page to another. To get JFFS2 working on DiskOnChip, we'll need to
fix the hardware driver to read multiple pages in one go.
It shouldn't be hard - want to have a go at it?
--
dwmw2
prev parent reply other threads:[~2002-04-25 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 19:45 build_fs failed Frederick Lefebvre
2002-04-24 22:15 ` David Woodhouse
2002-04-25 1:53 ` Frederick Lefebvre
2002-04-25 8:31 ` David Woodhouse [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=4272.1019723466@redhat.com \
--to=dwmw2@infradead.org \
--cc=flefebvre@irg.ca \
--cc=linux-mtd@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox