From: Martin Dalecki <dalecki@evision-ventures.com>
To: Andre Hedrick <andre@linuxdiskcert.org>
Cc: Tim Moore <timothymoore@bigfoot.com>, linux-kernel@vger.kernel.org
Subject: Re: disk transfer speed problem
Date: Thu, 28 Feb 2002 13:27:00 +0100 [thread overview]
Message-ID: <3C7E2214.3030201@evision-ventures.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10202272049180.22351-100000@master.linux-ide.org>
Andre Hedrick wrote:
> What is more useful is the cat /proc/ide/ide0/config !!!
>
>>From that I can tell you what is going on completely about the system.
>
> Oh and for those not reading this email, it is a side note on why the ide
> proc-pci interface had best be left alone and in tact.
Module the fact fact lspci could be easly extendid to provide the
same information from user space... wait... we are on unix and we have
manual pages:
-x Show hexadecimal dump of first 64 bytes of the PCI
configuration space (the standard header). Useful
for debugging of drivers and lspci itself.
-xxx Show hexadecimal dump of whole PCI configuration
space. Available only for root as several PCI
devices crash when you try to read undefined por-
tions of the config space (this behaviour probably
doesn't violate the PCI standard, but it's at least
very stupid).
As you can see lspci -x -xxx ALREADY DOES THIS!
next prev parent reply other threads:[~2002-02-28 12:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 20:49 disk transfer speed problem lonely wolf
2002-02-28 2:06 ` Tim Moore
2002-02-28 4:51 ` Andre Hedrick
2002-02-28 11:56 ` Dave Jones
2002-02-28 17:14 ` Andre Hedrick
2002-02-28 12:27 ` Martin Dalecki [this message]
2002-02-28 22:48 ` Stephen Samuel
2002-02-28 23:58 ` lonely wolf
[not found] <Pine.LNX.4.33.0202271701360.13103-100000@coffee.psychology.mcmaster.ca>
2002-02-27 22:52 ` lonely wolf
2002-02-27 23:46 ` Alan Cox
2002-02-28 9:20 ` Davidovac Zoran
2002-02-28 14:49 ` lonely wolf
2002-03-01 2:25 ` lonely wolf
2002-03-01 10:59 ` Andre Hedrick
2002-03-01 10:51 ` Marco Colombo
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=3C7E2214.3030201@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=andre@linuxdiskcert.org \
--cc=linux-kernel@vger.kernel.org \
--cc=timothymoore@bigfoot.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox