This driver can be used in some usb encoder devices.
http://www.linuxtv.org/wiki/index.php/Go7007
The related firmware files are in linux-firmware for some time.
The driver has left staging since few release, but I'm
fine if this is enabled in linux kernel 4.5 and later.
---
config-generic | 6 +++++-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/config-generic b/config-generic
index 9eef876..1cfcfab 100644
--- a/config-generic
+++ b/config-generic
@@ -3410,6 +3410,10 @@ CONFIG_VIDEO_CX231XX=m
CONFIG_VIDEO_CX231XX_ALSA=m
CONFIG_VIDEO_CX231XX_DVB=m
CONFIG_VIDEO_CX231XX_RC=y
+CONFIG_VIDEO_GO7007=m
+CONFIG_VIDEO_GO7007_USB=m
+CONFIG_VIDEO_GO7007_LOADER=m
+CONFIG_VIDEO_GO7007_USB_S2250_BOARD=m
CONFIG_VIDEO_HEXIUM_ORION=m
CONFIG_VIDEO_HEXIUM_GEMINI=m
CONFIG_VIDEO_IVTV=m
@@ -3422,6 +3426,7 @@ CONFIG_VIDEO_SAA6588=m
CONFIG_VIDEO_SAA7134=m
CONFIG_VIDEO_SAA7134_ALSA=m
CONFIG_VIDEO_SAA7134_DVB=m
+CONFIG_VIDEO_SAA7134_GO7007=m
CONFIG_VIDEO_SAA7134_RC=y
CONFIG_VIDEO_SOLO6X10=m
CONFIG_VIDEO_USBVISION=m
@@ -5560,7 +5565,6 @@ CONFIG_STAGING_MEDIA=y
# CONFIG_VIDEO_DT3155 is not set
# CONFIG_TI_ST is not set
# CONFIG_FB_XGI is not set
-# CONFIG_VIDEO_GO7007 is not set
# CONFIG_I2C_BCM2048 is not set
# CONFIG_DT3155 is not set
# CONFIG_PRISM2_USB is not set
--
1.7.2.1

On Sun, Feb 28, 2016 at 12:24 PM, Corey Sheldon <sheldon.corey(a)gmail.com> wrote:
> Josh,
>
Adding the Fedora kernel list on CC.
> Been updating my blog with news of the respins Southern_Gentlemen
> (fas: jbwillia) makes when new kernels make it to updates, like
> 4.4.2-301 did last night.
>
>
> Both for personal knowledge and per requests for a more 'snapshot'-ish
> changelog I am looking to get a effective .diff changelog since the
> last kernel.
"The last kernel" is kind of the weird part here. For Fedora, that
can mean anything between simply another build of the existing major
version with a minor fix included, to a whole kernel version rebase.
We'll try and cover all the cases, but as usual the answer is never
the same or any particular kernel.
> As I understand the work flow being:
>
> old kernel foo has features / fixes /etc
>
>
>
> new kernel bar
>
> since last re-spin with kernel foo this re-spin has updates from
> %date and the following fixes / patches which I presume would have ofc
> those in rpm -qp --changelog %bar.src.rpm.
Correct.
> However is there a place I could link to or parse for a more thorough
> %changelog ? without having to parse the entire creation spec file and /
> or hoping it has build version marked in the spec file?
The spec file doesn't have what you're looking for. The changelog in
the spec file is the only place we log any kind of description and
it's kept intentionally terse.
Now, if you can determine the old and new versions then there are a
few things you can do. I'll give some examples.
For things like kernel-4.3.6 -> 4.4.2, that would be a major version
rebase. As Laura said in the channel yesterday, the kernelnewbies.org
site usually has a decent writeup of features and major fixes for each
major kernel version. You can find the latest at the site Laura
linked to, or all their writeups at
http://kernelnewbies.org/LinuxVersions.
For things like kernel-4.4.2-300 -> 4.4.2-301, the changelog is going
to have a list of the stuff that is specifically interesting to
Fedora. That is simply a build of the existing upstream kernel, with
some changes we've added.
For a bump like 4.4.2 -> 4.4.3, there really isn't a good answer.
That is an upstream stable kernel release. There are bugfixes all
over the kernel tree, sometimes numbering in the hundreds of commits.
There may be some bug numbers listed in the RPM changelog that an
upstream stable release fixes, and we'll note that in the RPM
changelog if so. For the most part though, this is simply "more
fixes".
I hope that helps. If you have any further questions, please let us know.
josh

JÃ³hann_B._GuÃ°mundsson wrote:
> Arguably the regression in 4.4 with drm/i915 that causes screen
> flickering in dual monitor setups needs to be looked at before this gets
> released since it will get tiresome quite quickly for end users trying
> to do some work when suddenly one of the screen turns itself off and
> then on again.
I don't see any related patch in Greg's stable-queue for 4.4:
https://git.kernel.org/cgit/linux/kernel/git/stable/stable-queue.git/tree...
PD: the performance of HyperKitty is really awful!

i see such messages in dmesg repeatly on several machines
most likely some form of attacks since it affects in random intervals
any machine with a public IP and seems to be pretty new at all
why is there no source IP logged?
[501585.285984] conntrack: generic helper won't handle protocol 132.
Please consider loading the specific helper module.
sctp 132 SCTP # Stream Control Transmission Protocol