From: Alan Cox <alan@redhat.com>
To: root@chaos.analogic.com
Cc: jgarzik@mandrakesoft.com (Jeff Garzik),
davej@suse.de, alan@redhat.com (Alan Cox),
becker@scyld.com,
linux-kernel@vger.kernel.org (Linux Kernel Mailing List)
Subject: Re: [PATCH] Hamachi not doing pci_enable before reading resources
Date: Wed, 7 Feb 2001 15:42:20 -0500 (EST) [thread overview]
Message-ID: <200102072042.f17KgKW03277@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1010207152715.2498A-100000@chaos.analogic.com> from "Richard B. Johnson" at Feb 07, 2001 03:30:07 PM
> I stand by my statement. PCI devices that require resources are
> required to provide read/write registers indicating these resources
> whether or not the enable bits are set. This is mandatory.
And the assignment of those resources is done by pci_enable_device. So
looking at the irq data or the BAR assignment until pci_enable_device
has done its work doesnt tell you anything meaningful
It doesnt just flip the IO and MEM bits
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-07 20:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 19:17 [PATCH] Hamachi not doing pci_enable before reading resources davej
2001-02-07 19:23 ` Jeff Garzik
2001-02-07 19:50 ` Richard B. Johnson
2001-02-07 20:05 ` Jeff Garzik
2001-02-07 20:30 ` Richard B. Johnson
2001-02-07 20:42 ` Alan Cox [this message]
2001-02-07 20:50 ` Gérard Roudier
2001-02-07 22:18 ` Richard B. Johnson
-- strict thread matches above, loose matches on Subject: below --
2001-02-07 19:43 davej
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=200102072042.f17KgKW03277@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=becker@scyld.com \
--cc=davej@suse.de \
--cc=jgarzik@mandrakesoft.com \
--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