You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is one hardware registry, shared by every origin. It is the kernelci-pipeline config/hardware_registry catalog, stored in the hardware_registry_* tables, which have no origin column. A platform id has one vendor, one processor, one architecture, and one board type, and every origin uses that same record.
The hardware listing filters on that single catalog. Origin is not a hardware filter.
Proposed field order. This is a suggestion, not a fixed order:
Architecture (processors.architecture)
Processor (processors.id)
Platform vendor (platforms.vendor_id)
Silicon vendor (processors.vendor_id)
Platform (platforms.id)
System module (platforms.system_module_id)
Form factor (platforms.form_factor)
Board type (platforms.type)
Architecture, processor, and platform vendor are the three the meeting put first. Board type is last. Silicon vendor is separate from platform vendor, because the registry has both. Urls, free-text details, core count, and max clock speed are not filters.
Each field is a searchable multi-select. Selected values show as chips. A platform that is not in the registry still appears, and only matches a platform id filter.
Activity
fix(hardware): match the listing to the hardware page
feat(hardware): filter the hardware page by the registry
feat(filters): tighten the shared filters drawer
fix(hardware): match the listing to the hardware page
fix(hardware): count each origin's builds and clear every tree
chore(hardware): regenerate the API schema
test(hardware): clear every selected tree on qemu-arm64