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

Remove arm_atsam, Massdrop boards. #14081

Closed
wants to merge 1 commit into from
Closed

Conversation

tzarc
Copy link
Member

@tzarc tzarc commented Aug 19, 2021

Description

Removes support for ATSAM-based boards, due to licensing concerns. Follow-on from #10904.

Types of Changes

  • Core
  • Bugfix
  • New feature
  • Enhancement/optimization
  • Keyboard (addition or update)
  • Keymap/layout/userspace (addition or update)
  • Documentation

Checklist

  • My code follows the code style of this project: C, Python
  • I have read the PR Checklist document and have made the appropriate changes.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • I have tested the changes and verified that they work and don't break anything (as well as I can manage).

@qmk qmk locked as too heated and limited conversation to collaborators Aug 19, 2021
@tzarc tzarc changed the title [RFC] Remove arm_atsam, Massdrop boards. Remove arm_atsam, Massdrop boards. Aug 19, 2021
@tzarc
Copy link
Member Author

tzarc commented Aug 19, 2021

Discussion over on #14082.

@tzarc
Copy link
Member Author

tzarc commented Mar 7, 2022

Cancelling this for now given that #15464 is in the pipeline -- the number of conflicts is now considerable and it'll make more sense to do the cleanup after the dust settles with RIOT-OS integration.

@tzarc tzarc closed this Mar 7, 2022
@tzarc tzarc deleted the remove-atsam branch March 7, 2022 20:55
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant