cpresser

I looked at DMR0004A (http://www.ti.com/lit/ml/mpss084/mpss084.pdf) to understand the problem. Disclaimer: **I have not yet looked at this problem in Detail.** My first idea how to solve this would be to...

> Hi @cpresser , did you have a look at the first PR for this (#371). Initially I had the following properties: > I was not aware of that. Thanks...

I am currently working on https://github.com/pointhi/kicad-footprint-generator/pull/438, thus this will need re-basing soon. The good news is, since I am already working on that generator I can also review and merge...

I gave it a quick look and tbh, I don't like it. It seems way to complicated. I would rather keep pincount a string and use some `sed` magic to...

One PR (https://github.com/pointhi/kicad-footprint-generator/pull/645) I know of is related on this. But I could merge the footprints without this fix - the author did change the format strings. Once this is...

@evanshultz while looking at #438 I also found this PR. The history of this one looks broken. I think its best to fix this branch after #438 is merged.

I suggest to do the whole SC-70-xx series (The generator now supports missing pins). All but the 4-pin variants are in the JEDEC document. The 4-pin-variant is used for `APE8865U4-12-HF-3`....

In F5.4 the wording currently also is 'should'. I think we should change that as well? Do you agree, if yes I will open another PR for the F5.4-rule.

The common denominator for this rule seems to be a left-to-right flow in the schematic. Similar to writing text in most languages. I dislike the UART/RS232-example since there is no...

While we are at it we could also add voltage-regulators where we currently allow KLC violations. Thats a point that always bugs me. I find the idea appealing to have...