ReadMe.html
1<html>
2<title>BeOS driver for USBVision (Nogatech) TV tuners</title>
3<body bgcolor="#f0f0e0">
4<h1>BeOS driver for USBVision (Nogatech) TV tuners</h1>
5
6<h2>Introduction</h2>
7<p>This driver is designed to support USBVision (Nogatech) TV Tuners. Tested with:</p>
8
9<table border=1><tbody><tr>
10<td><b>Name</b></td><td><b>Vendor ID</b></td><td><b>Product ID</b></td>
11</tr><tr>
12<td>Hauppauge WinTV FM</td><td>0x0573</td><td>0x4d31</td>
13</tr></tbody></table>
14
15<table><tbody><tr><td>
16<b><font color="#00ff00">NOTE that</font></b>
17</td><td>
18I have one small request for you - if you tried this driver and it works -
19PLEASE e-mail me the information about your USB TV Tuner and results of your
20experiments. This information is very interesting for me and helps in improvement
21this driver! Thank you for co-operation!
22</td></tr><tr><td>
23<b><font color="#00ff00">NOTE that</font></b>
24</td><td>
25If you definetily have the some kind of USB TV Tuner but this driver didn't
26help you - see section "Unknown devices" below for instructions.
27</td></tr><tbody><table>
28
29<table><tbody><tr><td>
30<b><font color="#00ff00">NOTE that</font></b>
31</td><td>
32If your computer has the OHCI-compatible USB hardware you are out of luck. This hardware is not
33supported by non-Dan0-like versions. See the <a href="#patches">BeOS.USB.patches</a> vor details and
34solutions.
35</td></tr><tbody><table>
36
37<b>What's new:</b>
38<table border=1 ><tbody><tr><td>
39<b>Version:</b>
40</td><td>
41<b>History:</b>
42</td></tr><tr><td>
430.1.0-dev-0
44</td><td>
45very first "development" release.
46</td></tr><tbody><table>
47
48
49<h2>1. Installation</h2>
50<ul>
51<li>Run install.sh
52<li>If all is OK ... //TODO:
53<li>If something goes wrong ... //TODO:
54</ul>
55<h2>2. Uninstallation</h2>
56<ul>
57<li>Run uninstall.sh
58</ul>
59
60<h2>3. Problems solving</h2>
61<ul>
62<li> If this driver crash your system - reboot and press "Space" during load. In boot menu select
63 "Disable user add-ons" and continue boot. Uninstall driver and reboot again into normal mode.
64 Write me a e-mail about this problem.
65</ul>
66<h2>4. "Unknown" devices</h2>
67<a name="usbcommander"></a>
68 If you have something, that looks like USB TV tuner and tried it with
69 this driver but have no success - download <a href="http://www.zharik.host.sk/prahramy/usb_dev_info.zip">
70 usb device info tool</a> and use it to get required information.
71<ul>
72<li>Unplug all USB devices and hubs from your PC.
73<li>Go into Terminal and run the following command:
74<strong> ls -alR /dev/bus/usb</strong>
75 You should see something like this:
76<pre>
77$ ls -alR /dev/bus/usb/
78/dev/bus/usb:
79total 0
80drw-r--r-- 1 walther users 0 May 31 23:16 .
81drw-r--r-- 1 walther users 0 Jun 1 2003 ..
82drw-r--r-- 1 walther users 0 May 31 23:16 0
83drw-r--r-- 1 walther users 0 May 31 23:16 1
84crw-r--r-- 1 walther users 0, 0 May 31 23:16 unload
85
86/dev/bus/usb/0:
87total 0
88drw-r--r-- 1 walther users 0 May 31 23:16 .
89drw-r--r-- 1 walther users 0 May 31 23:16 ..
90crw-r--r-- 1 walther users 0, 0 May 31 23:16 hub
91
92/dev/bus/usb/1:
93total 0
94drw-r--r-- 1 walther users 0 May 31 23:16 .
95drw-r--r-- 1 walther users 0 May 31 23:16 ..
96crw-r--r-- 1 walther users 0, 0 May 31 23:16 hub
97</pre>
98
99<li> Note this information.
100<li> Now plug your USB TV tuner into PC and run <strong>ls -alR /dev/bus/usb/</strong> again.
101You'll get something slightly different:
102<pre>
103$ ls -alR /dev/bus/usb/
104/dev/bus/usb:
105total 0
106drw-r--r-- 1 walther users 0 May 31 23:16 .
107drw-r--r-- 1 walther users 0 Jun 1 2003 ..
108drw-r--r-- 1 walther users 0 May 31 23:16 0
109drw-r--r-- 1 walther users 0 May 31 23:16 1
110crw-r--r-- 1 walther users 0, 0 May 31 23:16 unload
111
112/dev/bus/usb/0:
113total 0
114drw-r--r-- 1 walther users 0 May 31 23:16 .
115drw-r--r-- 1 walther users 0 May 31 23:16 ..
116<blink>crw-r--r-- 1 walther users 0, 0 May 31 23:17 1</blink>
117crw-r--r-- 1 walther users 0, 0 May 31 23:16 hub
118
119/dev/bus/usb/1:
120total 0
121drw-r--r-- 1 walther users 0 May 31 23:16 .
122drw-r--r-- 1 walther users 0 May 31 23:16 ..
123crw-r--r-- 1 walther users 0, 0 May 31 23:16 hub
124</pre>
125
126$
127<li> Compare this results with previous one and look for file,
128that appeared. This file is your USB TV tuner.
129<li> Unpack downloaded usb_dev_info command and run it with full path to file appeared in
130the second listing. For my sample I should run:
131usb_dev_info /dev/bus/usb/0/1
132I'll get the following:
133<pre>
134$ usb_dev_info /dev/bus/usb/0/1
135[Device]
136Class .................. 0
137Subclass ............... 0
138Protocol ............... 0
139Vendor ID .............. 0x0573
140Product ID ............. 0x4d31
141Version ................ 0x0100
142Manufacturer String .... "NT"
143Product String ......... ""
144Serial Number .......... ""
145 [Configuration 0]
146 [Interface 0]
147 Class .............. 0
148 Subclass ........... 0
149 Protocol ........... 0
150 [Endpoint 0]
151 MaxPacketSize .... 8
152 Interval ......... 1
153 Direction ........ Input
154 [Endpoint 1]
155 MaxPacketSize .... 0
156 Interval ......... 1
157 Type ............. Isochronous
158 Direction ........ Output
159 [Configuration 1]
160 [Interface 0]
161 Class .............. 0
162 Subclass ........... 0
163 Protocol ........... 0
164 [Endpoint 0]
165 MaxPacketSize .... 8
166 Interval ......... 1
167 Direction ........ Input
168 [Endpoint 1]
169 MaxPacketSize .... 0
170 Interval ......... 1
171 Type ............. Isochronous
172 Direction ........ Output
173 [Endpoint 2]
174 MaxPacketSize .... 0
175 Interval ......... 1
176 Type ............. Isochronous
177 Direction ........ Input
178 [Configuration 2]
179 [Interface 0]
180 Class .............. 0
181 Subclass ........... 0
182 Protocol ........... 0
183 [Endpoint 0]
184 MaxPacketSize .... 8
185 Interval ......... 1
186 Direction ........ Input
187 [Endpoint 1]
188 MaxPacketSize .... 0
189 Interval ......... 1
190 Type ............. Isochronous
191 Direction ........ Output
192 [Endpoint 2]
193 MaxPacketSize .... 64
194 Interval ......... 1
195 Type ............. Bulk
196 Direction ........ Output
197 [Configuration 3]
198 [Interface 0]
199 Class .............. 0
200 Subclass ........... 0
201 Protocol ........... 0
202 [Endpoint 0]
203 MaxPacketSize .... 8
204 Interval ......... 1
205 Direction ........ Input
206 [Endpoint 1]
207 MaxPacketSize .... 0
208 Interval ......... 1
209 Type ............. Isochronous
210 Direction ........ Output
211 [Endpoint 2]
212 MaxPacketSize .... 0
213 Interval ......... 1
214 Type ............. Isochronous
215 Direction ........ Input
216 [Endpoint 3]
217 MaxPacketSize .... 64
218 Interval ......... 1
219 Type ............. Bulk
220 Direction ........ Output
221</pre>
222<li> Send this information to me with some additional words about your device.
223</ul>
224
225<h2>What is "BeOS.USB.patches"?</h2>
226<a name="patches"></a>
227All know that "classical" BeOS R5 don't works on OHCI USB hardware. But some time ago on one well-known
228BeOS file-sharing network appeared patches for plain R5. Those patches allows to work with OHCI
229hardware under this system version. Looks like it is some part of Dan0 or other "leaked" versions.
230There are 3 patches in BeOS.USB.patches.zip:
231<p>1. beos-usb-patch,
232<p>2. beos-usb.modem-patch,
233<p>3. beos-usb.modem-patch.sm.
234<p> You need the first one to make your OHCI hardware working under R5. Install it and proceed with this
235driver. Good luck!
236
237
238<p><b><a href="mailto:imker@gmx.li">Siarzuk Zharski <imker@gmx.li></a></b>
239<p><a href="http://www.zharik.host.sk/">http://www.zharik.host.sk/</a>
240</body></html>