From: Greg KH <gregkh@suse.de>
To: "V. ANANDA KRISHNAN" <mansarov@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: serial port driver 8250_pci - pci_device_id structure
Date: Tue, 14 Jun 2005 14:18:52 -0700 [thread overview]
Message-ID: <20050614211852.GA20037@suse.de> (raw)
In-Reply-To: <1118783140.7069.12.camel@siliver.austin.ibm.com>
On Tue, Jun 14, 2005 at 04:05:40PM -0500, V. ANANDA KRISHNAN wrote:
> Hi All,
>
> In ppc architecture, I am trying to find out the codes that populate
> the pci_devic_id structure ( drivers/serial/8250_pci.c file) in the
> following init_one function:
>
> static int __devinit
> pciserial_init_one(struct pci_dev *dev, const struct pci_device_id *ent)
It comes from the driver itself, as you point out:
> I have the (pci card) data hard-coded in the following tables of
> 8250_pci.c file:
> static struct pci_device_id serial_pci_tbl[]
> static struct pci_board pci_boards[] __devinitdata={...}
Yup, that's what the pci core sets that pointer to.
> Since I could not find the data in the pci_device_id for pci card, I
> went thru the drivers/pci/search.c and drivers/pci/pci-driver.c files. I
> am not successful in locating those codes that populate the
> pci_device_id structure for a given pci card.
drivers/pci/pci-driver.c::pci_device_probe_static() does it. See the
latest edition of the Linux Device Drivers book for a full description
and walk-through of how a pci device get added and removed from the
driver core (it's free online if you don't want to buy it.)
Hope this helps,
greg k-h
prev parent reply other threads:[~2005-06-14 21:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-14 21:05 serial port driver 8250_pci - pci_device_id structure V. ANANDA KRISHNAN
2005-06-14 21:18 ` Greg KH [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=20050614211852.GA20037@suse.de \
--to=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mansarov@us.ibm.com \
/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.