From: Jim Nelson <james4765@verizon.net>
To: eshwar <eshwar@moschip.com>
Cc: newbie <linux-newbie@vger.kernel.org>
Subject: Re: any way to find which pci driver uses what memory region & Any way to find which driver is attached to which device file
Date: Thu, 14 Oct 2004 18:11:09 -0400 [thread overview]
Message-ID: <416EF97D.9050401@verizon.net> (raw)
In-Reply-To: <025301c4b743$dd7a2d00$41c8a8c0@Eshwar>
eshwar wrote:
>HI,
>
> Is there any way to find which pci driver uses what memroy regions and any
>way to find which driver si attached to which device file
>
>
>
"cat /proc/iomem". That will list the memory addresses assigned to the
various PCI devices. Some kernels have PCI name support compiled in
(most stock distro kernels do), but without it, you get the PCI bus
location numbers, and have to do a bit of work with lspci to identify
what each adapter is.
I don't understand why you need to know PCI memory address regions -
they are remapped at device configuration time (unlike ISA) unless you
have a seriously broken adapter card.
What do you mean "any way to find which driver is attached to which
device file"? You can use "cat /proc/devices" to get the major number
assigned to each block and char driver, and then do a "ls -l
/dev/[device file name]" to get the major and minor numbers assigned to
that device. From there, things get more driver-specific - different
drivers use minor numbers in different ways.
More info about what you're actually trying to do would help.
Jim
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
prev parent reply other threads:[~2004-10-14 22:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 8:15 any way to find which pci driver uses what memory region & Any way to find which driver is attached to which device file eshwar
2004-10-14 22:11 ` Jim Nelson [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=416EF97D.9050401@verizon.net \
--to=james4765@verizon.net \
--cc=eshwar@moschip.com \
--cc=linux-newbie@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