From: Jeff Garzik <jgarzik@pobox.com>
To: Stuart Young <cef-lkml@optusnet.com.au>
Cc: linux-kernel@vger.kernel.org, root@chaos.analogic.com,
Markus Lidel <Markus.Lidel@shadowconnect.com>
Subject: Re: Problem with ioremap which returns NULL in 2.6 kernel
Date: Wed, 02 Jun 2004 22:51:43 -0400 [thread overview]
Message-ID: <40BE923F.7070601@pobox.com> (raw)
In-Reply-To: <200406031241.27669.cef-lkml@optusnet.com.au>
Stuart Young wrote:
> On Thu, 3 Jun 2004 01:45, Richard B. Johnson wrote:
>
>>I asked for the output of `cat /proc/pci` . Unless I get that
>>information, I can't find the length of the allocation.
>
>
> Is there no way to to get this information out of lspci (eg: lspci -vv)? This
> is particularly annoying since /proc/pci is depreciated. I know a number of
You _can_ get that information out of lspci.
Jeff
next prev parent reply other threads:[~2004-06-03 2:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 12:37 Problem with ioremap which returns NULL in 2.6 kernel Markus Lidel
2004-06-01 14:21 ` Jeff Garzik
2004-06-01 15:21 ` Markus Lidel
2004-06-01 17:08 ` Davide Rossetti
2004-06-02 8:59 ` Markus Lidel
2004-06-01 23:32 ` Jeff Garzik
2004-06-02 8:55 ` Markus Lidel
2004-06-02 13:23 ` Jeff Garzik
2004-06-02 13:49 ` Markus Lidel
2004-06-02 13:46 ` Jeff Garzik
2004-06-02 14:18 ` Markus Lidel
2004-06-02 14:39 ` Richard B. Johnson
2004-06-02 15:26 ` Markus Lidel
2004-06-02 15:45 ` Richard B. Johnson
2004-06-03 2:41 ` Stuart Young
2004-06-03 2:51 ` Jeff Garzik [this message]
2004-06-03 8:38 ` Markus Lidel
2004-06-03 11:42 ` Richard B. Johnson
2004-07-16 11:19 ` Richard B. Johnson
2004-06-02 0:09 ` Zwane Mwaikambo
2004-06-02 12:17 ` Markus Lidel
2004-06-04 20:16 ` Zwane Mwaikambo
2004-07-16 17:29 ` Zwane Mwaikambo
2004-07-16 17:30 ` Jeff Garzik
2004-07-17 0:30 ` Markus Lidel
2004-07-17 0:33 ` Markus Lidel
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=40BE923F.7070601@pobox.com \
--to=jgarzik@pobox.com \
--cc=Markus.Lidel@shadowconnect.com \
--cc=cef-lkml@optusnet.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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