-
Notifications
You must be signed in to change notification settings - Fork 839
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
RP235x: Add the new FJOIN_RX_xxx options #3369
base: main
Are you sure you want to change the base?
Conversation
Build error can be fixed by depending on pio-rs from this pr: rp-rs/pio-rs#66 |
4ac9fd0
to
46c6476
Compare
ce61dcd
to
e27918f
Compare
e27918f
to
a13f24b
Compare
should we wait for rp-rs/pio-rs#66 before merge? I see there's still quite a bit of discussion there. |
I think we should wait. It's not clear if the pio-rs pr will need to change more or not. This pr is also out of sync with the current state of that pr. |
Removed the |
I think this kind of got forgotten. Is this PR still relevant? |
afaict it's still waiting on rp-rs/pio-rs#66 |
OK, just wanted to make sure it doesn't go stale...
…On Sun, 29 Dec 2024, 12:14 Dario Nieuwenhuis, ***@***.***> wrote:
afaict it's still waiting on rp-rs/pio-rs#66
<rp-rs/pio-rs#66>
—
Reply to this email directly, view it on GitHub
<#3369 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAVC4LAKNFLBG5URMP4UL2H7RRHAVCNFSM6AAAAABOW7PXTKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUG4YDKNRTGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
This requires changes in
pio
too if we want the example to work (ping @CBJamo). Probably a new release?