Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261540AbVBOBlf (ORCPT ); Mon, 14 Feb 2005 20:41:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261562AbVBOBlf (ORCPT ); Mon, 14 Feb 2005 20:41:35 -0500 Received: from s-utl01-nypop.stsn.com ([199.106.90.52]:18352 "HELO s-utl01-nypop.stsn.com") by vger.kernel.org with SMTP id S261540AbVBOBld (ORCPT ); Mon, 14 Feb 2005 20:41:33 -0500 Subject: Re: avoiding pci_disable_device()... From: Arjan van de Ven To: Jeff Garzik Cc: Greg KH , Linux Kernel , Andrew Morton , Alan Cox In-Reply-To: <4211013E.6@pobox.com> References: <4210021F.7060401@pobox.com> <20050214190619.GA9241@kroah.com> <4211013E.6@pobox.com> Content-Type: text/plain Date: Mon, 14 Feb 2005 15:02:32 -0500 Message-Id: <1108411352.5994.27.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 15 Feb 2005 01:41:33.0094 (UTC) FILETIME=[7A7D9C60:01C512FF] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 753 Lines: 18 > No. You also need to consider situations such as out-of-tree drivers > for the same hardware (might not use PCI API), and situations where you > have peer devices discovered and used (PCI API doesn't have "hey, > device is associated with , too" capability) there's not a lot you or anyone else can do about such broken (and often proprietary) drivers.... if a device doesn't use the kernel API's its end of game basically. Adding more new API's isn't going to help you ... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/