> -----Original Message----- > From: video4linux-list-admin@xxxxxxxxxx > [mailto:video4linux-list-admin@xxxxxxxxxx] On Behalf Of > mhargrea@xxxxxxxxxxx > Sent: Monday, 21 July 2003 5:26 PM > To: video4linux-list@xxxxxxxxxx > Cc: video4linux-list@xxxxxxxxxx; video4linux-list-admin@xxxxxxxxxx > Subject: RE: SAA7134 multiple cards - options > > > > you could always try copying the saa7134.o file to another > name say saa7134_b.o > then use the duplicate options below. > > > alias char-major-81-0 saa7134 > options saa7134 oss=1 oss_debug=1 audio_debug=1 \ > ts_debug=1 core_debug=1 audio_debug=1 vbi_debug=1\ > i2c_debug=1 core_debug=1 \ > vbi_nr=1 mixer_nr=1 radio_nr=1\ > dsp_nr=1 ts_nr=1 video_nr=1 > > # Card 1 > alias char-major-81-1 saa7134_b > options saa7134_b oss=1 oss_debug=1 audio_debug=1 \ > ts_debug=1 core_debug=1 audio_debug=1 vbi_debug=1\ > i2c_debug=1 core_debug=1 \ > vbi_nr=2 mixer_nr=2 radio_nr=2\ > dsp_nr=2 ts_nr=2 video_nr=2 > > > Maybe... The first time you load the module it detects both cards and configures them then. However since the second card can't be configured with the same parameters, it should fail. The second renamed module should be able to get the second card only right? Or will it try to set up both cards? Another issue is the possible conflict between the two modules identical in every way except name. Is the module name embedded in the module itself or does it merely come from the filename? It's a nice idea and although it might break I will definitely try it. "Now why didn't I think of that?" he says to himself. Thanks for the suggestion CH
