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 work....unfortunately 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 <anothersname@xxxxxxxxxxxxxx> wrote: > OK, I realise I should be able to work this out....but 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 <anothersname@xxxxxxxxxxxxxx> 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 <dheitmueller@xxxxxxxxxxxxxx> 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 majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
