Re: Dear TV card experts - I need you help

2015-12-03 Thread Another Sillyname
It occurs to me that someone who is so cavalier with not paying legal
royalties would be pretty unlikely to pay bills for the advice and
support.

On 3 December 2015 at 16:56, Mr Andersson  wrote:
> Steven, I appreciate your concern.
>
> But the legal parts are of no concern to us, and we are already aware
> of potential legal complexities, especially in western countries, but
> fortunately there are many other countries outside of the western
> hemisphere. There is also plenty of internet based providers that
> already offers this, albeit with a less than ideal quality of service.
> So consider that a non issue for now.
>
> I'd like to keep this discussion on the technological aspects.
>
>
>
> On Thu, Dec 3, 2015 at 3:29 PM, Steven Toth  wrote:
>> (Please don't reply privately, keep all correspondence to this mailing list.)
>>
>>> Let me start of by presenting myself. I am a Computer Engineer and a
>>> business man, looking to launch a service where TV channels from
>>> primarily satellites will be made available to the public.
>>
>> You and 2 million other entrepreneurs, past, present and future.
>>
>> In most western countries, It's illegal to randomly redistribute
>> television content unless you have specific paid-for negotiated rights
>> with the content providers and the broadcasters. You should start by
>> studying the law and contacting the content owners, negotiating
>> contracts and seeking permission.
>>
>> Solve the legal contract / redistribution first, then the technology
>> to make it happen is easily available.
>>
>> --
>> Steven Toth - Kernel Labs
>> http://www.kernellabs.com
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Elgato Eye TV Deluxe V2 supported?

2015-10-11 Thread Another Sillyname
I realise this is from over a year ago but I ended up putting it to
one side till the kernel 'caught up' as it were.

Looking at github/torvalds/linux/tree/master/drivers/media/dvb-frontends
it looks like the as102 support is now in mainline and indeed looking
at staging there's no reference at all to any as102 devices.

I've just installed FC22 Kernel 4-1-10-200 x86_64 onto a box and
installed the required firmware files into /lib/firmware in the hope
the device would now workunfortunately plugging it in gives me
exactly the same as early last year.no firmware load even though
dmesg sees the device installed.

Am I still stuck with potentially having to compile a custom kernel to
support this device under Fedora (which isn't an option due to SELinux
issues it would present elsewhere).

Thanks in advance.

On 2 May 2014 at 14:52, Another Sillyname <anothersn...@googlemail.com> wrote:
> OK, I realise I should be able to work this outbut I'm stuck and
> no matter how much I read I've developed a mental block (think of it
> as the computing version of writers block).
>
> I use Fedora as my primary OS, currently Fedora 20 latest kernel 3.13
>
> I need to keep using this kernel as I use SELinux for a couple of
> things on my server and compiling a vanilla kernel and patching
> SELinux in is just way too messy
>
> As the V4L-DVB Media_Tree is NOT included in the kernel-devel version
> of the Fedora kernel it requires a complete kernel compile to download
> the required media tree, however I can't then get the V4L-DVB media
> tree from git to patch against the Fedora (uncompiled) kernel prior to
> compilation, I've installed all the tools required (I have built a few
> kernels before when I needed to) but I've just hit a mental wall......
>
> Help!!
>
>
>
> On 25 April 2014 20:06, Another Sillyname <anothersn...@googlemail.com> wrote:
>> OK, I'm not a coder these days but I'll look and see if I can work it out.
>>
>> Regards and have a good weekend.
>>
>> Tony
>>
>> On 25 April 2014 19:54, Devin Heitmueller <dheitmuel...@kernellabs.com> 
>> wrote:
>>>> Is the as102 tree ever likely to go mainline?
>>>
>>> The only reason it's in staging is because it doesn't meet the coding
>>> standards (i.e. whitespace, variable naming, etc).  Somebody needs to
>>> come along and expend the energy to satisfy the whitespace gods.
>>>
>>> Seems like a fantastically stupid reason to keep a working driver out
>>> of the mainline, but that's just my opinion.
>>>
>>> Devin
>>>
>>> --
>>> Devin J. Heitmueller - Kernel Labs
>>> http://www.kernellabs.com
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: DVB-T2 PCIe vs DVB-S2

2015-05-26 Thread Another Sillyname
TBS cards.PCIe x1 used them for years in both DVB-T2 and DVB-S2
formats..never had a problem (except the drivers were cr*p a fair
few years back).would not hesitate to recommend them to anyone.

Currently have quad tuners of both running in a server that hasn't
needed a reboot in 524 days and counting.

