From: Francois Romieu <romieu@cogenit.fr>
To: Sebastian Heidl <heidl@zib.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: find struct pci_dev from struct net_device
Date: Thu, 13 Sep 2001 14:10:24 +0200 [thread overview]
Message-ID: <20010913141024.A24905@se1.cogenit.fr> (raw)
In-Reply-To: <20010912145242.C20089@csr-pc1.zib.de>
In-Reply-To: <20010912145242.C20089@csr-pc1.zib.de>; from heidl@zib.de on Wed, Sep 12, 2001 at 02:52:42PM +0200
Sebastian Heidl <heidl@zib.de> :
> What's the easiest way to find a corresponding struct pci_dev from a
> struct net_device ? Especially, if the driver does not set
> pci_dev.driver_data to it's net_device struct (such as the acenic
> driver) ?
Forget it. It depends on the driver in both directions. How would it
handle a pci device with different L2 interfaces or a network adapter
with PCI bridge + various PCI devices behind the bridge ?
--
Ueimor
next prev parent reply other threads:[~2001-09-13 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-12 12:52 find struct pci_dev from struct net_device Sebastian Heidl
2001-09-13 12:10 ` Francois Romieu [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-13 9:22 Hen, Shmulik
2001-09-13 9:41 ` David Woodhouse
2001-09-13 10:34 Hen, Shmulik
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=20010913141024.A24905@se1.cogenit.fr \
--to=romieu@cogenit.fr \
--cc=heidl@zib.de \
--cc=linux-kernel@vger.kernel.org \
/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