On Wednesday 23 November 2005 14:54, Michael Krufky wrote:GREAT! ... So then Adrian's patch with my ACK should be applied, in addition to a similar patch for saa7134-dvb ... I'd like to try Sam's method on my machine... if it works, then I will send in a new patch on Friday.
Gene Heskett wrote:Yes, it fixes that just fine.
On Wednesday 23 November 2005 14:17, Michael Krufky wrote:I'm sorry -- I should have been clearer... It fixes the following error
f it fixes Gene's problem (a quick glance at his emails suggests thatRead further Michael, it still takes a _cold_ reboot to 126.96.36.199 to
it does) then:
Gene Heskett wrote:
WARNING:/lib/modules/2.6.15-rc2/kernel/drivers/media/video/cx88/cx88-About the cold reboot needed for 188.8.131.52, well, that is completely
dvb .ko needs unknown symbol nxt200x_attach.
First, does the patch fix the unknown symbol error? If so, then the
patch is correct.
More than likely, I would assume that the issue has something to do with some code inside nxt200x.c that makes some additional devices visible on the i2c bus... This should only affect devices that use nxt200x module, but perhaps there is something going on that is causing interference on the i2c bus of your card? This is just a guess.... Results from your cvs test will show us some better information.Moving on........Neither do I. But as a tv engineer with 50+ years of experience, the
Kirk Lapray wrote both OR51132 and NXT200X frontend modules (cc added)
First off, Gene, I am still under the impression that both v4l and dvb
subsystems are broken under 2.6.15 due to the memory bugs... I don't
know if Hugh Dickins fixed those yet or not.
general appearance is if the antenna cable has been disconnected and
held about 2" away from the f-59 connector when a hot reboot is done. The audio in both cases sounds like its a station 300 miles away when
the atmospherics are behaving themselves.
Link to wiki-howto on linuxtv.org provided below.Please try to build merged v4l+dvb cvs trees against your 184.108.40.206And how & where do I obtain that?
kernel, and tell me if you are having the same problems. If you are
indeed having the same problem, then it confirms that something in the
nxt200x module is causing problems in the OR51132 module.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^Kirk, are you able to use both modules together using both pcHDTV and
ATI HDTV Wonder PCI cx88 boards simultaneously without causing any
Once again, Gene, please follow the tree-merge instructions located at:
I'll give this a shot and advise on the results.I'll keep my email open...
Please let me know if the problem persists. If the problem is gone,
then nxt200x is a red herring.