LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: "x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Dealing with custom hardware on x86
Date: Wed, 24 Nov 2021 11:47:23 +0100	[thread overview]
Message-ID: <20211124104723.GA8909@duo.ucw.cz> (raw)
In-Reply-To: <4ad5a438-ddc4-ca0a-a792-09d17edeb66b@alliedtelesis.co.nz>

[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]

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.

In x86 land, we usually use PCI/PCIE and have a add-on board expose
unique IDs with driver knowing what the IDs are. ACPI should not be
involved for add-on boards.

Best regards,
								Pavel
-- 
http://www.livejournal.com/~pavelmachek

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2021-11-24 10:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10  3:02 Chris Packham
2021-11-24 10:47 ` Pavel Machek [this message]
2021-11-24 20:22   ` Chris Packham
2021-12-08 21:40     ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211124104723.GA8909@duo.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@kernel.org \
    --subject='Re: Dealing with custom hardware on x86' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).