From: Matt Porter <mporter@mvista.com>
To: Eugene Surovegin <ebs@innocent.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Status of 440GP port
Date: Tue, 2 Apr 2002 14:18:45 -0700 [thread overview]
Message-ID: <20020402141845.A12269@home.com> (raw)
In-Reply-To: <5.1.0.14.2.20020402113518.02aa3800@pop.prodigy.net>; from ebs@innocent.com on Tue, Apr 02, 2002 at 11:46:12AM -0800
On Tue, Apr 02, 2002 at 11:46:12AM -0800, Eugene Surovegin wrote:
>
> Hello all!
>
> Could anyone (probably MontaVista guys) give some information on status of
> IBM 440GP port?
>
> I checked yesterday bk://ppc.bkserver.net/linuxppc_2_4_devel tree and found
> some preparations for this port (e.g. 4xx->40x renaming).
There will be a few more preparation changes before the rest arrives.
> I understand that this effort is under way for quite some time but not yet
> released (or am I wrong?).
I wouldn't say it has been underway for "quite some time". 4-5 working
weeks is a short amount of development time for a new processor (at least
for me). :)
> We already have 440GP hardware and I'm eager to test linux on it (even be
> alpha/beta tester for this port).
>
> Any info will be greatly appreciated.
My showstopper list is down to a 1-2 entries. When those are exhausted,
it will be available for use/testing.
Regards,
--
Matt Porter
MontaVista Software, Inc.
mporter@mvista.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-02 21:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-02 19:46 Status of 440GP port Eugene Surovegin
2002-04-02 21:18 ` Matt Porter [this message]
2002-04-02 21:41 ` andrew may
2002-04-02 22:21 ` Matt Porter
2002-04-02 22:54 ` andrew may
2002-04-02 23:20 ` Matt Porter
2002-04-03 0:28 ` andrew may
2002-04-02 23:29 ` Frank Rowand
2002-04-03 0:08 ` Amit D. Chaudhary
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=20020402141845.A12269@home.com \
--to=mporter@mvista.com \
--cc=ebs@innocent.com \
--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).