Hardware Manifest for Keyboards

Registered by Zygmunt Krynicki on 2014-06-16

Our ways of detecting non-standard keys (speaker mute, microphone mute, media control, power & sleep, eject and several others is imperfect. We only test those keys on laptops and we don't really know which are applicable to a given device. I think that in the case of testing about-to-be-certified hardware we can reasonably require cert engineer to compile a manifest that lists which keys are present on the keyboard and let all tests access this information perfectly, without any guesswork.

This blueprint should design required changes to our system. One open question is where would we store the list of available keys for a given system and how we would discover which system we're workin on to retrieve that manifest. I think this ties nicely with secure ID but perhaps other ideas can be explored.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Zygmunt Krynicki
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Sylvain Pineau on 2018-06-05

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.