On Wed, 8 Nov 2006, Tyler Trafford wrote: > On Wed, Nov 08, 2006 at 04:53:25PM -0500, Robert Hardy wrote: > > >> The fact that this could be worked around by adding a delay (and only > >> seems to effect SMP systems) makes me think it has to do with > >> multiple firmware_request calls stomping on each other. > > > > That sounds as plausible an explanation as any I've heard so far... > > Oh, I bet it's actually that the pipe created to read the firmware files > isn't destroyed fast enough, which is bad since for all three files it > is in the same location. > > I wonder if there are any other drivers with multiple firmware loads > which have/had similar problems.
Yes, there have been lots of problems with sequential multiple firmware loads on the kernel mailing list, but don't ask me to quote details as I don't remember and I'm too tired right now. I think the ipw* drivers were one such case. I believe people have worked around it by joining multi-part firmwares into a single file and loading it with a single request_firmware call, but I could be blowing smoke on that... Regards, Rob -- ---------------------"Happiness is understanding."---------------------- Robert Hardy, B.Eng Computer Systems C.E.O. Webcon Inc. rhardy <at> webcon <dot> ca GPG Key available (613) 276-7327 _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
