Date: Mon, 13 Mar 2006 21:18:30 +0100
Message-ID: <s5h3bhmm73d.wl%tiwai@suse.de>
From: Takashi Iwai <tiwai@suse.de>
To: "Simon White" <s_a_white@email.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ISA "struct device"
In-Reply-To: <20060313193246.EEFF01F50C4@ws1-2.us4.outblaze.com>
References: <20060313193246.EEFF01F50C4@ws1-2.us4.outblaze.com>
User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 MULE XEmacs/21.5 (beta24)
 (dandelion) (i386-suse-linux)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1331
Lines: 34

At Mon, 13 Mar 2006 14:32:46 -0500,
Simon White wrote:
> 
> Hi,
> 
> I am supporting various hardsid/catweasel cards that provide _probe
> calls.  These _probe calls are called with struct pci_device and
> friends that contain various information about bus, slot, id,
> resources, etc.
> 
> I see that isa pnp does something similar and all this information is
> appears via /sys presumably for utitilies to pick up and do nice
> things with.
> 
> Am wondering what happens with non pnp isa (unfortunately nolonger
> have an ISA machine to experiment with).  Currently in the driver I
> just use request_region with a few known addresses, with a challange
> respone mechanism to see if it is the right thing.  How does one go
> about getting that into a nice, sensibly filled out "struct device"
> object and register it with /sys, for it to do the right thing.
> Are there any existing examples to follow?

platform_device is the easiest solution for non-PnP ISA drivers.

You can find many drivers when you grep with platform_device
(including 2.6.16-rc* ALSA ISA drivers :)


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