linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David DeHaven <daved@trestle.com>
To: <linuxppc-dev@lists.linuxppc.org>
Subject: Re: altivec
Date: Tue, 20 Jul 1999 12:04:32 -0500	[thread overview]
Message-ID: <199907201701.KAA22748@meer.meer.net> (raw)


>Motorola or IBM will be happy to sell you a "non-apple non-MacOS PPC"
>machine for Linux, it's just nobody wants to pay the price. :)  A startup
>with a very low overhead could probably provide a reasonably priced mobo
>with an MPC107 and MPC750@400+mhz.  They would want to then sell them to a
>system manufacturer which already has volume discount commodity parts in
>their facility to build a consumer priced machine.  Selling 1-2 boards to
>each homebrew person isn't a business plan that will attract any
>investment, a decent volume distribution deal is needed.  Hrm, I wonder
>what the licensing cost of OF is or would it be better to do an open
>implementation of the standard...

The problem is, there's not enough demand right now to drive a non-PPC 
Linux box market. It's one of those things where we all sit around and 
say "Gosh, that would be cool if all of Intels plants just blew up 
suddenly and PowerPC would dominate the world!!!" It just aint gonna 
happen, at least not in the near future. (very much like the story of 
BeOS...)

As for OF, last I heard IBM will gladly license you to use and modify 
their OF implementation to your own needs. In the short term, it's 
cheaper and easier than trying to brew something up yourself.

-DrD-

[[ 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.   ]]

             reply	other threads:[~1999-07-20 17:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-20 17:04 David DeHaven [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-09-10 10:32 altivec Sacha Varma
1999-09-10 11:59 ` altivec Benjamin Herrenschmidt
1999-09-10 12:27   ` altivec Sacha Varma
1999-09-10 17:43     ` altivec Brad Midgley
1999-09-10 17:51       ` altivec Brad Midgley
1999-09-10 18:02       ` altivec Vitaly Oratovsky
1999-09-10 17:39 ` altivec David Edelsohn
1999-07-20 17:04 altivec David DeHaven
1999-07-20 17:04 altivec David DeHaven
     [not found] <Pine.PMDF.3.96.990715091130.538970498B-100000@uni.edu>
1999-07-15 16:11 ` altivec Matt Porter
1999-07-15 16:22   ` altivec Jason Haas
1999-07-15 16:29     ` altivec Josh Huber
1999-07-15 12:14       ` altivec sean o'malley
1999-07-15 17:36     ` altivec Matt Porter
1999-07-16  6:29   ` altivec Geert Uytterhoeven
1999-07-16 14:47     ` altivec Matt Porter
1999-07-09 11:29 altivec Sacha Varma
1999-07-09 12:14 ` altivec Holger Bettag
1999-07-09 13:04   ` altivec Mike DeSimone
1999-07-09 15:33     ` altivec Holger Bettag
1999-07-10  0:41       ` altivec Mike DeSimone
1999-07-14 10:17         ` altivec sean o'malley
1999-07-14 21:04           ` altivec Matt Porter
1999-07-14 21:42             ` altivec Josh Huber
1999-06-21 14:34 Altivec sean o'malley

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=199907201701.KAA22748@meer.meer.net \
    --to=daved@trestle.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).