(Cc linux1394-devel, for the record)
Gene Heskett wrote:
> On Sunday 17 December 2006 13:31, Stefan Richter wrote:
>> Is your version of kino still using dv1394 or does it work without
>> dv1394 loaded too?
>>
> AFAIK, its kino is 0.9.3. Ok, while kino is running I did a modprobe -rv
> dc1394 and it removed dv1394.ko and ohci1394.ko
When dv1394 is loaded, the use count of ohci1394 is incremented because
dv1394 uses symbols of ohci1394. Likewise, when dv1394 is removed,
ohci1394's use count is decremented which may render ohci1394 "unused".
It will then be removed too. This is of course not desired in many cases.
> Now when going to the capture screen is says the device /dev/raw1394 is
> gone or the kernel module isn't loaded. raw1394 is still resident
> according to an lsmod, so I'm puzzled as to why the device was removed
> when the module is still present.
raw1394 does not mark FireWire hosts as in use. I think we should add
try_module_get(host->driver->owner) and module_put(host->driver->owner)
either to initiation and release of requests, or to the raw1394_open()
and raw1394_release() hooks for all hosts which are present when the
file is opened, or simply to raw1394's add_host() and remove_host() hooks.
I'll make a note on bugzilla.kernel.org and try to find a proper fix
some time.
> So I modprobe -rv raw1394 and it took
> out raw1394 and ieee1394, then reloaded raw1394 which loaded ieee1394.
> And kino is still without controls but does not now report the error at
> the bottom of its screen. Quitting it and restarting it restores the
> error. Then loading dv1394 also brings in ohci1394, and a recycle out and
> back to the capture window restored the controls.
>
> So I removed dv1394, and reloaded only ohci1384,
That's what was necessary after you removed dv1394.
> but an attempt to change
> screens in kino locked the box up tight, not even the x-clock in the
> right corner was running and I had to hard reset it.
This is, how should I put it, not good. Maybe raw1394 still held
resources on behalf of kino which related to the host that first
vanished, then reappeared as a new one. Anyway; raw1394 is supposed to
handle life addition and removal of hosts, but we obviously missed
something.
> With 4 modules to play with and 4!=15, its the lack of the dv1394 module
> that isn't exactly friendly, the other combo's just kill the controls.
>
> AIUI, it *should* be ohci1394 handling the controls stuff, so this
> represents a bit of a puzzle. Or the AIUI is wrong :)
...
What if you prevent dv1394 from ever being loaded, or don't build it in
the first place? CONFIG_IEEE1394_DV1394=n
--
Stefan Richter
-=====-=-==- ==-- =---=
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
