From: Greg KH <greg@kroah.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: pci_disable_device kills hardware (was Re: [PATCH] propagate pci_enable_device() errors)
Date: Thu, 26 Aug 2004 16:25:05 -0700 [thread overview]
Message-ID: <20040826232505.GB14515@kroah.com> (raw)
In-Reply-To: <412E6EC3.4060606@pobox.com>
On Thu, Aug 26, 2004 at 07:14:11PM -0400, Jeff Garzik wrote:
> Greg KH wrote:
> >On Thu, Aug 26, 2004 at 03:52:51PM -0400, Jeff Garzik wrote:
> >
> >>thanks much.
> >>
> >>We still need to figure out what to do for multiple-driver situations,
> >>since the additional of pci_disable_device() calls literally
> >>_guarantees_ failures in a two-drivers-for-the-same-hardware situation.
> >
> >
> >the "two-drivers-for-the-same-hardware" is what needs to be fixed.
> >You are on your own if you do that.
>
>
> Sure, but that's handwaving away reality... It stands to reason that we
> would all _prefer_ one driver for each piece of hardware.
That's what the pci driver model forces you to do. If you go around
behind the back of it, you get what you deserve :)
For stuff like this, the IDE drivers need to be changed to use the (what
is it, 4 years old now?) pci driver model. There's no reason technical
why such a conversion hasn't happened yet, right?
thanks,
greg k-h
prev parent reply other threads:[~2004-08-26 23:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 19:29 [PATCH] propagate pci_enable_device() errors Bjorn Helgaas
[not found] ` <412E3F93.9030503@pobox.com>
2004-08-26 22:41 ` pci_disable_device kills hardware (was Re: [PATCH] propagate pci_enable_device() errors) Greg KH
2004-08-26 23:14 ` Jeff Garzik
2004-08-26 23:25 ` Greg KH [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=20040826232505.GB14515@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=jgarzik@pobox.com \
--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
all inboxes | Powered by JetHome®