From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: Problem with Avermedia 771 Date: Thu, 21 Oct 2004 18:36:04 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <20041021101818.GA1182@bytesex> <20041021114311.GA2190@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: 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 14:11:44 +0200, I wrote: > > At Thu, 21 Oct 2004 13:43:11 +0200, > Gerd Knorr wrote: > > > > > 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. > > > > Yep, that should make the correct ID list visible to hotplug ... > > Ok, how about the attached patch? > > We may have a certralized header file such as linux/bt_pci_id.h > containig the entries of known working boards so that this can be > included from different drivers... BTW, I'll be in vacation from tomorrow for a couple of weeks. Will be unreachable from nets for a while... ciao, 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