linux-kernel - Dealing with custom hardware on x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <4ad5a438-ddc4-ca0a-a792-09d17edeb66b@alliedtelesis.co.nz>
Date:   Wed, 10 Nov 2021 03:02:11 +0000
From:   Chris Packham <Chris.Packham@...iedtelesis.co.nz>
To:     "x86@...nel.org" <x86@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Dealing with custom hardware on x86

Hi,

I'm about to start a project involving custom hardware using an x86 CPU. 
Complicating things somewhat we will have a CPU board supplied by a 3rd 
party vendor using a COM Express type 7 connector which will plug in to 
the board we're designing (actually 2 different boards each with some 
modular aspects) .

Coming from an embedded (mostly ARM) background I'm used to describing 
the hardware via a devicetree and dealing with plug-in modules by 
loading devicetree overlays. How do people achieve this kind of thing on 
x86?

I gather ACPI is involved somewhere but the knowledge that the BIOS has 
will go as far as the COM Express header and somehow we'll have to tell 
the kernel about the various non-probeable (mostly i2c) devices on our 
board which is kind of where I'm stuck. Any pointers would be greatly 
appreciated.

Thanks,
Chris