Stephen Wille Padnos wrote:
> Eric H. Johnson wrote:
>> Note: I moved SVST8_4.BIT to the bin folder just to avoid a path problem
>> with that file. I also tried putting rtlib/ before hm2_5i20, but that did
>> not work.
>>
> I think this is an artifact of using the kernel request_firmware
> system. It requires that the firmware come from the /lib/firmware (or
> similar) tree. This presents a problem when you have multiple
> run-in-place versions, or you have run-in-place and installed versions.
> I don't know the specifics of how to deal with this, but I think you
> more or less have to stick the firmware in the expected tree somewhere.
> I'm not sure how you specify the name at that point - the source (kernel
> or hostmot2) may tell you.
Steve is right, the hostmot2 driver looks in /lib/firmware for .BIT
files, never in /bin or anywhere else. Whatever is in /lib/firmware/hm2
is what it'll load. If you're not hacking on the firmware itself this
won't affect you at all.
If you want to have different firmwares available, you can symlink them
to /lib/firmware/hm2.test, /lib/firmware/hm2.rip-trunk, etc, and load
the driver with "firmware=hm2.test/5i20/SWP-SV12.BIT" or similar.
--
Sebastian Kuzminsky
Theo: "Julian? I haven't seen you in twenty years. You look good.
The picture the police have of you doesn't do you justice."
Julian: "What do the police know about justice?"
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
