Mark Paulus wrote:
I used this patch and managed to get the modules to compile and load
on my 2.6.18 debian/etch kernel. However, I have a question. Will
these modules now load in a deterministic manner? For instance,
on this box I have a PVR-150, a air2PC card, an Avermedia A180, and a
DVICO pcHDTV RT5 lite. My issue is that in myth, I need to assign the
proper /dev/device to the proper capture device.
To get around that with previous versions, I had some custom rules in
hotplug/udev that would create custom aliases, such as /dev/ivtv0,
/dev/bttv_vid0. However, this release has broken the mechanism that
created my /dev/ivtv0, so mythtv isn't happy.
Will all devices load and create /dev/video* in the same order all the
time,
or is it still up in the air as to which device will create which
/dev/video*, based upon who's faster today????
This is a long outstanding issue with udev/hotplug, but someone needs to
fix it, if they can figure out how.
Ok, I fixed up my udev script, and now I have my /dev/ivtv0 device again.
So, using your tree, everything seems to be working on my 2.6.18 box,
with the small patchset provided by Scott Reynolds. The appropriate
dmesg messages were attached to my previous email. So, outside
of a couple of small glitches, these drivers seem to be backwards
compatible.
begin:vcard
fn:Mark Paulus
n:Paulus;Mark
org:MCI;Lec Interfaces / 40419
adr;dom:;;2424 Garden of the Gods Rd;Colorado Springs;CO;80919
email;internet:[EMAIL PROTECTED]
title:Mark Paulus
tel;work:719-535-5578
tel;pager:800-pagemci / 1406052
tel;home:v622-5578
version:2.1
end:vcard
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
