forked from numist/is31io7326_clone
-
Notifications
You must be signed in to change notification settings - Fork 5
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
why does firmware flashing sketch not use Wire? #19
Comments
At the time, I believe to be primary reason for the cut down implementation was space. Wire includes both master and slave implementations and isn’t able to optimize them out. On the Model 01, we were very very flash constrained. It’s been a while and there may have been some perf implications too, but space was the primary concern.
For non avr devices, no, that implementation won’t work and since we’re not nearly as space constrained, just using Wire is a reasonable path to a first implementation.
… On May 30, 2022, at 6:32 AM, Taylor Yu ***@***.***> wrote:
What the reason was for using (a snapshot of?) the twi.c internals from the Wire library instead of Wire? I'm suspecting some sort of incompatibility, but I'm not finding many clues in the history. Will it work on the GD32-based (?) Model 100 without porting to Wire? The Kaleidoscope hardware support for the Model 100 seems to use Wire to talk to the ATtinys, from what I can tell.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
|
I think the firmware flashing sketch, even on the Model 01, is much less space constrained, so it might be safe to switch that back to using Wire? |
Yep. At one point we were hoping to bundle it into keyboard firmware, but that never happened on the Model 01
… On May 30, 2022, at 12:17 PM, Taylor Yu ***@***.***> wrote:
I think the firmware flashing sketch, even on the Model 01, is much less space constrained, so it might be safe to switch that back to using Wire?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What the reason was for using (a snapshot of?) the
twi.c
internals from the Wire library instead of Wire? I'm suspecting some sort of incompatibility, but I'm not finding many clues in the history. Will it work on the GD32-based (?) Model 100 without porting to Wire? The Kaleidoscope hardware support for the Model 100 seems to use Wire to talk to the ATtinys, from what I can tell.The text was updated successfully, but these errors were encountered: