From: Wolfgang Denk <wd@denx.de>
To: David Jander <david.jander@protonic.nl>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: FW: cpm_spi.c under kernel 2.6
Date: Thu, 20 Jan 2005 00:02:02 +0100 [thread overview]
Message-ID: <20050119230207.6202CC108D@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 19 Jan 2005 19:47:16 +0100." <200501191947.16167.david.jander@protonic.nl>
In message <200501191947.16167.david.jander@protonic.nl> you wrote:
>
> In u-boot there are two 8xx-SPI-drivers, one software and one in hardware, and
...
> I am starting to figure out the best way of fixing that mess. Is anyone busy
> with the same task?
You have better chances for a useful reply if you ask on the
U-Boot-Users mailing list instead.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
In theory, there is no difference between theory and practice. In
practice, however, there is.
prev parent reply other threads:[~2005-01-19 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 11:47 FW: cpm_spi.c under kernel 2.6 Christian-Hoffmann
2005-01-19 16:49 ` annamaya
2005-01-19 18:47 ` David Jander
2005-01-19 23:02 ` Wolfgang Denk [this message]
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=20050119230207.6202CC108D@atlas.denx.de \
--to=wd@denx.de \
--cc=david.jander@protonic.nl \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).