public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Bart Veer <bartv@ecoscentric.com>
To: gary@mlbassoc.com
Cc: ecos-maintainers@sources.redhat.com
Subject: Re: Another copyright issue
Date: Wed, 26 Feb 2003 16:05:00 -0000	[thread overview]
Message-ID: <20030226160243.95BD4EC6F1@delenn.bartv.net> (raw)
In-Reply-To: <1046272511.31018.6102.camel@hermes.chez-thomas.org> (message from Gary Thomas on 26 Feb 2003 08:15:11 -0700)

>>>>> "Gary" == Gary Thomas <gary@mlbassoc.com> writes:

    Gary> As part of one of the ports I've recently done, I had to
    Gary> add a couple of files which require special consideration.
    Gary> They are binary data, and only applicable to a particular
    Gary> device (nonetheless required to build RedBoot on the device
    Gary> since it needs them to initialize the hardware).

    Gary> The producer of the files (the hardware manufacturer) has
    Gary> allowed their use, but they want their copyright on them.
    Gary> I have amended this to look like this:

    Gary> //
    Gary> // Copyright (c) 2003 Intrinsyc Europe Ltd. All rights reserved.
    Gary> //
    Gary> // Redistribution and use in source or binary format is allowed
    Gary> // provided:
    Gary> //   * This notice must be preserved
    Gary> //   * The binary data which this file represents may only be 
    Gary> //     used on a NMI uPCI + uE250 based hardware platform.
    Gary> //

    Gary> which I believe preserves their use in the spirit of open source.

    Gary> Does anyone have a problem with this?

I think we do have to be careful about this sort of thing. We don't
want to get into a situation where people contribute HAL packages
which are just prebuilt binaries, encoded in a big C array or
similar. That sort of thing makes it impossible to customize the HAL
for specific application requirements. The GPL uses the phrase
"the preferred form of the work for making modifications to it", and I
think that is a good standard to work to.

Now, there are certainly cases where you need to feed magic numbers to
hardware or it won't work. I don't have a problem with that, within
reason. In this case uE250_pci_bitstream.h is 389K and
uE250_plx_bitstream.h is 130K. That seems like an awful lot of magic,
more than the rest of the platform HAL. I would certainly like to
understand why the platform needs such a large amount of magic.

Bart

  parent reply	other threads:[~2003-02-26 16:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26 15:15 Gary Thomas
2003-02-26 15:21 ` Jonathan Larmour
2003-02-26 15:24   ` Gary Thomas
2003-02-26 16:05 ` Bart Veer [this message]
2003-02-26 16:11   ` Gary Thomas
2003-02-26 16:44     ` Bart Veer
2003-02-26 16:56       ` Jonathan Larmour

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=20030226160243.95BD4EC6F1@delenn.bartv.net \
    --to=bartv@ecoscentric.com \
    --cc=ecos-maintainers@sources.redhat.com \
    --cc=gary@mlbassoc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).