From: "Dan Post" <djp.mtd@onemyth.net>
To: Nicolas Pitre <nico@cam.org>
Cc: linux-mtd@lists.infradead.org, "Eric W. Biederman" <ebiederman@lnxi.com>
Subject: Re: [RFC] refactoring MTD cmdset ops, jedec_probe, and cfi_probe
Date: Tue, 13 Jul 2004 09:33:59 -0800 [thread overview]
Message-ID: <20040713173359.M64485@onemyth.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0407131248030.18865-100000@xanadu.home>
On Tue, 13 Jul 2004 12:52:13 -0400 (EDT), Nicolas Pitre wrote
> On Tue, 13 Jul 2004, Dan Post wrote:
> > [L18 / hardware partitions]
>
> I committed support for that a while ago already. SMP and
> preemption safe too. Anything you think might be missing (besides
> the crude probing code that certainly could benefit from more work)?
Ahhh, I thought you reversed that :) Some must have slipped by. David, if
you're listening, I miss your lovely cvsweb interface... any word on when that
will be back up?
I'm downloading the latest snapshot as we speak. Maybe I'll have to wait
until tomorrow... ugly firewall doesn't let CVS through, so I'd miss a lot of
updates I think. At any rate, I'll check it out and give it a try.
Here is a preliminary 'missing' list:
OTP [protection register] support. I have some preliminary code that supports
reading / writing / locking / querying the primary + extended OTP space
(extended is only available on L18). It's targeted against an ancient version
of the MTD, but I've been updating it to work against my djp1. It's good
reference code, and the only thing that will change significantly is the code
that actually writes / reads the OTP bits. There are several functions on top
of that to make access to the two regions transparent and contiguous. I can't
hand out the OTP stuff today, but I'll push this up on my priority list. Also
todo is make OTP work on chips with only the primary OTP space (e.g. K3).
XIP. :) This is my job. It works in djp1, but needs porting to the modern
stuff.
Needs better probing code: I trust you on that one.
Dan
next prev parent reply other threads:[~2004-07-13 17:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 3:13 [RFC] refactoring MTD cmdset ops, jedec_probe, and cfi_probe Eric W. Biederman
2004-07-13 6:25 ` David Woodhouse
2004-07-13 7:05 ` Eric W. Biederman
2004-07-13 8:02 ` David Woodhouse
2004-07-13 14:23 ` Eric W. Biederman
2004-07-13 14:45 ` Thayne Harbaugh
2004-07-13 15:04 ` Eric W. Biederman
2004-07-13 15:21 ` Thayne Harbaugh
2004-07-13 15:40 ` Eric W. Biederman
2004-07-13 16:00 ` Eric W. Biederman
2004-07-14 5:44 ` Eric W. Biederman
2004-08-12 7:39 ` Eric W. Biederman
2004-07-13 15:25 ` Eric W. Biederman
2004-07-13 16:17 ` Josh Boyer
2004-08-12 7:13 ` Eric W. Biederman
2004-08-16 14:13 ` Josh Boyer
2004-07-13 16:36 ` Dan Post
2004-07-13 16:52 ` Nicolas Pitre
2004-07-13 17:33 ` Dan Post [this message]
2004-07-13 18:17 ` Nicolas Pitre
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=20040713173359.M64485@onemyth.net \
--to=djp.mtd@onemyth.net \
--cc=ebiederman@lnxi.com \
--cc=linux-mtd@lists.infradead.org \
--cc=nico@cam.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