From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libpciaccess: add dependency on hwdata
Date: Thu, 29 Mar 2018 13:41:59 -0300 (BRT) [thread overview]
Message-ID: <1751033060.982024.1522341719017.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <87zi2r7zaa.fsf@dell.be.48ers.dk>
> From: "Peter Korsgaard" <peter@korsgaard.com>
> To: "Carlos Santos" <casantos@datacom.ind.br>
> Cc: "buildroot" <buildroot@buildroot.org>, "Bernd Kuhls" <bernd.kuhls@t-online.de>
> Sent: Thursday, March 29, 2018 11:05:17 AM
> Subject: Re: [PATCH] libpciaccess: add dependency on hwdata
>>>>>> "Carlos" == Carlos Santos <casantos@datacom.ind.br> writes:
>
> > libpciaccess requires /usr/share/hwdata/pci.ids (or pci.ids.gz, if
> > compiled with zlib support). That file is provided by the hwdata
> > package, so add it as a run-time dependency.
>
> > Signed-off-by: Carlos Santos <casantos@datacom.ind.br>
>
> Is this really a hard dependency? Looking at src/common_device_name.c,
> this seems to only be used in populate_vendor(), which just returns
> without error if the file cannot be opened.
>
> --
> Bye, Peter Korsgaard
It is required by libvirt[1] to show device names when we use virtual
machine manager to add hardware via PCI passthrough, otherwise only
the PCI bus information (slot, port, function) is shown.
1. https://patchwork.ozlabs.org/patch/841613/
--
Carlos Santos (Casantos) - DATACOM, P&D
?The greatest triumph that modern PR can offer is the transcendent
success of having your words and actions judged by your reputation,
rather than the other way about.? ? Christopher Hitchens
next prev parent reply other threads:[~2018-03-29 16:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-28 23:52 [Buildroot] [PATCH] libpciaccess: add dependency on hwdata Carlos Santos
2018-03-29 14:05 ` Peter Korsgaard
2018-03-29 16:41 ` Carlos Santos [this message]
2018-03-29 17:52 ` Yann E. MORIN
2018-03-29 19:05 ` Peter Korsgaard
2018-04-03 1:38 ` Carlos Santos
2018-04-28 21:39 ` Thomas Petazzoni
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=1751033060.982024.1522341719017.JavaMail.zimbra@datacom.ind.br \
--to=casantos@datacom.ind.br \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.