Iris Artin

> On Sun, Dec 29, 2024 at 05:08:53PM -0800, Iris Artin wrote: > > > @innermatrix pushed 1 commit. > > [928daa8](https://github.com/Rahix/avr-hal/commit/928daa8aa8a3028599c40d5503a991b46fa1f3b7) Fixed attiny doctests > > Hey, #617 has...

tldr: Thank you and @Rahix for all your great work; I think my contributions would be valuable to the community, so I would love to align with you and @Rahix...

Didn't think of that! Tyvm.

For context, I came into `avr-hal` as a software engineer (with 20+ years of non-embedded industry experience) and an embedded hobbyist (with 10+ years experience including designing my own boards...

@Patryk27 Oooh, good to know! Poking around it, I see that `avr-tester` uses `simavr`, which doesn't implement some of the cores that are already present in `avr-hal` (for example, tiny88),...

@Patryk27 Those look like declarations derived from upstream AVR sources; wouldn't there need to be something related to tiny88 in https://github.com/buserror/simavr/tree/ae75edec3f4068f3d1a6c30130abef7ef8e83155/simavr/cores ? (Could be I just don't quite understand how...

I would love some direction re how to move my PRs along. I realize that I am proposing a big change, and I would be very happy to restructure my...

@Phil-hacker I do think that if the one-file-per-mcu goes through it would make sense to look at the stuff that is common between `attiny-hal` and `atmega-hal` and see if some...

@stappersg @Rahix I retooled my previous PRs (in which conflated scaling out issues with some unrelated peeves of mine) and focused them narrowly on refactoring the MCU crates to use...

@AlternativleyCoolSlimbo It doesn't need to be a package named `cargo-avr`. It only needs to be a binary named `cargo-avr` (in a package named `avr-hal`, or any other package). So I...