From: dwmw2@infradead.org (David Woodhouse)
To: linux-mtd@lists.infradead.org
Subject: [PATCH] Fix stack usage for amd_flash.c
Date: 17 Mar 2003 08:47:56 +0000 [thread overview]
Message-ID: <1047890876.28282.5.camel@passion.cambridge.redhat.com> (raw)
In-Reply-To: <3C6BEE8B5E1BAC42905A93F13004E8AB01CAF576@mailse01.se.axis.com>
On Mon, 2003-03-17 at 08:36, Jonas Holmberg wrote:
> [ J??rn Engel wrote: ]
> > On Fri, 14 March 2003 16:05:10 +0000, David Woodhouse wrote:
> > > Also note that all but the CFI-based drivers are deprecated. We have
> > > old-style probes which allow us to use the CFI back-end drivers with
> > > non-CFI chips anyway.
> >
> > Right. But since 2.[567] is going towards 4k kernel stack, those
> > drivers should be fixed or revomed. If you don't remove it, I'll try
> > to fix it. :)
>
> We're still using the amd_flash-driver a lot because I haven't got time
> to try out the jedec_probe since the toggle-bit stuff was added in the
> CFI driver.
Yep, that's why I haven't actually _removed_ the other drivers; just
marked them deprecated. I'm sort of planning to remove them in 2.7.
> I made some rough tests just before that, and jedec_probe +
> CFI driver turned out to be much slower than amd_flash. But then the CFI
> driver was modified... I'll try to get some time to test them again soon
> and maybe even do something about it.
That'd be useful -- thanks. The CFI cmdset 0002 driver could do with a
little more loving :)
Btw, your mail landed in my spam folder and got bounced from the MTD
list due to missing In-Reply-To: and References: headers.
--
dwmw2
next parent reply other threads:[~2003-03-17 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C6BEE8B5E1BAC42905A93F13004E8AB01CAF576@mailse01.se.axis.com>
2003-03-17 8:47 ` David Woodhouse [this message]
2003-03-14 15:46 [PATCH] Fix stack usage for amd_flash.c Joern Engel
2003-03-14 16:05 ` David Woodhouse
2003-03-14 16:19 ` Joern Engel
2003-03-14 16:43 ` 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=1047890876.28282.5.camel@passion.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--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