On 26 May 2015 at 20:10, Olli Salonen olli.salo...@iki.fi wrote:
 There are indeed a few DVB-T2 PCIe cards that are supported (DVBSky
 T9580, T980C, T982C, TechnoTrend CT2-4500 CI, Hauppauge HVR-2205,
 Hauppauge HVR-5525 at least come to my mind). PCTV 290e is a USB
 device, not PCIe. In the wiki there's currently some issue with the
 filtering when it comes to the tables - that's why every PCIe device
 is printed instead of just the DVB-T2 supporting ones.

 As Jemma points out, the application should be clever enough to tell
 the driver that DVB-T2 delivery system is wanted. For the cxd2820r
 driver (PCTV 290e) Antti made the fudge, but has decided not to
 implement it in the Si2168 driver (reasoning, to which I
 wholeheartedly agree, is here:
 http://blog.palosaari.fi/2014/09/linux-dvb-t2-tuning-problems.html ).

 When it comes to PVR backends, at least tvheadend supports DVBv5 fully
 - I don't have a clear picture of other backends.

 Cheers,
 -olli

 On 26 May 2015 at 17:44, Jemma Denson jden...@gmail.com wrote:
 On 26/05/15 08:53, Ian Campbell wrote:

 Hello,

 I'm looking to get a DVB-T2 tuner card to add UK Freeview HD to my
 mythtv box.

 Looking at http://linuxtv.org/wiki/index.php/DVB-T2_PCIe_Cards is seems
 that many (the majority even) of the cards there are actually DVB-S2.

 Is this a mistake or is there something I don't know (like maybe S2 is
 compatible with T2)?

 Thanks,
 Ian.


 That's a mistake - I don't recall that table looking like that when I was
 looking for one, and S2 is quite definitely not compatible with T2!

 I can confirm that the 290e works out of the box with myth with very few
 problems, however it's well out of production now and you might not be after
 a USB device. I'm not sure anything else would work without some hacking
 because last I heard myth doesn't do T2 the proper way using DVBv5 yet, and
 afaik only the 290e driver has a fudge to allow T2 on v3.
 (http://lists.mythtv.org/pipermail/mythtv-users/2014-November/374441.html
 and https://code.mythtv.org/trac/ticket/12342)


 Jemma.
 --
 To unsubscribe from this list: send the line unsubscribe linux-media in
 the body of a message to majord...@vger.kernel.org
 More majordomo info at  http://vger.kernel.org/majordomo-info.html
 --
 To unsubscribe from this list: send the line unsubscribe linux-media in
 the body of a message to majord...@vger.kernel.org
 More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Elgato Eye TV Deluxe V2 supported?

2014-05-02 Thread Another Sillyname
OK, I realise I should be able to work this outbut I'm stuck and
no matter how much I read I've developed a mental block (think of it
as the computing version of writers block).

I use Fedora as my primary OS, currently Fedora 20 latest kernel 3.13

I need to keep using this kernel as I use SELinux for a couple of
things on my server and compiling a vanilla kernel and patching
SELinux in is just way too messy

As the V4L-DVB Media_Tree is NOT included in the kernel-devel version
of the Fedora kernel it requires a complete kernel compile to download
the required media tree, however I can't then get the V4L-DVB media
tree from git to patch against the Fedora (uncompiled) kernel prior to
compilation, I've installed all the tools required (I have built a few
kernels before when I needed to) but I've just hit a mental wall..

Help!!



On 25 April 2014 20:06, Another Sillyname anothersn...@googlemail.com wrote:
 OK, I'm not a coder these days but I'll look and see if I can work it out.

 Regards and have a good weekend.

 Tony

 On 25 April 2014 19:54, Devin Heitmueller dheitmuel...@kernellabs.com wrote:
 Is the as102 tree ever likely to go mainline?

 The only reason it's in staging is because it doesn't meet the coding
 standards (i.e. whitespace, variable naming, etc).  Somebody needs to
 come along and expend the energy to satisfy the whitespace gods.

 Seems like a fantastically stupid reason to keep a working driver out
 of the mainline, but that's just my opinion.

 Devin

 --
 Devin J. Heitmueller - Kernel Labs
 http://www.kernellabs.com
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Elgato Eye TV Deluxe V2 supported?

2014-04-25 Thread Another Sillyname
I have an Elgato Eye TV V2 USB device  USB ID 0fd9:002c which reading here

https://github.com/mirrors/linux-2.6/blob/master/drivers/staging/media/as102/as102_usb_drv.h

