Re: Siano subsystem (DAB/DMB support) library for linux?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





--- On Sun, 1/18/09, BOUWSMA Barry <freebeer.bouwsma@xxxxxxxxx> wrote:

> From: BOUWSMA Barry <freebeer.bouwsma@xxxxxxxxx>
> Subject: Re:  Siano subsystem (DAB/DMB support) library for linux?
> To: urishk@xxxxxxxxx
> Cc: "Ståle Helleberg / drc.no" <staale@xxxxxx>
> Date: Sunday, January 18, 2009, 2:29 PM
> An update.  You will see what I fool I am.
> 
> On Sun, 18 Jan 2009, BOUWSMA Barry wrote:
> 
> > cd /dev && mknod -m 766 /dev/mdtvctrl c
> $SMSCHAR $(($SMSMINOR + 0))
> > cd /dev && mknod -m 766 /dev/mdtv1 c $SMSCHAR
> $(($SMSMINOR + 1))
> 
> You know, it might help if I actually looked at the files
> I'm
> hacking on, instead of blindly assuming they work like
> `MAKEDEV'
> and create the node in the current directory  :-)
> 
> Nonetheless, when I chose to migrate from major 251 to 249,
> I decided I could hide my ignorance by an `rm' like
> so...
> 
> rm /dev/mdtvctrl && mknod -m 766 /dev/mdtvctrl c
> $SMSCHAR $(($SMSMINOR + 0))
> rm /dev/mdtv1 && mknod -m 766 /dev/mdtv1 c $SMSCHAR
> $(($SMSMINOR + 1))
> 
> 
> > > I'm not quite that far yet, as I may have
> some further
> > > hardware debugging to do -- plus I will learn far
> more from
> > 
> > It was not hardware debugging needed, so it seems.  On
> the
> 
> Or...  was it?  Not only with major 249 on the newer build,
> but now, again with 249 on my notebook, I also see success.
> 
> Could it be that the USB device into which I plugged the
> TerraTec Piranha caused the problems?  Maybe, because into
> a different USB hub, I have success on the notebook...
> 
> Tuning into a frequency
> Kenneth, the frequency is  227360000
> Esemble Info Result
> Well, no problems there
> Tuning...
> Esemble Info Result
> EID: 16385 with 12 services 'SRG SSR D01     '
> Get Combined Components result
> Found 12 services...
> 
> Service: 0 - DRS 1
> 
> 
> > on the other machine.  If so, I'll complain loudly
> to Uri
> > that the Siano binary library seems to have major 251
> hardcoded
> > somewhere within, rather than the device names linked
> by the
> > script, or some similar problem.
> 
> Uri, please accept my apologies.  This was *not* the
> problem,
> the library works fine with the device nodes pointed to by
> the
> script:
> beer@ralph:/usr/local/src/mini_dab$ ls -lart /dev/mdtv*
> crwxrw-rw- 1 root root 249,  0 Jan 17 18:52 /dev/mdtvctrl
> crwxrw-rw- 1 root root 249,  1 Jan 17 18:52 /dev/mdtv1
> 
> Sorry to have made any false accusation.  It just seemed
> to me that it could be one of the many possibilities that
> might have been at fault.
> 
> 
> Now, the interesting thing is that a USB2 DVB-S connected
> through this same hub delivered streams that were corrupt
> every few minutes, while the same device connected to a
> different hub has been delivering flawless streams.  Now
> I need to check whether the USB1 Piranha can deliver the
> clean streams, or if again, cheap hardware will cause me
> grief...
> 
> 
> thanks again,
> now back to play
> barry bouwsma

Cool, I'm just CC the ML
I get questions (sometimes the exact same questions) from various of people. Lets use the ML to sync all...

Uri


      

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@xxxxxxxxxxxxxxx
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


[Index of Archives]     [Linux Media]     [Video 4 Linux]     [Asterisk]     [Samba]     [Xorg]     [Xfree86]     [Linux USB]

  Powered by Linux