FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [September 2015 Threads] Upstream process for FreeRTOSPosted by maddihri on September 14, 2015 Hello,
Could you please describe me the upstream process for a new platform?
I made a new directory for a Freescale board with support for two compilers. The binary is generated using a makefile.I was planning to create a patch only with this directory, because I didn't modify anything else. Is this ok?
Thank you,
Madalina Hristache
Upstream process for FreeRTOSPosted by rtel on September 14, 2015 Hi Madalina,
Thanks for your efforts -
For legal reasons, indemnification, etc. we have to keep contributed code separate from the main FreeRTOS .zip file download - but of course all contributions are greatfully received. I would be grateful if you could up load your contribution to the FreeRTOS Interactive site: http://interactive.freertos.org
Regards.
Upstream process for FreeRTOSPosted by maddihri on September 14, 2015 I am an engineer in Freescale and the demo code has Freescale copyright. The project is also approved by our legal team. There are any other legal problems?
Regards.
Upstream process for FreeRTOSPosted by rtel on September 14, 2015 Hi again, in which case can you please contact me using the "business contact" link on the following page: http://www.freertos.org/contact - mark your email for the attention of Richard. Thanks.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|