Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751022AbWEFSKF (ORCPT ); Sat, 6 May 2006 14:10:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751062AbWEFSKF (ORCPT ); Sat, 6 May 2006 14:10:05 -0400 Received: from khc.piap.pl ([195.187.100.11]:36620 "EHLO khc.piap.pl") by vger.kernel.org with ESMTP id S1751022AbWEFSKD (ORCPT ); Sat, 6 May 2006 14:10:03 -0400 To: "Jon Smirl" Cc: "Dave Airlie" , "Greg KH" , "Ian Romanick" , "Dave Airlie" , "Arjan van de Ven" , linux-kernel@vger.kernel.org Subject: Re: Add a "enable" sysfs attribute to the pci devices to allow userspace (Xorg) to enable devices without doing foul direct access References: <20060505202603.GB6413@kroah.com> <9e4733910605051335h7a98670ie8102666bbc4d7cd@mail.gmail.com> <20060505210614.GB7365@kroah.com> <9e4733910605051415o48fddbafpf0f8b096f971e482@mail.gmail.com> <20060505222738.GA8985@kroah.com> <9e4733910605051705j755ad61dm1c07c66c2c24c525@mail.gmail.com> <21d7e9970605051857l4415a04ai7d1b1f886bb01cee@mail.gmail.com> <9e4733910605052039n7d2debbse0fd07e0d1d059fb@mail.gmail.com> <9e4733910605060608l57c1a215pa300c326ef1eef4b@mail.gmail.com> From: Krzysztof Halasa Date: Sat, 06 May 2006 20:10:01 +0200 In-Reply-To: <9e4733910605060608l57c1a215pa300c326ef1eef4b@mail.gmail.com> (Jon Smirl's message of "Sat, 6 May 2006 09:08:28 -0400") Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 982 Lines: 23 "Jon Smirl" writes: > Substitute vga with the name of whatever class of device you are > working on and build it a minimal driver for it. The technique is > generic. The card in question _has_ a driver. I, for example, just need a way to write EEPROM data to it (vendor/device ID etc). The card has to be selected by PCI bus and slot (device) number, not by device class and/or IDs, because it can contain garbage and/or some generic IDs with generic device class. I'm not against the additional driver but it has to be able to work with any specified card (as setpci does). But if it's that simple then why not do that in the PCI code instead (holding some device file open isn't a problem)? -- Krzysztof Halasa - 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/