Skip to content

Pr io revamp #266

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

Merged
merged 20 commits into from
Jul 22, 2025
Merged

Pr io revamp #266

merged 20 commits into from
Jul 22, 2025

Conversation

sportron-ledger
Copy link
Contributor

No description provided.

@sportron-ledger sportron-ledger force-pushed the pr-io-revamp branch 4 times, most recently from 76cb5bd to 750c620 Compare June 30, 2025 14:58
#[cfg(not(any(target_os = "stax", target_os = "flex")))]
use ledger_secure_sdk_sys::buttons::{get_button_event, ButtonEvent, ButtonsState};
use ledger_secure_sdk_sys::seph as sys_seph;
use ledger_secure_sdk_sys::*;

use crate::seph;

#[cfg(any(target_os = "nanox", target_os = "stax", target_os = "flex"))]
use crate::seph::ItcUxEvent;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this used to manage BLE connection?

@@ -32,5 +32,5 @@ pub fn screen_update() {
#[cfg(not(feature = "speculos"))]
pub fn seph_setup_ticker(interval_ms: u16) {
let ms = interval_ms.to_be_bytes();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this function still needed ? It is never called by any other SDK modules or external apps

@yogh333 yogh333 force-pushed the pr-io-revamp branch 2 times, most recently from 219273a to f097c39 Compare July 17, 2025 12:54
@yogh333 yogh333 merged commit 6a521b4 into master Jul 22, 2025
33 checks passed
@yogh333 yogh333 deleted the pr-io-revamp branch July 22, 2025 11:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants