Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Carsten Langgaard <carstenl@mips.com>
To: David Christensen <dpchrist@holgerdanske.com>
Cc: linux-mips@oss.sgi.com, license-discuss@opensource.org, kevink@mips.com
Subject: Re: Linux and the Sony Playstation 2
Date: Wed, 19 Jun 2002 11:15:16 +0200	[thread overview]
Message-ID: <3D104BA4.BEEAAB6C@mips.com> (raw)
In-Reply-To: 00e001c216f6$86594b40$0b01a8c0@w2k30g

The DVDs you get with the linux kit, contain all necessary hardware
documentation.

/Carsten


David Christensen wrote:

> Kevin:
>
> Kevin D. Kissell <kevink@mips.com> wrote on linux-mips@oss.sgi.com:
> > The Sony PS2 Linux kit has been shipping for nearly...
>
> If the PS2 is an open source platform, I would like to know that.
> However, I do not see Sony on the OSI approved license list:
>
>     http://www.opensource.org/licenses/index.php
>
> So, let me get out my soap box...
>
> When people say "Open Source", the first thing that comes to mind is
> software.  But, this is only one half of the equation.  The hardware
> must also be "open", or the concept doesn't work.  First, because
> attempting to write systems software without complete and accurate
> hardware documentation is an exercise in reverse engineering.  The
> community can better spend its time on documented hardware.  Second, and
> more importantly, because any intellectual property (IP) encumbrance
> will make the results pointless in the marketplace.
>
> Closed hardware breaks the community development model.  Vendors who
> provide a Linux distribution but keep their hardware proprietary cannot
> honestly claim "Open Source".  Vendors who fully disclose and freely
> license both their hardware and software have embraced "Open Source".
> As consumers, we vote with our dollars. As engineers, we further one
> cause or the other by our education, employment, and personal project
> choices.
>
> David Christensen
> dpchrist@holgerdanske.com

--
_    _ ____  ___   Carsten Langgaard   Mailto:carstenl@mips.com
|\  /|||___)(___   MIPS Denmark        Direct: +45 4486 5527
| \/ |||    ____)  Lautrupvang 4B      Switch: +45 4486 5555
  TECHNOLOGIES     2750 Ballerup       Fax...: +45 4486 5556
                   Denmark             http://www.mips.com

  parent reply	other threads:[~2002-06-19  9:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-18 13:59 Linux and the Sony Playstation 2 Kevin D. Kissell
2002-06-18 13:59 ` Kevin D. Kissell
2002-06-18 15:19 ` H . J . Lu
2002-06-18 18:31 ` David Christensen
2002-06-18 18:31   ` David Christensen
2002-06-19  9:15   ` Carsten Langgaard [this message]
2002-06-19 18:18     ` David Christensen
2002-06-19 18:18       ` David Christensen
     [not found]       ` <E17LA2R-0001PQ-0X@anchor-post-33.mail.demon.net>
2002-06-20 23:59         ` David Christensen
2002-06-20 23:59           ` David Christensen
     [not found] <A9CCF75C3F008040A1B6AFC351DC9AD943EA55@pony-express.bts.co.uk>
2002-06-19 19:06 ` David Christensen
2002-06-19 19:06   ` David Christensen
  -- strict thread matches above, loose matches on Subject: below --
2002-06-19 20:10 Smith, Todd
2002-06-20 12:29 ` Maciej W. Rozycki
2002-06-20 17:27 ` Karsten Merker

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=3D104BA4.BEEAAB6C@mips.com \
    --to=carstenl@mips.com \
    --cc=dpchrist@holgerdanske.com \
    --cc=kevink@mips.com \
    --cc=license-discuss@opensource.org \
    --cc=linux-mips@oss.sgi.com \
    /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