dst_ca_open:Device opened [ffff81001c0ffc80] dst_ca_ioctl: Sending message ca_send_message ca_send_message:Command=[0x9f8032] Command = SEND_CA_PMT asn_1_decode: Length field=[12] asn_1_decode: Length=[12] ca_set_pmt: CA Message length=[18] ca_set_pmt: RAW CA Message with tag and length: Offset=[ 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13 14 15 ] String=[ 9f 80 32 12 03 05 e4 01 10 06 01 09 04 0b 00 e5 05 02 e2 02 f0 05 ] ca_set_pmt: ASN.1: Offset=[ 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10 11 ] String=[ 03 05 e4 01 10 06 01 09 04 0b 00 e5 05 02 e2 02 f0 05 ] ca_set_pmt: Program Header(BUF) Offset=[ 00 01 02 03 04 05 ] String=[ 03 05 e4 01 10 06 ] ca_set_pmt: Copying Program header copy_string: Copying [ 12 03 05 e4 01 10] ca_set_pmt: Probably an ASIC bug !!! Offset=[ 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10 11 12 ] String=[ 19 40 03 00 03 12 00 12 03 05 e4 01 10 00 00 00 00 00 45 ] ca_set_pmt: Program Header(HW), Count=[6] Offset=[ 00 01 02 03 04 05 06 07 08 09 0a 0b 0c ] String=[ 19 40 03 00 03 12 00 12 03 05 e4 01 11 ] ca_set_pmt: Program info length=[06] copy_string: Copying [ 01 09 04 0b 00 e5 05] ca_set_pmt: Stream Header copy_string: Copying [ 05 02 e2 02 f0] Offset=[ 14 15 16 17 18 ] String=[ 05 02 e2 02 f0 ] ca_set_pmt: ES Info length bytes = [f0 05] ca_set_pmt: ES info length=[05] ca_set_pmt: buf_offset+1 [p_ca_message->msg[buf_offset+1]]=16 [00] ca_set_pmt: buf_offset+2 [p_ca_message->msg[buf_offset+2]]=17 [00] ca_set_pmt: buf_offset+3 [p_ca_message->msg[buf_offset+3]]=18 [00] Offset=[ 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13 14 15 16 17 18 19 ] String=[ 19 40 03 00 03 12 00 12 03 05 e4 01 11 01 09 04 0b 00 e5 05 05 02 e2 02 f0 a1 ] dst_put_ci: Put Command write_to_8820: DST-CI Command succes. ca_send_message: -->CA_PMT Success ! dst_ca_release:Device closed. This is my latest output, but it's still not good. Any idea? Oivind On 6/24/05, Manu Abraham <manu@xxxxxxxxxxx> wrote: > Oivind wrote: > > I see. So the p_ca_message argument is the EN50221 message and > > hw_buffer is filled with the twinhan hardware message. > > > > Yes the userspace is responsible to send in a proper EN50221 message, > the driver gets this message in p_ca_message > > The hardware does not take in an EN50221 message, so to modify it, the > message is copied to hw_buffer and is modified there.. > > Once things are okay, it is written to hardware .. > > > Are the logs from previous mail making any sense? > > > > Yes, i have posted a reply on that too .. I think the offset is wrong > and the lengths need to be initialize to 0 too, as a precautionary case > .. in the case if the shifts are not equal to the number of bit positions. > > In the library this does not matter, as those shifts exactly matches the > fields and the error is avoided there .. Else we would have been > debugging in the library .. Anyway hope to catch some bugs there too .. > > > Manu > > _______________________________________________ > > linux-dvb@xxxxxxxxxxx > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >
