Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] pci_ids.h missing
Date: Mon, 16 Jan 2012 18:34:05 +0100	[thread overview]
Message-ID: <201201161834.06077.arnout@mind.be> (raw)
In-Reply-To: <CAOrAeomeuJhMTOicaqz22Y+xULo1hZBs92xASrWsSYCG8gvVdw@mail.gmail.com>

On Monday 16 January 2012 17:38:01 vbr vbr wrote:
> Just downloaded and extracted a vanilla 2.6.39.4 kernel from kernel.org,
> and this version does ship pci_ids.h. There must be something else going on:
> 
> x linux-2.6.39.4/include/linux/pch_dma.h
> x linux-2.6.39.4/include/linux/pci-acpi.h
> x linux-2.6.39.4/include/linux/pci-aspm.h
> x linux-2.6.39.4/include/linux/pci-dma.h
> x linux-2.6.39.4/include/linux/pci.h
> x linux-2.6.39.4/include/linux/pci_hotplug.h
> x linux-2.6.39.4/include/linux/pci_ids.h   <<<<<<<<<<<<<
> x linux-2.6.39.4/include/linux/pci_regs.h
> x linux-2.6.39.4/include/linux/pcieport_if.h
> 
> Thanks
> Vincent
> 
> 
> On Sun, Jan 15, 2012 at 9:50 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> 
> > On Sunday 15 January 2012 14:24:41 vbr vbr wrote:
> > > pci_ids.h is missing from the include/linux directory in the staging
> > area:
> > >
> > > # ls output/staging/usr/include/linux/pci*.h
> > > output/staging/usr/include/linux/pci.h
> > > output/staging/usr/include/linux/pci_regs.h
> > >
> > > Am I missing something in the buildroot configuration?
> >
> > upstream linux kernel doesn't ship it, thus buildroot does not
                                  ^^^^
 This should be: upstream linux kernel doesn't *install* it.

 pci_ids.h is not considered ABI and should not be accessed by userspace.
External modules should always be compiled from the Linux source tree 
itself so they don't need pci_ids.h in staging.

 pciutils, for instance, includes its own list of ids.


 Regards,
 Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      parent reply	other threads:[~2012-01-16 17:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-15 19:24 [Buildroot] pci_ids.h missing vbr vbr
2012-01-16  5:50 ` Mike Frysinger
2012-01-16 16:38   ` vbr vbr
2012-01-16 17:32     ` vbr vbr
2012-01-16 17:34     ` Arnout Vandecappelle [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=201201161834.06077.arnout@mind.be \
    --to=arnout@mind.be \
    --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