Comments for "https://os.phil-opp.com/hardware-interrupts/"

[utterances-bot]

This is a general purpose comment thread for the “Hardware Interrupts” post.

[ZerothLaw]

Hi, I'd be interested in writing the small scancode_set1 crate! You can reach me at trinioler at gmail.com if you want to continue the discussion out of band. :)

[phil-opp]

@ZerothLaw Awesome, I'll write you an email!

I’m following your tutorials, and (am currently) creating an API for device drivers. Thanks for the amazing work!

[phil-opp]

@rybot666 You're welcome! What are your plans for the API design?

[donald-pinckney]

I'm curious if you have any plans for how to do APIC, as it doesn't look like there is a crate for it.

@phil-opp I’m planning on using traits to implement it (I’ve got a Driver trait that holds info, and an InterruptHandler trait that allows drivers to register interrupt handlers). You can have a look, but the source code is a bit of a mess. The API for drivers is in master, because I forgot to make a PR. ;)

EDIT: Forgot the link

[thejpster]

I wrote a crate called pc-keyboard which handles raw access to a UK 105 key PS/2 keyboard generating scan code set 2. Happy for patches to make it work with set 1 and other keyboard layouts.

[phil-opp]

@thejpster Awesome! cc @ZerothLaw

[phil-opp]

@rybot666 Ah, so that devices can register and unregister for certain interrupts at runtime?

[phil-opp]

@donald-pinckney Nothing specific yet, just some vague ideas.

@phil-opp Exactly. Currently (as in right now) trying to get rid of errors about not being able to send Fn(...) types across threads

[phil-opp]

@rybot666 I think you need to add the Send bound to your register function to allow only function types that can be safely sent across threads.

@phil-opp Yea, I have and it seems to have fixed that. Although my current device isn't very good (an iPad and the Github editor).