From: David Brownell <david-b@pacbell.net>
To: "Hans-Jürgen Koch" <hjk@linutronix.de>
Cc: dwmw2@infradead.org, Andrew Victor <andrew@sanpeople.com>,
tglx@linutronix.de,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: drivers/mtd/devices/at91_dataflash26.c
Date: Thu, 10 May 2007 13:07:19 -0700 [thread overview]
Message-ID: <200705101307.19794.david-b@pacbell.net> (raw)
In-Reply-To: <200704271908.17403.david-b@pacbell.net>
On Friday 27 April 2007, David Brownell wrote:
> On Friday 27 April 2007, Hans-Jürgen Koch wrote:
>
> > > the m25p80 driver
> > > was pretty close to working with those Atmel devices too ...
> > > most of the commands are identical.
> >
> > Thanks for that hint, I'll have a look at the data sheet.
Any progress on that? I looked again, and yes most commands
are identical.
- That driver relies on an AT91-only SPI stack that's not
going upstream, instead of drivers/spi/atmel_spi.c;
- Driver can't even be selected on kernel.org kernel (!!);
- The m25p80 driver will need at most minor tweaks to
handle those AT26 (and AT25) series chips;
So 340ea370c2ce89d1c15fbf785460f2f74314ce58 should be reverted.
- Dave
next parent reply other threads:[~2007-05-10 20:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200704271812.26392.david-b@pacbell.net>
[not found] ` <200704280336.44913.hjk@linutronix.de>
[not found] ` <200704271908.17403.david-b@pacbell.net>
2007-05-10 20:07 ` David Brownell [this message]
2007-05-10 21:19 ` drivers/mtd/devices/at91_dataflash26.c Thomas Gleixner
2007-05-10 21:34 ` drivers/mtd/devices/at91_dataflash26.c David Brownell
2007-05-10 21:31 ` drivers/mtd/devices/at91_dataflash26.c Hans-Jürgen Koch
2007-06-25 2:51 ` drivers/mtd/devices/at91_dataflash26.c David Brownell
2007-06-25 6:35 ` drivers/mtd/devices/at91_dataflash26.c Hans-Jürgen Koch
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=200705101307.19794.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=andrew@sanpeople.com \
--cc=dwmw2@infradead.org \
--cc=hjk@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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