Add ferris 0.2

[pierrechevalier83]

Description

The Ferris 0.2 switches from an atmega32u4 chip to an stm32f072 chip.

Write firmware for this. The most challenging bit was to configure i2c
as the hardware uses the i2c2 pins: PB10 and PB11 which is uncommon.

The ferris bling has backlighting leds which are not supported yet.
Support will come in a later PR.

Note that part of this change refactors the 0.1's matrix.c implementation for
consistency as only higher level functions are available to call with chibios
and I prefer to have code that is closer to each other between revisions.

Types of Changes

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

Issues Fixed or Closed by This PR

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).

[pierrechevalier83]

Is there anything holding this PR from getting merged? It looks like it was approved 13 days ago. When it's in, I'll want to raise a follow-up PR for the underglow :)

[drashna]

Is there anything holding this PR from getting merged? It looks like it was approved 13 days ago. When it's in, I'll want to raise a follow-up PR for the underglow :)

Just time. We review PRs in our spare time, so it can take some time.

[pierrechevalier83]

Is there anything holding this PR from getting merged? It looks like it was approved 13 days ago. When it's in, I'll want to raise a follow-up PR for the underglow :)

Just time. We review PRs in our spare time, so it can take some time.

Hi @drashna , thanks for the reply. I'm sorry if I sounded impatient. I totally appreciate the time you all are spending on maintaining this huge project for the benefit of the hobbyist keyboard community. I also appreciate that so far I've been getting great quality code reviews in all of my PRs and people have been really helpful on discord when I had questions ❤️

I guess my question was more about the process than just the timeline: do PRs need two approving reviews before landing? I haven't found a clear indication here: https://docs.qmk.fm/#/contributing, so it's a bit hard to know what to expect. Maybe I haven't been looking at the right place in the documentation to find this kind of information?

[pierrechevalier83]

Thanks for the review, @fauxpark. I've committed all of your suggestions 👍 I learnt something about controlling the size of an imgur image preview today 😄

[drashna]

Is there anything holding this PR from getting merged? It looks like it was approved 13 days ago. When it's in, I'll want to raise a follow-up PR for the underglow :)

Just time. We review PRs in our spare time, so it can take some time.

Hi @drashna , thanks for the reply. I'm sorry if I sounded impatient. I totally appreciate the time you all are spending on maintaining this huge project for the benefit of the hobbyist keyboard community. I also appreciate that so far I've been getting great quality code reviews in all of my PRs and people have been really helpful on discord when I had questions ❤️

I guess my question was more about the process than just the timeline: do PRs need two approving reviews before landing? I haven't found a clear indication here: docs.qmk.fm/#/contributing, so it's a bit hard to know what to expect. Maybe I haven't been looking at the right place in the documentation to find this kind of information?

No worries. And yeah, we generally want 2 approvals before a PR is merged in.

And I've been meaning to add that info to the docs.