From: Matthew Locke <mlocke@mvista.com>
To: Dan Malek <dan@mvista.com>
Cc: Jure Menart <jure@kom.org>,
linuxppc dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: linux-2.4 & 405gp & other stuff
Date: Fri, 17 Aug 2001 10:19:15 -0700 [thread overview]
Message-ID: <3B7D5213.3020602@mvista.com> (raw)
In-Reply-To: 3B7C6586.120CF7D4@mvista.com
Dan Malek wrote:
> Matthew Locke wrote:
>
>
>> Oak doesn't compile anymore.
>
>
> It did not long ago.......don't you have a board for testing so you
> can make the changes we need :-)?
>
Well, not in my office. If we ever find a working 10base2<->10baseT
converter, maybe we have a chance to keep the Oak code up to date:)
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-08-17 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-16 15:55 linux-2.4 & 405gp & other stuff Jure Menart
2001-08-16 21:42 ` Dan Malek
2001-08-16 23:16 ` Matthew Locke
2001-08-17 0:29 ` Dan Malek
2001-08-17 17:19 ` Matthew Locke [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=3B7D5213.3020602@mvista.com \
--to=mlocke@mvista.com \
--cc=dan@mvista.com \
--cc=jure@kom.org \
--cc=linuxppc-dev@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).