Two good news today. This is the first:

-------- Original Message --------
Subject: Fwd: RE: gpasm - MPASM include files license
Date: Thu, 29 Jul 2010 10:29:48 -0700
From: John O Battle <jobattle@caltech.edu>
To: borut.razem@siol.net


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Borut

I forwarded your EMAIL to a friend at Microchip and his reply is below.
 Please keep me posted on your progress.

John Battle

- -------- Original Message --------
Subject: RE: gpasm - MPASM include files license
Date: Thu, 29 Jul 2010 09:12:52 -0700
From: <Joe.Drzewiecki@microchip.com>
To: <jobattle@caltech.edu>,	<Donna.Mason@microchip.com>,
<Vincent.Sheard@Microchip.com>

John,

We're going one better.
We're setting up a web site where the entire device database is
presented in XML (among other things).

We can post the header and include files as well at the time of release
of every compiler or MPASM. It will take a little doing, but hell, you
can't use them with any other device - why should we care about letting
GPASM and SDCC use them?

The only thing is going to be a question of synchronization. The release
schedule is pretty haphazard right now. The SDCC and GPASM guys are
going to have to keep an eagle eye out and when we update them on the
open-source web site, they'll have to snarf them. Is that fair enough?

Joe
P.S., BTW, I am the guy Borut wants to talk to. Feel free to give him my
name and email address. We'd like to forge (:) a closer alliance with
those guys.
- -----Original Message-----
From: John O Battle [mailto:jobattle@caltech.edu]
Sent: Thursday, July 29, 2010 8:14 AM
To: Donna Mason - C08830; Joe Drzewiecki - C11694; Vincent Sheard -
C10252
Subject: Fwd: gpasm - MPASM include files license

Donna

Any way we (Microchip) can help/cooperate with this effort?  I think
working with these guys would be good PR for microchip and would make
some friends in the process.

John

- -------- Original Message --------
Subject: gpasm - MPASM include files license
Date: Wed, 28 Jul 2010 21:33:56 +0200
From: Borut Razem <borut.razem@siol.net>
Reply-To: <gnupic@linuxhacker.org>
To: gnupic <gnupic@linuxhacker.org>
CC: Sdcc-Devel <sdcc-devel@lists.sourceforge.net>

Hi,

I wold like to know what is the status of using / distributing Microchip
MPASM include files with gpasm:
- - is there any "official" statement from Microchip that the include
files can be used with gpasm?
- - has anybody contact the Microchip to clarify this issue?
- - does anybody know a contact person or address at Microchip where I
can
send an e-mail to get answers about the matter?

I'm asking this because there is no copyright notice (Microchip is
mentioned, but not explicitly as a copyright holder) nor any licensing
terms in include files.

Sdcc project is using MPASM include files to produce device specific
headers and c source files which are part of sdcc run-time libraries.
One of goals for the upcoming sdcc 3.0 release is to release the sdcc
library under the GPL+LE (see
http://sourceforge.net/apps/trac/sdcc/wiki/Library%20License%20Selection
),
so that it can be used with closed source (proprietary) software. Part
of this task is also clarification of licensing status of MPASM include
files.

Best regards,
Borut

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJMUbqMAAoJELejoBGAt4nRlg8H/01ADtOx69SL0pT3Hl2M70Zr
NtaT8IUU6zNZrGCLXcpeUj/MoklhBaGGI+qx2PJPfnno6cajeJTd0dw+oWuXKpQX
oNssyzbtu8kYews1PsgWZU6hssr3Dc/niBN/OOlN0+xoPTiJ95uxhOMSZViBYUVS
aP5GHL8TpoPAa/1cJneL6kjcG8yOMi0xvhwgLxanzaL9VRxtXeacuhsTQKlEIpaD
vRRq/BFqcOJptrvAtdzJm0RejIz18sPjak4Vsm2JIHHF6YAbZ4Cjg8Dhv77/1bjp
C7PZ3gKzHlsGaoZPsI1YvGtE/3gkQ8yxvxrYxErTOO0ZxiaILncpzE/DxOoFzFQ=
=AD/U
-----END PGP SIGNATURE-----