From: Conn Clark <clark@esteem.com>
To: MTD Mailing List <linux-mtd@lists.infradead.org>
Subject: Re: Re: How does one mount an existing jffs2 partition so it is writeable?
Date: Tue, 20 Aug 2002 11:02:16 -0700 [thread overview]
Message-ID: <3D628428.312055B5@esteem.com> (raw)
In-Reply-To: 3D627BC7.DD6B6823@esteem.com
Conn Clark wrote:
>
> Christopher Hoover wrote:
> >
> > Do you need to unlock your flash before you can write to it? That's not
> > done automatically by mtd or jffs2. There's a diff in the ARM patch
> > system by me that might be applicable.
> >
> > -ch
> >
> > ______________________________________________________
> > Linux MTD discussion mailing list
> > http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
> This is what I needed to know and is probably the culprit. However my unlock
> utility is broken. I can tell this because it doesn't even try to move through
> the sectors in the partition like the lock command does.
>
> I think I have it under control now.
>
> Thanks.
>
> Conn
I meant to say move through the sectors like the erase command, however I
can see that the lock command works very similar to the unlock command. This
makes me suspect that I have something wrong in the kernel code.
here is what I have.
I am running on a MPC850 PowerPC processor.
I am using a single intel TE28F320C3BA110 flash chip mapped as a 16 bit device.
I am using kernel 2.4.19 from kernel.org with the shared zlib patch.
I had to change 2 lines in cfi_cmdset_0001.c from
extp->FeatureSupport = cfi32_to_cpu(extp->FeatureSupport);
extp->BlkStatusRegMask = cfi32_to_cpu(extp->BlkStatusRegMask);
to
extp->FeatureSupport = le32_to_cpu(extp->FeatureSupport);
extp->BlkStatusRegMask = le16_to_cpu(extp->BlkStatusRegMask);
in order to fix an endian issue.
I had to create a custom map driver as well.
Any ideas on what else I have to change to get the lock/unlock commands to work?
Thanks in advance,
Conn
--
*****************************************************************
If you live at home long enough, your parents will move out.
(Warning they may try to sell their house out from under you.)
*****************************************************************
Conn Clark
Engineering Stooge clark@esteem.com
Electronic Systems Technology Inc. www.esteem.com
Stock Ticker Symbol ELST
"clark@esteem.com" Copyright 2000 By Electronic Systems Technology
This email address may be used to communicate to Conn Clark
provided it is not being used for advertisement purposes, unless
prior written consent is given. This email address may not be
sold under any circumstances. All other rights reserved.
next prev parent reply other threads:[~2002-08-20 18:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 17:34 How does one mount an existing jffs2 partition so it is writeable? Conn Clark
2002-08-19 23:42 ` Jörn Engel
2002-08-20 0:01 ` Conn Clark
2002-08-20 0:25 ` Christopher Hoover
2002-08-20 10:21 ` David Woodhouse
2002-08-20 12:12 ` Jamey Hicks
2002-08-20 12:19 ` David Woodhouse
2002-08-20 13:12 ` Jörn Engel
2002-08-20 16:34 ` Christopher Hoover
2002-08-20 19:24 ` Jörn Engel
2002-08-20 21:45 ` Christopher Hoover
2002-08-20 21:46 ` David Woodhouse
2002-08-20 17:26 ` Conn Clark
2002-08-20 18:02 ` Conn Clark [this message]
2002-08-20 18:18 ` Christopher Hoover
2002-08-20 18:42 ` Conn Clark
2002-08-20 21:50 ` Christopher Hoover
2002-08-20 10:10 ` Jörn Engel
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=3D628428.312055B5@esteem.com \
--to=clark@esteem.com \
--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