From: Dan Malek <dan@mvista.com>
To: frowand@mvista.com
Cc: Joe Dery <jedery@mtu.edu>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Walnut user-space software problem
Date: Tue, 13 Feb 2001 13:55:11 -0500 [thread overview]
Message-ID: <3A89830F.CF2C0970@mvista.com> (raw)
In-Reply-To: 3A896367.95BE7CF4@mvista.com
Frank Rowand wrote:
> You really want to move forward to the rev D 405GP. The workarounds
> in the kernel for the rev C are not 100% effective.
Now you tell me :-). I've been struggling with cache related problems
for several weeks trying to get the software merged into the latest
tree.........
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-13 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 13:49 Walnut user-space software problem Joe Dery
2001-02-13 16:40 ` Frank Rowand
2001-02-13 18:55 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-13 14:14 Lucinda Schafer
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=3A89830F.CF2C0970@mvista.com \
--to=dan@mvista.com \
--cc=frowand@mvista.com \
--cc=jedery@mtu.edu \
--cc=linuxppc-embedded@lists.linuxppc.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).