From: Martin Mares <mj@ucw.cz>
To: Enrico Bartky <DOSProfi@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: lspci != scanpci !?
Date: Sat, 15 Jan 2005 13:35:54 +0100 [thread overview]
Message-ID: <20050115123554.GA2115@ucw.cz> (raw)
In-Reply-To: <003d01c4fa7b$983b21b0$0c00a8c0@amd64>
Hello!
> Now the scanpci command shows the M7101 BUT lspci and /proc/pci,
> /proc/bus/pci, /sys/bus/pci NOT. What can I do? Is there anything like a
> "update_pci" command?
What does `lspci -vv -M' and `lspci -vv -M -H1' print?
(Please Cc to me, I usually read LKML in large batches.)
Have a nice fortnight
--
Martin `MJ' Mares <mj@ucw.cz> http://atrey.karlin.mff.cuni.cz/~mj/
Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth
Air conditioned environment -- Do not open Windows.
next prev parent reply other threads:[~2005-01-15 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 20:57 lspci != scanpci !? Enrico Bartky
2005-01-14 22:37 ` Matthew Dharm
2005-01-15 12:35 ` Martin Mares [this message]
2005-01-15 15:54 ` Enrico Bartky
-- strict thread matches above, loose matches on Subject: below --
2005-01-14 23:01 Enrico Bartky
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=20050115123554.GA2115@ucw.cz \
--to=mj@ucw.cz \
--cc=DOSProfi@web.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