On 22/9/2022 11:44 pm, Joel Sherrill wrote:
>
>
> On Thu, Sep 22, 2022 at 4:44 AM Karel Gardas wrote:
>
> On 9/22/22 10:41, Sebastian Huber wrote:
> > On 22/09/2022 10:30, Karel Gardas wrote:
> >> On 9/22/22 00:00, Gedare Bloom wrote:
> >>> On Wed, Sep 21, 2022 at 9:12 AM Joel S
On Thu, Sep 22, 2022 at 4:44 AM Karel Gardas
wrote:
> On 9/22/22 10:41, Sebastian Huber wrote:
> > On 22/09/2022 10:30, Karel Gardas wrote:
> >> On 9/22/22 00:00, Gedare Bloom wrote:
> >>> On Wed, Sep 21, 2022 at 9:12 AM Joel Sherrill wrote:
>
>
>
> On Wed, Sep 21, 2022 at 8:
On 9/22/22 10:41, Sebastian Huber wrote:
On 22/09/2022 10:30, Karel Gardas wrote:
On 9/22/22 00:00, Gedare Bloom wrote:
On Wed, Sep 21, 2022 at 9:12 AM Joel Sherrill wrote:
On Wed, Sep 21, 2022 at 8:48 AM Karel Gardas
wrote:
The problem is that we still need to discuss licensing here.
On 22/09/2022 10:30, Karel Gardas wrote:
On 9/22/22 00:00, Gedare Bloom wrote:
On Wed, Sep 21, 2022 at 9:12 AM Joel Sherrill wrote:
On Wed, Sep 21, 2022 at 8:48 AM Karel Gardas
wrote:
The problem is that we still need to discuss licensing here. Randomly
checked files from the HAL patch
On 9/22/22 00:00, Gedare Bloom wrote:
On Wed, Sep 21, 2022 at 9:12 AM Joel Sherrill wrote:
On Wed, Sep 21, 2022 at 8:48 AM Karel Gardas wrote:
The problem is that we still need to discuss licensing here. Randomly
checked files from the HAL patch contains this as a license:
* This so
On Wed, Sep 21, 2022 at 9:12 AM Joel Sherrill wrote:
>
>
>
> On Wed, Sep 21, 2022 at 8:48 AM Karel Gardas wrote:
>>
>>
>> The problem is that we still need to discuss licensing here. Randomly
>> checked files from the HAL patch contains this as a license:
>>
>>* This software is licensed unde
On Wed, Sep 21, 2022 at 8:48 AM Karel Gardas
wrote:
>
> The problem is that we still need to discuss licensing here. Randomly
> checked files from the HAL patch contains this as a license:
>
>* This software is licensed under terms that can be found in the
> LICENSE file
>* in the root di
On 9/21/22 15:48, Karel Gardas wrote:
On the bright side, it looks like STM still holds on BSD-3 for their HAL
code for F4?
https://github.com/STMicroelectronics/STM32CubeF4/blob/master/LICENSE.md
Would be great indeed.
After very quick investigation, everything under CMSIS is under Apache
The problem is that we still need to discuss licensing here. Randomly
checked files from the HAL patch contains this as a license:
* This software is licensed under terms that can be found in the
LICENSE file
* in the root directory of this software component.
* If no LICENSE file come
This patch set has been sitting for almost 7 weeks. I was going to commit
it today but was asked to give one last the patch merge equivalent of
""if anyone can show just cause why this patch and RTEMS cannot be
joined together, let them speak now or forever hold their peace"
Or at least be nice
Dear all,
These patches are to address the issues in my previous versions. These
include GPIO API, ADC API and STM32F4 BSP implementation for them.
My repository is at: https://github.com/dtbpkmte/GSoC-2022-RTEMS (master
branch).
The sample application code for these APIs can be found at:
https:
11 matches
Mail list logo
