From: Shane Nay <shane@agendacomputing.com>
To: Nicolas Pitre <nico@cam.org>
Cc: Shane Nay <shane@agendacomputing.com>, mtd@infradead.org
Subject: Re: Problems with cfi_cmdset_0001
Date: Sat, 2 Dec 2000 08:54:19 +0000 [thread overview]
Message-ID: <20001202085419.I4457@www.easysolutions.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0012021004200.16670-100000@xanadu.gn.com>; from nico@cam.org on Sat, Dec 02, 2000 at 15:23:33 +0000
Nicholas,
> Please consider using the following for better efficiency instead:
>
> cmd_adr = addr & ~(mtd->erasesize-1);
Will do. I was trying to think of the bit wise way to do it, but I was/am
kind of tired.
>
> This produces the same result but omits the division which is best to
> avoid
> on some CPUs which don't have a native instruction for it.
Tell me about it..., working on FPU less MIPS processor. So division in
general makes the hair on my neck stand out on end.
>
> What kind of arrangement do the probe function find? Does it actually
> tell
> you: "Found 2 x8 CFI devices at location 0 in 8 bit mode"? If not,
> you'll
> have to look at the probe code in cfi-probe.c. Carefully reordering the
> probe sequence might be required (I had to do it for the 32-bit buswidth
> case).
Ah, ic. No, I think it found it correctly, here's the output: (Paste
isn't working right now, have to turn on Emulate3Buttons again)
supports x8 and x16 via BYTE# with asynchronous interface
>
> My impression is that it had better advantages to be separate just to
> keep
> things as simple as possible.
I happen to agree with your position now :-). After a couple days of
drudging through stuff, I think simple is much better :). I don't know
whether to contribut this stuff, and use a macro to re-probe for the
commandset_xip, and then write a commandset_xip.c file and contribute that
or what precisely. It's pretty special purpose, so maybe just a patch
floating around for people to try out. In any case, I have to maintain the
patch against linux-vr cvs repository for our device after we ship, so
it'll be floating around on the agenda computing pages starting Real Soon
Now, aka, as soon as I suck it into a kernel release for our device, which
is likely to be Monday or Tuesday.
> Well... I don't know who is the official maintainer, but I think I
> contributed the largest mods recently.
Cool, then I'll make the patch, post it on one of our pages and drop a link
here. You guys can choose to include it in your stuff or not. I
understand Daves philsophical issue on this..., RAM is cheaper than flash
:-).
Thanks,
Shane.
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-12-02 15:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-02 5:01 Problems with cfi_cmdset_0001 Shane Nay
2000-12-02 7:29 ` Problems with cfi_cmdset_0001 && XIP kernel w/MTD working Shane Nay
2000-12-02 15:23 ` Problems with cfi_cmdset_0001 Nicolas Pitre
2000-12-02 8:54 ` Shane Nay [this message]
2000-12-03 3:42 ` including doc2001 and docprobe into the kernel Adam Agnew
2000-12-03 5:52 ` Levi Khatskevitch
2000-12-03 16:32 ` David Woodhouse
2000-12-03 17:19 ` Levi Khatskevitch
2000-12-03 18:13 ` David Woodhouse
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=20001202085419.I4457@www.easysolutions.net \
--to=shane@agendacomputing.com \
--cc=mtd@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 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.