Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for atsamd51, cpu 120mhz 256kb ram, 1mb flash. See: https://www.microchip.com/en-us/product/ATSAMD51G18A Thanks #1

Open
vslinuxdotnet opened this issue Jan 24, 2023 · 4 comments
Assignees
Labels
enhancement New feature or request

Comments

@vslinuxdotnet
Copy link

No description provided.

@chettrick chettrick added the enhancement New feature or request label Jan 27, 2023
@chettrick
Copy link
Owner

Hello, thanks for your suggestion about adding support for the SAM D51.

From my cursory view, Microchip's software offer for that chip series is licensed as either Apache 2.0 or a BSD-like license with an exclusive-use clause.
Such non-free licensed software, including software licensed under GPL, LGPL, EPL, CDDL, and so on, will not be included in DiscoBSD.

I will leave this Issue open, in the hope that a suitably licensed chip and board support package is discovered or independently developed. I appreciate any suggestions.

Thanks,
Christopher Hettrick

@chettrick chettrick self-assigned this Mar 5, 2023
@amarkee
Copy link
Contributor

amarkee commented Aug 12, 2023

For clarification on the license, is the Apache 2.0 a problem? The device headers and linker scripts appear to be Apache 2.0 while the drivers (Harmony or ASF) are under the exclusive-use clause. Harmony and ASF aren't worth the time, so not being able to use them wouldn't be a big loss. This could be a port I could take on once I familiarize myself with the code base a bit more.

@chettrick
Copy link
Owner

@amarkee Yes, the Apache 2.0 license is a problem. See https://www.openbsd.org/policy.html and the rationale under Specific Cases for Apache.

DiscoBSD adopts, in general, the OpenBSD approach to software licensing.

The big issue that will be faced in the future is that the CMSIS files from Arm for Cortex-M33 devices and newer devices are also Apache 2.0, and no BSD-style license exists for them that I could find.

For clarity, there currently are issues with the licensing of some utilities inherited from RetroBSD, such as the virus editor and lcc. A licensing audit will be performed once the codebase is in a stable form that is receptive for a sort of Ports Collection for transferring the third party utilities to.

@amarkee
Copy link
Contributor

amarkee commented Aug 18, 2023

@chettrick Thank you for the clarification. There are so many different definitions of what constitutes free and non-free software it's good to have clear license guidelines. I will shelve this port for now and keep researching solutions.

chettrick added a commit that referenced this issue Jan 19, 2024
Update the char version[] in vers.c, generated by the shell
script sys/conf/newvers.sh, for the DiscoBSD operating system.

The old char version[] string stated, for stm32, something like:

2.11 BSD UNIX for STM32, rev G469 #1: Thu Jan 18 08:51:11 MST 2024
     chris@stm32.discobsd.org:/sys/stm32/f412gdisco

The new char version[] string states, for all architectures:

DiscoBSD 2.1 (F412GDISCO) #2 473: Fri Jan 19 00:52:08 MST 2024
     chris@stm32.discobsd.org:/sys/stm32/f412gdisco

The top line information values, from left to right, are:
ostype, osrelease, kernel id, compile version, git repo number, date.

The top line is used by motd to be displayed upon each log in.

Other simple cleanups to the file for regularity.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants