On Thu, 2005-06-02 at 13:49 -0400, Nathanael Nerode wrote: > Andres Salomon wrote: [...] > > > > I haven't bothered looking at other drivers in the tree that support > > firmware loading; are paths hardcoded in there, or is the firmware > > location simply a module/kernel arg? > Hardcoded, consistently. The few present have erratically chosen names > hardcoded. Indeed I have no idea where to find the firmware files to go > with some of those names, which is an issue. > > I think the feeling was that the file in that location can be replaced > rather than changing the name searched for, and that that was simpler. > I'm not doctrinaire about it or anything though! >
Oh, that's lovely. We should probably move this policy into userspace, or allow the root path to be overridden via procfs/sysfs. I'll make a note to check it out. > >>Oh, what I was thinking was this: > >>> (1) reorganize the upstream kernel driver so that the included firmware > >>> was in > >>> a separate file (#included, for instance), as is done in most such drivers > > > > > > This alone would go a long way towards making my life easier, if > > upstream accepted it. > Well, maybe I should do that first. :-) Yes, please. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
