From: Alessandro Suardi <alessandro.suardi@oracle.com>
To: Dave Airlie <airlied@skynet.ie>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCI again in 2.4.15-pre4
Date: Tue, 13 Nov 2001 12:20:46 +0100 [thread overview]
Message-ID: <3BF1020E.2AFEEEDC@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.32.0111122334280.4284-100000@skynet>
Dave Airlie wrote:
>
> I saw this first in 2.4.15-pre2 here it is again for pre4.
>
> I've attached a cat /proc/pci which is bad, my Xircom doesn't show up,
> further down I've attached an lspci -v -H 1 and it has my Xircom on it ..
>
> Anyone care to comment... this worked in 2.4.10 I'll try to patch up to
> 2.4.14 and see where it stared..
>
> Dave.
Confirmed on -pre3 - Xircom RBEM56G100 is "invisible" to /proc/pci.
--alessandro
"we live as we dream alone / to break the spell we mix with the others
we were not born in isolation / but sometimes it seems that way"
(R.E.M., live intro to 'World Leader Pretend')
prev parent reply other threads:[~2001-11-13 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 23:37 PCI again in 2.4.15-pre4 Dave Airlie
2001-11-13 11:20 ` Alessandro Suardi [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=3BF1020E.2AFEEEDC@oracle.com \
--to=alessandro.suardi@oracle.com \
--cc=airlied@skynet.ie \
--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