Looks like it should be supported (it looks like Devin wrote some of
the code?)..it gets recognised in dmesg and indeed lsusb sees it,
but no firmware is loaded (I have the required as102 files in
/lib/firmware) and in effect it never 'initialises'.

Has something broken since kernel 2.6 (I'm currently running 3.13.10)
or did it never work?

Googling around pops up a load of contradictory information whether it
works or not.

lsusb gives me this...

lsusb -v -d 0fd9:002c

Bus 002 Device 004: ID 0fd9:002c Elgato Systems GmbH EyeTV DTT Deluxe v2
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass  255 Vendor Specific Class
  bDeviceSubClass   255 Vendor Specific Subclass
  bDeviceProtocol   255 Vendor Specific Protocol
  bMaxPacketSize064
  idVendor   0x0fd9 Elgato Systems GmbH
  idProduct  0x002c EyeTV DTT Deluxe v2
  bcdDevice1.00
  iManufacturer   1 Elgato
  iProduct2 EyeTV DTT Dlx
  iSerial 3 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   39
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0
bmAttributes 0x80
  (Bus Powered)
MaxPower  300mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass255 Vendor Specific Subclass
  bInterfaceProtocol255 Vendor Specific Protocol
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01  EP 1 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83  EP 3 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
Device Qualifier (for other device speed):
  bLength10
  bDescriptorType 6
  bcdUSB   2.00
  bDeviceClass  255 Vendor Specific Class
  bDeviceSubClass   255 Vendor Specific Subclass
  bDeviceProtocol   255 Vendor Specific Protocol
  bMaxPacketSize064
  bNumConfigurations  1
Device Status: 0x
  (Bus Powered)



lsusb ends



Any ideas?

Thanks in advance.

Tony
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Elgato Eye TV Deluxe V2 supported?

2014-04-25 Thread Another Sillyname
Thanks Devin

Is the as102 tree ever likely to go mainline?

Regards

Tony

On 25 April 2014 19:40, Devin Heitmueller dheitmuel...@kernellabs.com wrote:
 On Fri, Apr 25, 2014 at 2:31 PM, Another Sillyname
 anothersn...@googlemail.com wrote:
 I have an Elgato Eye TV V2 USB device  USB ID 0fd9:002c which reading 
 here

 https://github.com/mirrors/linux-2.6/blob/master/drivers/staging/media/as102/as102_usb_drv.h

 Looks like it should be supported (it looks like Devin wrote some of
 the code?)..it gets recognised in dmesg and indeed lsusb sees it,
 but no firmware is loaded (I have the required as102 files in
 /lib/firmware) and in effect it never 'initialises'.

 Hi Tony,

 Sorry, I saw your email yesterday but forgot to reply.  The issue is
 that the as102 is still in staging, so it won't appear in mainline
 kernels by default.  You would need to install the media_build tree,
 run make menuconfig, enable staging drivers and then enable the
 as102 bridge.

 The messages you are seeing in dmesg and lsusb are just the kernel
 finding the hardware at a USB level - these messages will appear
 whether there is a driver or not for the actual device.

 Devin

 --
 Devin J. Heitmueller - Kernel Labs
 http://www.kernellabs.com
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Elgato Eye TV Deluxe V2 supported?

2014-04-25 Thread Another Sillyname
OK, I'm not a coder these days but I'll look and see if I can work it out.

Regards and have a good weekend.

Tony

On 25 April 2014 19:54, Devin Heitmueller dheitmuel...@kernellabs.com wrote:
 Is the as102 tree ever likely to go mainline?

 The only reason it's in staging is because it doesn't meet the coding
 standards (i.e. whitespace, variable naming, etc).  Somebody needs to
 come along and expend the energy to satisfy the whitespace gods.

 Seems like a fantastically stupid reason to keep a working driver out
 of the mainline, but that's just my opinion.

 Devin

 --
 Devin J. Heitmueller - Kernel Labs
 http://www.kernellabs.com
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Elgato DTT Deluxe V2

2013-04-23 Thread Another Sillyname
I recently picked up one of these very cheap and am trying to load it into 'nix.

According to this

http://www.linuxtv.org/wiki/index.php/Elgato_EyeTV_DTT_deluxe_v2

It should be recognised and load, and indeed when plugged in dmesg
correctly reports it being detected and lsusb sees the device and the
correctly reports the device ID.

However there's no DVB section loading and I'm not sure why.

I've copied the two .hex files to firmware and dmesg is not reporting
any other outstanding requirements, however it's just not
partying

Installed into a windows machine the drivers load and it reports OK
(it's not tuning but I'm pretty sure that's a location issue at the
moment).

any ideas anyone?


section from dmesg

[88238.662053] usb 2-1: new high-speed USB device number 6 using ehci-pci
[88238.777869] usb 2-1: New USB device found, idVendor=0fd9, idProduct=002c
[88238.777881] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[88238.777888] usb 2-1: Product: EyeTV DTT Dlx
[88238.777895] usb 2-1: Manufacturer: Elgato
[88238.777902] usb 2-1: SerialNumber: xx
[88554.865760] usb 2-1: USB disconnect, device number 6
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Problems with Hauppauge Nova TD Dual Tuner USB Stick and Mythtv, no problems in Windows!

2013-03-28 Thread Another Sillyname
I'm posting this on both the Mythtv dev and Linux Media lists as I'm
not sure where the problem sits, my inclination is it's probably in
myth's tuning and I'll explaing why shortly.

I recently built a system for a friend of mine, using Fedora 18 x64.

Clean build on a DFI Mini ITX P55-T36 system with a decent sized hard
disk and 4GB of memory..plenty to run a mythTV backend.

The tuners were Hauppauge Nova TD Dual Tuner USB Sticks, USB reference
2040:9580 IIRC.

His place has a masthead antenna and no matter what I did I could not
get these things to tune properly.

LNA On, LNA Off, Rooftop Antenna, Mini Antenna supplied with Stick,
Attenuators in and out, I've messed around with every variation for
about 3 weeks now and been unable to get a proper signal on all the
muxes no matter what I do.  He's in East London on the border of the
City near Aldgate.  His internal antenna feed to the TV is perfect but
I cannot get it behave using Linux no matter what configuration I try.

In desperation I finally tried something different today, took in
another hard disk and did a clean build of Windows 7 Ultimate x64,
didn't touch anything else, installed the latest Hauppauge drivers
from their website and used Win7Ult own Media for TV
software.every channel tuned in straight away no problem, except
some borderline signal issues with the Film4 mux.

Now this got me thinking back to when I first plugged the USB stick in
to a Mint Live CD, I tested it using either VLC or Kaffeine (I honest
can't rmember which) and I could get tuning on pretty much all the
channels straight away.

As the device isn't supported properly in Myth/Linux I had to compile
the V4L drivers, I'm running Fedora 18 x64 Kernel 3.8.4-202 and V4L
compiled last night, using Mythtv from the RPMFusion repos so
26.0.7--18.

If anyone can suggest anything I'm receptive to try it but honestly I
think something is broken in either the mythtv tuning code or the
interaction between the tuners and the V4L drivers.

If anyone wants specific info let me know what you need.

Tony
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: media_build build is broken

2013-03-25 Thread Another Sillyname
Sorry feeling a bit thick now...

Never done a rollback using git and thought it would be
straightforward as subversion, however I hadn't realised that the
build is actually pulling the latest head version as part of the build
itself.

Had a play around trying to use git reset --hard xxx to get to a
previous version on 8th March however my command of git is somewhat
limited and although I've googled I can't see how to achieve this
easily.

If someone on the list could let me know a quick way of going back to
99fa97227ee3f4728d16c0db214637e2b61fa128 on the 8th March I'd be
grateful.

Regards

On 25 March 2013 18:47, Another Sillyname anothersn...@googlemail.com wrote:
 Sorry feeling a bit thick now...

 Never done a rollback using git and thought it would be
 straightforward as subversion, however I hadn't realised that the
 build is actually pulling the latest head version as part of the build
 itself.

 Had a play around trying to use git reset --hard xxx to get to a
 previous version on 8th March however my command of git is somewhat
 limited and although I've googled I can't see how to achieve this
 easily.

 If someone on the list could let me know a quick way of going back to
 99fa97227ee3f4728d16c0db214637e2b61fa128 on the 8th March I'd be
 grateful.

 Regards



 On 25 March 2013 15:17, Hans Verkuil hverk...@xs4all.nl wrote:
 On Mon March 25 2013 16:14:26 Another Sillyname wrote:
 Cripes that's hilarious.

 I was just about to post this as well, Fed 18 x86_64 blah blah blah.

 Hans, how far back do I need to go on git to get a good build version
 please, I'm building a new box today and only have a few days to test
 before buggering off for a few weeks.

 It was working a week ago.

 Regards,

 Hans


 Thanks

 On 25 March 2013 14:38, Hans Verkuil hverk...@xs4all.nl wrote:
  On Mon March 25 2013 15:33:08 Anthony Horton wrote:
  Apologies is this is already known about but I couldn't find anything
  when I searched.
 
  The media_build tree appears to be currently broken, at least for my
  build environment (Fedora 18, gcc 4.7.2, 3.8.4-202.fc18.x86_64
  kernel).
 
  Lots of code has been merged in the past few days, and this is still
  ongoing. Once things have settled a bit I'll work on fixing media_build.
  It should be fixed this week, likely sooner rather than later.
 
  Regards,
 
  Hans
 
 
  $ git clone git://linuxtv.org/media_build.git
  $ cd media_build/
  $./build
  Checking if the needed tools for Fedora release 18 (Spherical Cow) are 
  available
  Needed package dependencies are met.
  ...
  lots of output
  ...
CC [M]  /home/username/build/v4l/media_build/v4l/mem2mem_testdev.o
CC [M]  /home/username/build/v4l/media_build/v4l/sh_veu.o
  /home/username/build/v4l/media_build/v4l/sh_veu.c: In function 
  'sh_veu_probe':
  /home/username/build/v4l/media_build/v4l/sh_veu.c:1168:2: error:
  implicit declaration of function 'devm_ioremap_resource'
  [-Werror=implicit-function-declaration]
  /home/username/build/v4l/media_build/v4l/sh_veu.c:1168:12: warning:
  assignment makes pointer from integer without a cast [enabled by
  default]
  /home/username/build/v4l/media_build/v4l/sh_veu.c: At top level:
  /home/username/build/v4l/media_build/v4l/sh_veu.c:1252:1: warning:
  data definition has no type or storage class [enabled by default]
  /home/username/build/v4l/media_build/v4l/sh_veu.c:1252:1: warning:
  type defaults to 'int' in declaration of
  'module_platform_driver_probe' [-Wimplicit-int]
  /home/username/build/v4l/media_build/v4l/sh_veu.c:1252:1: warning:
  parameter names (without types) in function declaration [enabled by
  default]
  /home/username/build/v4l/media_build/v4l/sh_veu.c:1147:12: warning:
  'sh_veu_probe' defined but not used [-Wunused-function]
  /home/username/build/v4l/media_build/v4l/sh_veu.c:1244:41: warning:
  'sh_veu_pdrv' defined but not used [-Wunused-variable]
  cc1: some warnings being treated as errors
  make[3]: *** [/home/username/build/v4l/media_build/v4l/sh_veu.o] Error 1
  make[2]: *** [_module_/home/username/build/v4l/media_build/v4l] Error 2
  make[2]: Leaving directory `/usr/src/kernels/3.8.4-202.fc18.x86_64'
  make[1]: *** [default] Error 2
  make[1]: Leaving directory `/home/username/build/v4l/media_build/v4l'
  make: *** [all] Error 2
  build failed at ./build line 452.
 
  This seems to be a recent regression, I successfully built from
  media_build on another Fedora 18 machine just a couple of weeks ago.
  --
  To unsubscribe from this list: send the line unsubscribe linux-media in
  the body of a message to majord...@vger.kernel.org
  More majordomo info at  http://vger.kernel.org/majordomo-info.html
 
  --
  To unsubscribe from this list: send the line unsubscribe linux-media in
  the body of a message to majord...@vger.kernel.org
  More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message

Blackgold BGT3620 DVB-T2 Dual Tuner PCI-E Card...development?

2011-01-01 Thread Another Sillyname
Hi Guys

Blackgold have just started shipping the BGT3620 Dual Tuner PCI-E
DVB-T2 card, as far as I know this is the first DVB-T2 card actually
shipping.

The link to the page is here.

http://shop.blackgold.tv/BGT3620

Is there any chance of getting some development of a Linux driver underway?

I'd be willing to organise a bounty payment to kick start things if it
would help.

Regards
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [linux-dvb] Help needed

2010-09-07 Thread Another Sillyname
On 7 September 2010 07:33, Jimmy Öhlin jimmy.oh...@artvise.se wrote:
 Hello,



 Hope that you can help me with the following questions.

 I need a dvb-t and dvb-s2 card that work with Common Interface (Swedish
 Boxer and Canal Digital).



 I have looked at different dvb cards but… still not found a DVB-T and DVB-S2
 card that will work under linux with CI support.

 I will use mplayer with ca_zap  as frontend for my dvb application.





 Kind Regards,

 Jimmy Ohlin



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

Are you saying you need a single card with both interfaces?

Are you happy being able to record on only DVB-T or DVB-S2 one at a time?
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


TBS 6980 Dual Tuner PCI-e card.....not in Wiki at all?

2010-05-28 Thread Another Sillyname
Guys

The TBS 6920 PCI-e card is in the Wiki and is a supported card.

The TBS 6980 dual tuner PCI-e card is not in the Wiki at all, is there
a reason for this given they have released a non GPL blob at least?

Also is there a reason that an indicative price for supported cards is
not shown in the wiki?  It would save a load of time rather then
having to search on each card only to find out it's ridiculously
priced at $1000.

Thanks
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: CI USB

2010-04-17 Thread Another Sillyname
On 24 January 2010 09:56, Konstantin Dimitrov kosio.dimit...@gmail.com wrote:
 On Sun, Jan 24, 2010 at 10:54 AM, Konstantin Dimitrov
 kosio.dimit...@gmail.com wrote:
 On Sun, Jan 24, 2010 at 10:12 AM, Manu Abraham abraham.m...@gmail.com 
 wrote:
 On Sun, Jan 24, 2010 at 11:49 AM, Konstantin Dimitrov
 kosio.dimit...@gmail.com wrote:
 On Sun, Jan 24, 2010 at 1:43 AM, Manu Abraham abraham.m...@gmail.com 
 wrote:
 On Sun, Jan 24, 2010 at 1:45 AM, Konstantin Dimitrov
 kosio.dimit...@gmail.com wrote:
 On Sat, Jan 23, 2010 at 1:31 AM, Manu Abraham abraham.m...@gmail.com 
 wrote:
 On Sun, Jan 10, 2010 at 9:21 PM, Ian Wilkinson n...@sgtwilko.f9.co.uk 
 wrote:
 HoP wrote:

 I don't know the details into the USB device, but each of those CAM's
 have bandwidth limits on them and they vary from one CAM to the other.
 Also, there is a limit on the number of simultaneous PID's that which
 you can decrypt.

 Some allow only 1 PID, some allow 3. Those are the basic CAM's for
 home usage.The most expensive CAM's allow a maximum of 24 PID's. But


 You, of course, ment number of descramblers not PIDS because it is 
 evident
 that getting TV service descrambled, you need as minimum 2 PIDS for 
 A/V.

 Anyway, it is very good note. Users, in general, don't know about it.


 If it is using a CI+ plus chip (I heard from someone that it is a CI+
 chip inside) :
 http://www.smardtv.com/index.php?page=ciplus

 After reading the CI+ specifications, I doubt that it can be supported
 under Linux with open source support, without a paired decoder
 hardware or software decoder. A paired open source software decoder
 seems highly unlikely, as the output of the CI+ module is eventually
 an encrypted stream which can be descrambled with the relevant keys.
 The TS is not supposed to be stored on disk, or that's what the whole
 concept is for CI+

 http://www.ci-plus.com/data/ci-plus_overview_v2009-07-06.pdf

 See pages 7, 8 , 12, 15

 It could be possible to pair a software decoder with a key and hence
 under Windows, but under Linux I would really doubt it, if it happens
 to be a CI+ chip

 at least in Windows Hauppage WinTV-CI USB (which is OEM version of
 SmartDTV USB CI) allows you to capture the decrypted stream to your
 hard drive (i've just tested it).


 Maybe it is not CI+ itself in the first place


 so, i can't see a reason why even if it has CI+ chip inside same
 functionally as in Windows can't be provided in Linux if someone
 developed a driver.


 It would be interesting to know what chips the hardware has  ...

 i can confirm the information here:

 * http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-CI

 and it contains:

 * an FX2 from Cypress (CY7C68013A) and a FPGA (Actel Proasic-plus, 
 APA075-F)



 No CI+ in there ... Generic USB bridge with microcontroller and
 possibly a FPGA programmed by Hauppauge themselves, most probably. The

 no, the whole Hauppauge device is actually made by SmartDTV even on
 the board there is a title SmartDTV Rev...

 also, Terratec device is the same as Hauppauge device, they even look the 
 same:

 http://www.terratec.net/en/products/Cinergy_CI_USB_2296.html

 and Terratec driver for Windows says Copyright SmarDTV., which means
 it's made by SmarDTV.

 actually, Terratec driver for Windows is essentially the same as
 Hauppauge one, because firmware extracted from both drivers is the
 same (they update the firmware with driver updates, so matching
 versions of Terratec and Hauppauge driver is needed to check that the
 firmwares are the same).

 bridge would be similar to other DVB USB devices, Application on the
 FPGA would be more or less similar to the one found on general DVB CI
 devices.

 If it's not a Masked FPGA, it would need to load it's instructions
 some place, maybe an EEPROM or maybe from the firmware that you need
 load itself. Some part of the firmware that you load could be partly
 for the microcontroller on the USB bridge as well.

 i believe that 40 A3 firmware requests are for the USB controller

 typo, 40 A0 firmware requests are for the USB controller

 and then the subsequent 40 A3 firmware requests are to load the FPGA
 instructions through the USB controller.



 Manu


 --
 To unsubscribe from this list: send the line unsubscribe linux-media in
 the body of a message to majord...@vger.kernel.org
 More majordomo info at  http://vger.kernel.org/majordomo-info.html


According to this page

http://www.bsc-bvba.be/linux/dvb/

the firmware load problem was solved about a month ago

What is needed in the way of resources to solve this problem?

Regards
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [linux-dvb] Struggling with Astra 2D (Freesat) / Happauage Nova-HD-S2

2009-11-02 Thread Another Sillyname
2009/11/3 TD topper.dog...@googlemail.com:
 On 2009-11-02, Goga777 goga...@bk.ru wrote:
 Приветствую, TD

 you have to use scan-s2
 http://mercurial.intuxication.org/hg/scan-s2

 Hi, and thanks for your quick reply.

 I tried it but no better:
 snip
 initial transponder DVB-S  12692000 V 19532000 1/2 AUTO AUTO
 initial transponder DVB-S2 12692000 V 19532000 1/2 AUTO AUTO
 -- Using DVB-S
 tune to: 11720:hC34S0:S0.0W:29500:
 DVB-S IF freq is 112
 WARNING:  tuning failed!!!
 tune to: 11720:hC34S0:S0.0W:29500: (tuning failed)

 and the channels.conf was no better than before - it didn't include *one* BBC
 channel, for example.


 or

 dvb2010 scan
 http://hg.kewl.org/dvb2010/

 Once I got it working, same:
 Astra 2A/2B/2D/Eurobird 1 (28.2E) 10714 H DVB-S QPSK 22000 5/6 ONID:0 TID:0
 AGC:0% SNR:0%
    Can't tune

 Astra 2A/2B/2D/Eurobird 1 (28.2E) 10729 V DVB-S QPSK 22000 5/6 ONID:0 TID:0
 AGC:0% SNR:0%
    Can't tune

 Where do I go from here?
 --
 TD


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

Are you running myth .21 or .22?
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Steven T. any chance your next 'project' could be.....

2009-10-30 Thread Another Sillyname
A dual tuner PCI-E DVB-S2 card?

A fair few people are probably now trying to move away from legacy
(PCI) kit and at the moment the DVB-S2 PCIe area is quite badly
served.

I realise it's dependant upon your time availability and getting hold
of hardware/information to develop a driver, however if you could keep
it in mind that would be great.

If there's a particular card that catches your eye let me know and
I'll see if I can help sourcing one.

Regards
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Hauppage HVR-2250 Tuning problems

2009-10-26 Thread Another Sillyname
2009/10/26 dan danwalke...@gmail.com:
 I can't seem to get my HVR-2250 (rev. 88061) card to tune any
 channels.  I have Comcast digital cable, and my VIZIO VL370M
 television is able to tune all of the QAM channels, so I know that the
 signal is present and is usable (in theory).  I have tried scanning
 for channels in Mythbuntu 9.10 RC (2.6.31 kernel), with MythTV, scan,
 dvbscan and scte65scan, without finding any channels.  I have tried
 installing the saa7164 drivers from the kernellabs repository and also
 the linuxtv repository, with the same results.

 The channel scanner in MythTV has two bars at the top of the screen to
 indicate signal strength and signal-to-noise ratio, and they both stay
 at 0% during the channel scan.  The scanner will say locked for a
 particular channel, but then it will show a message saying that it
 timed and without finding any channels.  I have already set the
 timeout to the maximum allowed by the software.

 scte65 scan get the closest to giving some kind of output.  I run it
 with this command:

 $ ./scte65scan -f1 -n1 ./us-Cable-Standard-center-frequencies-QAM256 
 channels.conf

 At some point it  gives the following output:

 tuning 74100hz..locked...PID 0x1ffc found
 Collecting data (may take up to 2 minutes)

 but then it basically just hangs indefinitely until I kill it, and
 channels.conf is always empty afterward.

 I do have a couple of errors show up in dmesg, but I'm not sure if
 they're relevant.  Just in case it's helpful, here is the output from
 dmesg.

 [   14.266956] saa7164 driver loaded
 [   14.267518] saa7164 :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 
 16
 [   14.267621] CORE saa7164[0]: subsystem: 0070:8891, board: Hauppauge
 WinTV-HVR2250 [card=7,autodetected]
 [   14.267627] saa7164[0]/0: found at :01:00.0, rev: 129, irq: 16,
 latency: 0, mmio: 0xe400
 [   14.267633] saa7164 :01:00.0: setting latency timer to 64
 [   14.267637] IRQ 16/saa7164[0]: IRQF_DISABLED is not guaranteed on shared 
 IRQs
 [   14.460016] saa7164_downloadfirmware() no first image
 [   14.460029] saa7164_downloadfirmware() Waiting for firmware upload
 (v4l-saa7164-1.0.3.fw)
 [   14.460035] saa7164 :01:00.0: firmware: requesting v4l-saa7164-1.0.3.fw
 [   16.075415] saa7164_downloadfirmware() firmware read 3978608 bytes.
 [   16.075417] saa7164_downloadfirmware() firmware loaded.
 [   16.075425] saa7164_downloadfirmware() SecBootLoader.FileSize = 3978608
 [   16.075431] saa7164_downloadfirmware() FirmwareSize = 0x1fd6
 [   16.075433] saa7164_downloadfirmware() BSLSize = 0x0
 [   16.075434] saa7164_downloadfirmware() Reserved = 0x0
 [   16.075435] saa7164_downloadfirmware() Version = 0x51cc1
 [   23.351830] saa7164_downloadimage() Image downloaded, booting...
 [   23.460015] saa7164_downloadimage() Image booted successfully.
 [   25.840015] saa7164_downloadimage() Image downloaded, booting...
 [   27.260019] saa7164_downloadimage() Image booted successfully.
 [   27.302513] saa7164[0]: Hauppauge eeprom: model=88061
 [   28.539398] saa7164_api_i2c_read() error, ret(2) = 0x13
 [   28.542913] saa7164_api_i2c_read() error, ret(2) = 0x13
 [   28.543201] DVB: registering new adapter (saa7164)
 [   32.148177] DVB: registering new adapter (saa7164)

 I have done some searching online, and that's what led me to scan,
 dvbscan and scte65scan, but none of the suggestions I've found so far
 seem to help.  Does anyone have any suggestions as to where I can go
 from here?  Could there be something wrong with the card itself?  Are
 there any diagnostics I could run?

 Thanks in advance for any help that anyone can offer.

 --dan
 --
 To unsubscribe from this list: send the line unsubscribe linux-media in
 the body of a message to majord...@vger.kernel.org
 More majordomo info at  http://vger.kernel.org/majordomo-info.html


Dan

I've got the 2200 version of this device and I do not get any error
messages during the load.

Steven Toth wrote the driver and has a status page here...

http://www.steventoth.net/blog/products/hvr-2250/

you may want to contact him directly, keeping in mind he does this out
of love and doesn't get paid for support :) (Although Hauppauge should
pay him something for the amount of work he does on their products
IMHO).

Good Luck
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Is anyone working on a Dual DVB-S2 PCIe Tuner driver?

2009-10-17 Thread Another Sillyname
I've had a look at the Wiki and there appears to be only two PCIe
cards that have Dual Tuners.

However both seem crazily expensive and perhaps in once case are vapourware.

Is there anyone working on any DVB-S2 PCI Express Device that has dual tuners?

Lastly (I know it's not shipping yet) there's a newly announced
Blackgold card BGT3595
that supposedly will have Dual DVB-T AND Dual DVB-S2 (so 4 tuners) on
a PCI express platform.
Will anyone be working on a driver for that device?  (Looking back
through the lists it would appear)
that previous cards from Blackgold couldn't get the information to
produce a driver.

Thanks in advance.
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


SAA7133 failure under Kernel 2.6.29

2009-06-22 Thread Another Sillyname
I noted from a discussion in the list back in April there were
problems with SAA7133 devices under 2.6.29 Kernel.

I have such a device and just upgraded to Fed 11 yesterday, device now
fails.  Under Fed 10 no problems.

I'm happy to provide dmesg and lspci and whatever else you need,
however don't want to clutter the list with data that may not be
needed.

The device in question is a 5168:3307 Lifeview Hybrid and I'm getting
the IRQF_Disabled error previously described.

Any ideas chaps?

Thanks in Advance
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html