This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RedBoot licensing question


According to the RedBoot web page, it's under the "Red Hat eCos Public
License", that requires sources for "covered code" to be distributed along
with binaries.

My question: 

I create a C source file (mycommand.c) with some code in it that impliments
some command functionality, and use the RedBoot_cmd() macro to add it to the
RedBoot command table at link time as "mycommand".   Maybe I put this file
in as part of my HAL, or maybe it's a completely separate package.

Is mycommand.c "covered code" that has to be distributed in source?  Somebody 
I know wants to use RedBoot for a project, but his management thinks they
can't becuase they want to:

 1) include some "proprietary" functionality for which they don't want to
    distribute sources.
    
 2) want to restrict redistribution of the resulting bootloader binary.

AFAICT, this is the same as linking proprietary application code with eCos
and limiting distribution of the resulting binary and refusing to distribute
source for the proprietary application routines.  

That's allowed, right?

-- 
Grant Edwards
grante@visi.com

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]