From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: Problem with Avermedia 771 Date: Thu, 21 Oct 2004 12:38:28 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <20041021101818.GA1182@bytesex> Mime-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <20041021101818.GA1182@bytesex> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Gerd Knorr Cc: Clemens Ladisch , Jaroslav Kysela , Holger Waechtler , dvb list , alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Thu, 21 Oct 2004 12:18:18 +0200, Gerd Knorr wrote: > > > The new patch hides the whitelisted ids from the exported PCI id > > table, i.e. hotplug can't know which driver should be loaded for the > > certain known device. > > If the wildcard entry is in there as well like it used to be that > doesn't really make a difference, hotplug doesn't know that the driver > will ignore the card by default because it is tagged "DEFAULT_ENTRY" via > driver-data ... Yes, that was my concern. The hotplug can load multiple modules, but it's disabled as default. That's the reason why I suggested the second way in my earlier post: We prepare two pci_id tables, one for the whitelist and another for the default ids. Only the former is exported. When the module option is given, the latter id is registered while usually the fomer is used. Takashi ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl