Re: [Sdcc-user] New FX2 header file and a licensing question

[Frieder F. <fri...@we...>]

Hi Christer,

Christer Weinigel schrieb:
> I'm hereby releasing this file under a X11/MIT license and hope that
> you'll find it useful.  Maybe you might even wanto to add it the main
> SDCC distribution.  Also, please tell me if I have made any mistakes
> while writing this file, it's pretty easy to mess up when rewrinting
> stuff by hand.  I have compared this file to a bunch of fx2regs.h
> files from the net, but I still may have missed something.

sorry for the late answer. The file looks fine although it does not yet
use the "more standard C-conforming" notation which would look like:

__sfr __at (0x80) IOA;                /* I/O Port A (bit-adressable) */

See f.e. the header file XC866.h.



The very latest of header file technology is used
within the recently added file cc2510fx.h.

The method (of using a compatibility file #include compiler.h)
used there would allow to use the *same* header
file for different compilers!

As of now: SDCC, Keil, Raisonance, IAR, Hi-Tech,
Tasking, Crossware, Wickenh=E4user.

(Related discussion at:
http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1481734&grou=
p_id=3D599&atid=3D350599 )



I'd be happy to add your header file in a __sfr __at (0x80) IOA;
or the more modern "#include compiler.h" style.
Also I like the X11/MIT license for header files and to my boguous
memories this license was kind of considered compatible with LGPL/GPL.
There were some licensing discussions for the header and library
files lately but the discussions are somewhat hindered by the
fact that some of the developers are not lawyers.
(Hugh, and we didn't even consider dual licenses yet:)

Anyway, in order not to interfere, I'd want to wait one month
from now before adding your X11/MIT file.

Greetings,
Frieder


>         Copyright (c) 2006 Christer Weinigel, Nordnav Technologies AB
>=20
>         Permission is hereby granted, free of charge, to any person
>         obtaining a copy of this software and associated documentation
>         files (the "Software"), to deal in the Software without
>         restriction, including without limitation the rights to use,
>         copy, modify, merge, publish, distribute, sublicense, and/or
>         sell copies of the Software, and to permit persons to whom the
>         Software is furnished to do so, subject to the following
>         conditions:
>=20
>         The above copyright notice and this permission notice shall be
>         included in all copies or substantial portions of the
>         Software.
>=20
>         THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
>         KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
>         WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
>         PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
>         COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
>         LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
>         OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
>         SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.