Message-ID: <41FA5F22.5020008@drzeus.cx>
Date: Fri, 28 Jan 2005 16:49:54 +0100
From: Pierre Ossman <drzeus-list@drzeus.cx>
User-Agent: Mozilla Thunderbird 0.9 (X11/20041127)
MIME-Version: 1.0
To: "Randy.Dunlap" <rddunlap@osdl.org>
CC: LKML <linux-kernel@vger.kernel.org>
Subject: Re: PNP and bus association
References: <41F95A42.40001@drzeus.cx> <41F97185.6030905@osdl.org>
In-Reply-To: <41F97185.6030905@osdl.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1398
Lines: 37

Randy.Dunlap wrote:

> Pierre Ossman wrote:
>
>> I recently tried out adding PNP support to my driver to remove the 
>> hassle of finding the correct parameters for it. This, however, 
>> causes it to show up under the pnp bus, where as it previously was 
>> located under the platform bus.
>>
>> Is the idea that PNP devices should only reside on the PNP bus or is 
>> there some magic available to get the device to appear on several 
>> buses? It's a bit of a hassle to search in two different places in 
>> sysfs depending on if PNP is used or not.
>>
>> Also, the PNP bus doesn't really say that much about where the device 
>> is physically connected. The other bus types usually give a hint 
>> about this.
>
>
> Not to take away from your question, but:
> Is there "the PNP bus"?  I've seen an ISA bus that (sort of)
> supports PNP, PCI PNP, NuBus PNP, USB PNP, IEEE 1394 PNP, etc.
>
It's not a physical bus but it is a bus as far as the kernel is 
concerned. And that's really my problem. I want it to support PNP, but 
also to associate with the physical bus it's connected to.

Rgds
Pierre

PS. Your outgoing mail server gives the wrong HELO

-
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/