From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to check if a platform supports PCI bus
Date: Thu, 17 Mar 2016 21:32:35 +0100 [thread overview]
Message-ID: <20160317213235.77cd98e9@free-electrons.com> (raw)
In-Reply-To: <900813099.3374314.1458219344699.JavaMail.zimbra@datacom.ind.br>
Hello,
On Thu, 17 Mar 2016 09:55:44 -0300 (BRT), DATACOM - Tiago.Brusamarello
wrote:
> I'm about to submit a new package to the upstream. This package is intended to be used for testing the Linux PCIe driver. On the "Config.in" file I'm using the same check made by the "pciutils" package:
>
> # PCI not supported on Blackfin
> depends on !BR2_bfin
>
> Is this correct to check if a platform supports PCI bus on Buildroot?
No. We don't really try to make sure that the platform has the relevant
HW for a certain package. You can build i2c-tools even if you don't
have an I2C bus. You can build X.org even if you don't have a screen,
etc.
So just don't try to do anything special about the PCI dependency. You
can try to build your package on Blackfin to see if it builds or not.
If it doesn't, then exclude Blackfin, and that's it. It should build
fine on other architectures.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-03-17 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 12:55 [Buildroot] How to check if a platform supports PCI bus DATACOM - Tiago.Brusamarello
2016-03-17 20:32 ` Thomas Petazzoni [this message]
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=20160317213235.77cd98e9@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox