From: Gary Thomas <gary@mlbassoc.com>
To: Bart Veer <bartv@ecoscentric.com>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: Another copyright issue
Date: Wed, 26 Feb 2003 16:11:00 -0000 [thread overview]
Message-ID: <1046275913.31018.6295.camel@hermes.chez-thomas.org> (raw)
In-Reply-To: <20030226160243.95BD4EC6F1@delenn.bartv.net>
On Wed, 2003-02-26 at 09:02, Bart Veer wrote:
> >>>>> "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.
>
This system uses FPGA devices for a number of peripherals (the
PCI bus in particular). The only way to use those devices is
to program them - at boot time - with this data. The only place
to hold this data on the platform is in the FLASH. So, the choice
would be to have some very-hard-to-initialize-and-maintain way
to get it into part of the FLASH, or make it be part of RedBoot,
which is what I chose.
n.b. this sort of thing will become more and more popular in
the future. FPGA and soft-core systems are beginning to be
very common.
--
------------------------------------------------------------
Gary Thomas |
MLB Associates | Consulting for the
+1 (970) 229-1963 | Embedded world
http://www.mlbassoc.com/ |
email: <gary@mlbassoc.com> |
gpg: http://www.chez-thomas.org/gary/gpg_key.asc
------------------------------------------------------------
next prev parent reply other threads:[~2003-02-26 16:11 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
2003-02-26 16:11 ` Gary Thomas [this message]
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=1046275913.31018.6295.camel@hermes.chez-thomas.org \
--to=gary@mlbassoc.com \
--cc=bartv@ecoscentric.com \
--cc=ecos-maintainers@sources.redhat.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).