Re: [ECOS] Re: HOWTO: eCos on QEMU PC emulator

[ricky wu <rickleaf dot wu at gmail dot com>]

Dear all:
I think that eCos is an easy to use RTOS, but most of students and
developer have
not idea to how to start their work.
We create this project only hope them do it from a virtual system like
QEMU or synthetic target.
And the drivers and application will base on this target.
We will fix some issues continually, if we have own a repository that
work will be more difficult.
If the eCos interest it too, we will sent the patch to eCos Team
following standard procedure.
We show some picture to let more people join us

2011/3/28 ricky wu <rickleaf.wu@gmail.com>
>
> I think that eCos is an easy to use RTOS, but most of students and developer have
> not idea to how to start their work.
> We create this project only hope them do it from a virtual system like QEMU or synthetic target.
> And the drivers and application will base on this target.
> We will fix some issues continually, if we have own a repository that work will be more difficult.
> If the eCos interest it too, we will sent the patch to eCos Team following standard procedure.
> We show some picture to let more people join us
> 2011/3/28 Grant Edwards <grant.b.edwards@gmail.com>
>>
>> On 2011-03-28, Alex Schuilenburg <alexs@ecoscentric.com> wrote:
>> > On 2011-03-25 15:26, John Dallaway wrote:
>> >> Drasko
>> >>
>> >> Drasko DRASKOVIC wrote:
>> >>
>> >>>>> Second, if you re-distribute it, can not you do it the way you like -
>> >>>>> for example putting it in git repository.
>> >>>> Yes, you certainly can.
>> >>> So why then the authors must assign copyright to the FSF and
>> >>> contribute it in the order for us to put eCos sources in git tree ?
>> >> You can put eCos-licensed sources in your _own_ repository and
>> >> redistribute them without issue. However, it is eCos project policy that
>> >> copyright in all contributions to the official eCos project repository
>> >> must be assigned to the FSF. [ There are a few exceptions. ]
>> >
>> > The only benefit I can think of wanting to publish your own repository
>> > would be for the rapid-turnaround in shared development of your port.
>> >
>> > While you can redistribute freely, there are a few good reasons why you
>> > should consider contributing after the work is completed rather than
>> > continuing to publish the code in your own repository.
>>
>> In this case, he can't consider contributing after the work is
>> completed. ?He didn't write the port in question. ?AFAICT he was
>> asking about creating a repository which which contained code which
>> somebody else developed and for which a copyright assignment to the
>> FSF hadn't been executed -- but for which the license terms allows him
>> to redistribute the source code.
>>
>> In any case it's pretty much a moot point, since the author of the
>> port has expressed a desire to contribute it.
>>
>> --
>> Grant Edwards ? ? ? ? ? ? ? grant.b.edwards ? ? ? ?Yow! I'm young ... I'm
>> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?at ? ? ? ? ? ? ? HEALTHY ... I can HIKE
>> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?gmail.com ? ? ? ? ? ?THRU CAPT GROGAN'S LUMBAR
>> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? REGIONS!
>>
>>
>> --
>> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
>> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>>
>
>
>
> --
> Ricky Wu



--
Ricky Wu

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