From: "Mark Richards" <markr@massmicro.com>
To: "'Matthew S. McClintock'" <mattsm@arlut.utexas.edu>,
"'David Woodhouse'" <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: RE: MTD - DOC 2000 freezes on umount
Date: Thu, 22 Jan 2004 22:35:57 -0500 [thread overview]
Message-ID: <003a01c3e162$03ab7a00$6e01a8c0@solarwave> (raw)
In-Reply-To: <1074623299.4726.2.camel@chuck.arlut.utexas.edu>
I finally managed to get a good build running on the 2.4.24 kernel on RedHat
7.2, applying the MTD drivers. Here's what I had to do:
1. Copy the sources (not link them).
2. Include the JFFS drivers.
3. Use make oldconfig (make xconfig is not properly supported by one of the
MTD make files)
In a previous try I also had to fix one of the sources which had an extra
parameter defined, but in my finally-successful build this problem did not
show up.
So the problem I had - lock up when issuing a umount - is resolved, but it
was not easy getting there :)
I can't explain why the MTD version that ships with the 2.4.24 kernel has
this problem and I can't find any reference to it searching the newsgroups,
etc.
Mark Richards
> -----Original Message-----
> From: Matthew S. McClintock [mailto:mattsm@arlut.utexas.edu]
> Sent: Tuesday, January 20, 2004 13:28
> To: David Woodhouse
> Cc: Mark Richards; linux-mtd@lists.infradead.org
> Subject: RE: MTD - DOC 2000 freezes on umount
>
> On Tue, 2004-01-20 at 12:22, David Woodhouse wrote:
>
> > Bizarre. It's a define_bool, which is relatively new -- but not so new
> > it's not in 2.4.24, I thought. As you're only interested in the
> > DiskOnChip drivers, you're right that it doesn't affect you (assuming
> > that's what you meant:)
>
> I'm using the linuxppc_2_4_devel tree if that helps any.
>
> --
> Matthew S. McClintock <mattsm@arlut.utexas.edu>
next prev parent reply other threads:[~2004-01-23 3:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 2:23 MTD - DOC 2000 freezes on umount Mark Richards
2004-01-20 13:51 ` Mark Richards
2004-01-20 14:07 ` David Woodhouse
2004-01-20 15:11 ` Mark Richards
2004-01-20 18:04 ` Mark Richards
2004-01-20 18:10 ` David Woodhouse
2004-01-20 18:32 ` Mark Richards
2004-01-21 5:51 ` Mark Richards
2004-01-20 18:20 ` Matthew S. McClintock
2004-01-20 18:22 ` David Woodhouse
2004-01-20 18:28 ` Matthew S. McClintock
2004-01-23 3:35 ` Mark Richards [this message]
[not found] <E1Aj0eB-0006rS-Bn@pentafluge.infradead.org>
2004-01-20 20:01 ` Bob Beers
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='003a01c3e162$03ab7a00$6e01a8c0@solarwave' \
--to=markr@massmicro.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mattsm@arlut.utexas.edu \
/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