CMSIS-Driver implementations as open source repositories

Such ST Pack sources are not to find on GitHub, Henry. 

I am not aware of any public device repo with CMSIS drivers.

Such ST Pack sources are not to find on GitHub, Henry. 

I am not aware of any public device repo with CMSIS drivers.

Thanks for your feedback. For sure, I also didn't find any source of these implementations on GitHub.

The reason I'm asking the question here is that I believe somewhere in ARM Community might provide source code/repo of "device packs".

We have observed some issues in the current CMSIS-Driver implementations, and it would be great to access these open source repos where we can report issue, discuss solution, and even contribute with our enhancements (as normal open source projects).

FYI : I have seen the information in the header of device pack source code, like in the I2C_STM32F7xx.h:

/* -----------------------------------------------------------------------------

 * Copyright (c) 2013-2020 Arm Limited (or its affiliates). All 
 * rights reserved.
 * SPDX-License-Identifier: Apache-2.0
 * Licensed under the Apache License, Version 2.0 (the License); you may
 * not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 * www.apache.org/licenses/LICENSE-2.0

 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an AS IS BASIS, WITHOUT
 * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.

 * $Date:        16. December 2020
 * $Revision:    V1.7
 * Project:      I2C Driver definitions for ST STM32F7xx
 * -------------------------------------------------------------------------- */

I too, think the ARM Community would benefit from the Open Source Community. There's some stalled packs I would like to see updated, and don't mind doing it myself, except I can't find any repo to do so.

It's hard to understand why ARM would overlook such work horse, while wanting the biggest adoption. If ARM wants to control the merge or PRs, I don't mind one bit.

Nowadays opening to contributors seems like the way to go.

If anyone has contact names that could influence the decisions around this, I'd like to know them

Cheers

Thanks for this discussion and its ideas, which I have shared with the Arm Keil management.

In this specific case, I recommend also contacting ST(or any other SIP) to provide CMSIS-Driver support.