Hi,
how do I make it so that the firmware for a particular device doesn't get unloaded when the device is no longer in use?
Apparently the firmware is unloaded when the device becomes unused. At least it is loaded again when the device is used again; messages in dmesg show that the firmware is loaded again. There are no messages about unloading the firmware, so I don't know whether it is actually unloaded or not.
Loading the firmware again (or unloading it) seems to cause problems with the device. So I would like to load the firmware once and keep it loaded, without any more attempts to load it once it has been loaded.
On 20.06.2014 21:25, lee wrote:
Hi,
how do I make it so that the firmware for a particular device doesn't get unloaded when the device is no longer in use?
Apparently the firmware is unloaded when the device becomes unused. At least it is loaded again when the device is used again; messages in dmesg show that the firmware is loaded again. There are no messages about unloading the firmware, so I don't know whether it is actually unloaded or not.
Loading the firmware again (or unloading it) seems to cause problems with the device. So I would like to load the firmware once and keep it loaded, without any more attempts to load it once it has been loaded.
Only you know how to complicate like this. :) Why not solve the problem with the device, entirely. What is that device, a telescope?
poma
poma pomidorabelisima@gmail.com writes:
On 20.06.2014 21:25, lee wrote:
Hi,
how do I make it so that the firmware for a particular device doesn't get unloaded when the device is no longer in use?
Apparently the firmware is unloaded when the device becomes unused. At least it is loaded again when the device is used again; messages in dmesg show that the firmware is loaded again. There are no messages about unloading the firmware, so I don't know whether it is actually unloaded or not.
Loading the firmware again (or unloading it) seems to cause problems with the device. So I would like to load the firmware once and keep it loaded, without any more attempts to load it once it has been loaded.
Only you know how to complicate like this. :) Why not solve the problem with the device, entirely.
That's what I'm trying.
On 21.06.2014 11:13, lee wrote:
poma pomidorabelisima@gmail.com writes:
On 20.06.2014 21:25, lee wrote:
Hi,
how do I make it so that the firmware for a particular device doesn't get unloaded when the device is no longer in use?
Apparently the firmware is unloaded when the device becomes unused. At least it is loaded again when the device is used again; messages in dmesg show that the firmware is loaded again. There are no messages about unloading the firmware, so I don't know whether it is actually unloaded or not.
Loading the firmware again (or unloading it) seems to cause problems with the device. So I would like to load the firmware once and keep it loaded, without any more attempts to load it once it has been loaded.
Only you know how to complicate like this. :) Why not solve the problem with the device, entirely.
That's what I'm trying.
Super duper, and you know this is not the only mail list out there. :)
poma
poma pomidorabelisima@gmail.com writes:
On 21.06.2014 11:13, lee wrote:
poma pomidorabelisima@gmail.com writes:
Why not solve the problem with the device, entirely.
That's what I'm trying.
Super duper, and you know this is not the only mail list out there. :)
And?
Please feel free to unsubscribe from this list when you think that users of Fedora are not supposed to ask questions here.
On 21.06.2014 21:36, lee wrote:
poma pomidorabelisima@gmail.com writes:
On 21.06.2014 11:13, lee wrote:
poma pomidorabelisima@gmail.com writes:
Why not solve the problem with the device, entirely.
That's what I'm trying.
Super duper, and you know this is not the only mail list out there. :)
And?
Please feel free to unsubscribe from this list when you think that users of Fedora are not supposed to ask questions here.
It is certainly your conclusion, but totally missed one.
Is it not clear that anyone can at least try to ask something meaningful, but also anyone can respond to. With the exception of spam and the like, of course :)
You really insist discuss kernel module internals, here, on this list!? :) OK let me help you, select one that fits your device and subscribe, http://vger.kernel.org/vger-lists.html Unfortunately there is no telescope-devel@, but you can always ask on the one related to the bus to which the device is connecting.
However, if you find interlocutors here, indeed it does not bother me at all. That would actually be interesting to follow. However. Here. :)
poma
poma pomidorabelisima@gmail.com writes:
On 21.06.2014 21:36, lee wrote:
poma pomidorabelisima@gmail.com writes:
On 21.06.2014 11:13, lee wrote:
poma pomidorabelisima@gmail.com writes:
Why not solve the problem with the device, entirely.
That's what I'm trying.
Super duper, and you know this is not the only mail list out there. :)
And?
Please feel free to unsubscribe from this list when you think that users of Fedora are not supposed to ask questions here.
It is certainly your conclusion, but totally missed one.
Is it not clear that anyone can at least try to ask something meaningful, but also anyone can respond to. With the exception of spam and the like, of course :)
You really insist discuss kernel module internals, here, on this list!? :) OK let me help you, select one that fits your device and subscribe, http://vger.kernel.org/vger-lists.html Unfortunately there is no telescope-devel@, but you can always ask on the one related to the bus to which the device is connecting.
However, if you find interlocutors here, indeed it does not bother me at all. That would actually be interesting to follow. However. Here. :)
Like I said, totally besides the point.
vlado99 V.99@seznam.cz writes:
On 20.6.2014 21:25, lee wrote:
Apparently the firmware is unloaded when the device becomes unused.
Maybe the device firmware is not unloaded, it is just forget when unused device enters low power state/is powered off?
I don't know, it seems that the firmware is loaded every time the device is being accessed, perhaps with a timeout. I don't know of any way to tell whether a device is powered down or not or how to tell whether firmware is actually unloaded (is that even possible?) or not.
Loading the same firmware several times might be a bug.