From: Dave Wolfe <dwolfe@risc.sps.mot.com>
To: LinuxPPC-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Motorola Web Site
Date: Fri, 6 Aug 1999 16:20:49 -0500 [thread overview]
Message-ID: <19990806162049.A3976@miaow.risc.sps.mot.com> (raw)
In-Reply-To: <Pine.LNX.4.10.9907281254550.30083-100000@fwrsl-11.phx.mcd.mot.com>; from Matt Porter on Wed, Jul 28, 1999 at 01:05:39PM -0700
[ Matt Porter writes: ]
>
> On Wed, 28 Jul 1999, Wolfgang Denk wrote:
>
> > 3) Is Motorola going to extend it's Linux support to the embedded
> > controllers (MPC8xx, MPX82xx) ?
>
> I'm not speaking for Motorola Computer Group, but the idea is to
> support all current systems under Linux. For MPC8xx and MPC82xx
> processors, this means the MBX (8xx) and the announced MVME2100
> (82xx).
>
> Keep in mind that the various evaluation boards for 8xx and 82xx are
> produced by Motorola Semiconductor Processor Sector and any support
> for those products would have to come from them. I can tell you I
> have zero contact with them and don't even know if they can pronounce
> Linux. :)
Nor do I speak for SPS, but I asked around and here was the answer
I got. This person asked to remain anonymous, so obviously he's not
speaking for SPS either, but this is the current party line:
> Linux has been ported to the PowerPC (8xx) architecture by various
> third parties. Motorola Netcomm has no plans to actively port Linux to
> 8xx.
Netcomm is the group that manufactures, markets, distributes, and
supports 8xx and 82xx embedded processors. Obviously, a lot of lobbying
needs to be done to help them "get it", but software in a semiconductor
manufacturer is like an ethics committee at a political convention, they
know they've got to have it, but don't understand what it's good for. :-)
--
Dave Wolfe
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-08-06 21:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-27 22:05 Motorola Web Site Johnnie Peters
1999-07-27 21:25 ` Tim Waugh
1999-07-28 7:54 ` VALETTE Eric
1999-07-28 13:36 ` Wolfgang Denk
1999-07-28 20:05 ` Matt Porter
1999-08-06 21:20 ` Dave Wolfe [this message]
1999-07-29 14:03 ` Alan Cox
1999-07-29 14:03 ` Alan Cox
[not found] <4575832C8E71D111AC4100A0C96B512704A633F5@fmsmsx36.fm.intel.com>
1999-07-27 23:33 ` Johnnie Peters
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=19990806162049.A3976@miaow.risc.sps.mot.com \
--to=dwolfe@risc.sps.mot.com \
--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).