1. 21 5月, 2013 1 次提交
  2. 31 7月, 2012 1 次提交
  3. 31 12月, 2011 1 次提交
  4. 07 11月, 2011 1 次提交
  5. 19 5月, 2010 1 次提交
  6. 30 3月, 2009 6 次提交
    • A
      V4L/DVB (11124): Add support for ProVideo PV-183 to bttv · dceaddb9
      Alan McIvor 提交于
      Add support for ProVideo PV-183 to bttv
      
      This patch adds support for the ProVideo PV-183 card to the bttv
      device driver. The PV-183 is a PCI card with 8 BT878 devices plus a Hint
      Corp HiNT HB4 PCI-PCI Bridge. Each BT878 has two composite input channels
      available. There are no tuners on this card.
      Signed-off-by: NAlan McIvor <alan.mcivor@reveal.co.nz>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      dceaddb9
    • H
      V4L/DVB (11044): v4l2-device: add v4l2_device_disconnect · ae6cfaac
      Hans Verkuil 提交于
      Call v4l2_device_disconnect when the parent of a hotpluggable device
      disconnects. This ensures that you do not have a pointer to a device that
      is no longer present.
      Signed-off-by: NHans Verkuil <hverkuil@xs4all.nl>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      ae6cfaac
    • J
    • R
      V4L/DVB (10944): Conceptronic CTVFMI2 PCI Id · 76ecf459
      Robert Millan 提交于
      My BTTV_BOARD_CONCEPTRONIC_CTVFMI2 card wasn't auto-detected, here's a patch
      that adds its PCI id.
      
      lspci -nnv output:
      
      05:06.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
      05:06.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
      
      Press <break> within 3 seconds if this is wrong.
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      76ecf459
    • B
      V4L/DVB (10827): Add support for GeoVision GV-800(S) · 0c5db425
      Bruno Christo 提交于
      I have a GeoVision GV-800(S) card, it has 4 CONEXANT BT878A chips.
      It has 16 video inputs and 4 audio inputs, and it is almost identical
      to the GV-800, as seen on http://bttv-gallery.de .
      The only difference appears to be the analog mux, it has a CD22M3494
      in place of the MT8816AP. The card has a blue PCB, as seen in this
      picture: http://www.gsbr.com.br/imagem/kits/GeoVision%20GV%20800.jpg .
      
      This card wasn't originally supported, and it was detected as
      UNKNOWN/GENERIC. The video inputs weren't working, so I tried
      "forcing" a few cards like the GeoVision GV-600, but there was still
      no video. So I made a patch to support this card, based on the Kodicom
      4400r.
      
      The GV-800(S) is identified as follows:
      
      ...
      02:00.0 Multimedia video controller: Brooktree Corporation Bt878 Video
      Capture (rev 11)
      02:00.1 Multimedia controller: Brooktree Corporation Bt878 Audio
      Capture (rev 11)
      02:04.0 Multimedia video controller: Brooktree Corporation Bt878 Video
      Capture (rev 11)
      02:04.1 Multimedia controller: Brooktree Corporation Bt878 Audio
      Capture (rev 11)
      02:08.0 Multimedia video controller: Brooktree Corporation Bt878 Video
      Capture (rev 11)
      02:08.1 Multimedia controller: Brooktree Corporation Bt878 Audio
      Capture (rev 11)
      02:0c.0 Multimedia video controller: Brooktree Corporation Bt878 Video
      Capture (rev 11)
      02:0c.1 Multimedia controller: Brooktree Corporation Bt878 Audio
      Capture (rev 11)
      
      ...
      02:00.0 0400: 109e:036e (rev 11)
             Subsystem: 800a:763d
             Flags: bus master, medium devsel, latency 32, IRQ 10
             Memory at cdfff000 (32-bit, prefetchable) [size=4K]
             Capabilities: [44] Vital Product Data <?>
             Capabilities: [4c] Power Management version 2
             Kernel modules: bttv
      
      02:00.1 0480: 109e:0878 (rev 11)
             Subsystem: 800a:763d
             Flags: bus master, medium devsel, latency 32, IRQ 10
             Memory at cdffe000 (32-bit, prefetchable) [size=4K]
             Capabilities: [44] Vital Product Data <?>
             Capabilities: [4c] Power Management version 2
      
      02:04.0 0400: 109e:036e (rev 11)
             Subsystem: 800b:763d
             Flags: bus master, medium devsel, latency 32, IRQ 10
             Memory at cdffd000 (32-bit, prefetchable) [size=4K]
             Capabilities: [44] Vital Product Data <?>
             Capabilities: [4c] Power Management version 2
             Kernel modules: bttv
      
      02:04.1 0480: 109e:0878 (rev 11)
             Subsystem: 800b:763d
             Flags: bus master, medium devsel, latency 32, IRQ 10
             Memory at cdffc000 (32-bit, prefetchable) [size=4K]
             Capabilities: [44] Vital Product Data <?>
             Capabilities: [4c] Power Management version 2
      
      02:08.0 0400: 109e:036e (rev 11)
             Subsystem: 800c:763d
             Flags: bus master, medium devsel, latency 32, IRQ 10
             Memory at cdffb000 (32-bit, prefetchable) [size=4K]
             Capabilities: [44] Vital Product Data <?>
             Capabilities: [4c] Power Management version 2
             Kernel modules: bttv
      
      02:08.1 0480: 109e:0878 (rev 11)
             Subsystem: 800c:763d
             Flags: bus master, medium devsel, latency 32, IRQ 10
             Memory at cdffa000 (32-bit, prefetchable) [size=4K]
             Capabilities: [44] Vital Product Data <?>
             Capabilities: [4c] Power Management version 2
      
      02:0c.0 0400: 109e:036e (rev 11)
             Subsystem: 800d:763d
             Flags: bus master, medium devsel, latency 32, IRQ 10
             Memory at cdff9000 (32-bit, prefetchable) [size=4K]
             Capabilities: [44] Vital Product Data <?>
             Capabilities: [4c] Power Management version 2
             Kernel modules: bttv
      
      02:0c.1 0480: 109e:0878 (rev 11)
             Subsystem: 800d:763d
             Flags: bus master, medium devsel, latency 32, IRQ 10
             Memory at cdff8000 (32-bit, prefetchable) [size=4K]
             Capabilities: [44] Vital Product Data <?>
             Capabilities: [4c] Power Management version 2
      
      As you can see, the GV-800(S) card is almost identical to the GV-800
      on bttv-gallery, so this patch might also work for that card. If not,
      only a few changes should be required on the gv800s_write() function.
      
      After this patch, the video inputs work correctly on linux 2.6.24 and
      2.6.27 using the software 'motion'. The input order may seem a little
      odd, but it's the order the original software/driver uses, and I decided
      to keep that order to get the most out of the card.
      
      I tried to get the audio working with the snd-bt87x module, but I only
      get noise from every audio input, even after selecting a different mux
      with alsamixer. Also, after trying to play sound from those sources, I
      randomly get a RISC error about an invalid RISC opcode, and then that
      output stops working. I also can't change the sampling rate when
      recording. Any pointers to adding audio support are welcome.
      Signed-off-by: NBruno Christo <bchristo@inf.ufsm.br>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      0c5db425
    • D
      V4L/DVB (10299): bttv: Add support for IVCE-8784 support for V4L2 bttv driver · ade0815c
      Douglas Kosovic 提交于
      It's a quad Bt878 PCI-e x1 capture board that's basically the same as the
      IVC-200 (quad Bt878 PCI) capture board that's currently supported in
      the V4L2 bttv driver.
      
      Manufacturer's web page for IVCE-8784 with photo and info:
        http://www.iei.com.tw/en/product_IPC.asp?model=IVCE-8784Signed-off-by: NDouglas Kosovic <douglask@itee.uq.edu.au>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      ade0815c
  7. 30 12月, 2008 1 次提交
  8. 12 10月, 2008 1 次提交
  9. 25 4月, 2008 2 次提交
    • M
    • E
      V4L/DVB (7366): Support for a 16-channel bt878 card · 97275ac5
      Ernesto Hernández-Novich 提交于
      I have what looks like a Geovision GV-600 (or 650) card. It has a large
      chip in the middle labeled
      
      CONEXANT
      FUSION 878A
      25878-13
      E345881.1
      0312 TAIWAN
      
      It has an audio connector coming out from a chip labeled
      
      ATMEL
      0242
      AT89C2051-24PI
      
      It is identified as follows on my Debian GNU/Linux Etch (kernel 2.6.18)
      
      ...
      01:0a.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
      01:0a.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
      ...
      01:0a.0 0400: 109e:036e (rev 11)
              Subsystem: 008a:763c
              Flags: bus master, medium devsel, latency 64, IRQ 58
              Memory at dfffe000 (32-bit, prefetchable) [size=4K]
              Capabilities: [44] Vital Product Data
              Capabilities: [4c] Power Management version 2
      
      01:0a.1 0480: 109e:0878 (rev 11)
              Subsystem: 008a:763c
              Flags: bus master, medium devsel, latency 64, IRQ 58
              Memory at dffff000 (32-bit, prefetchable) [size=4K]
              Capabilities: [44] Vital Product Data
              Capabilities: [4c] Power Management version 2
      
      It was being detected as a GENERIC UNKNOWN CARD both by the 2.6.18
      kernel and the latest v4l-dvb drivers, but it did not work at all. The
      card has sixteen (16) BNC video inputs, four of them on the board itself
      and twelve on three daughter-cards. It has a single bt878 chip, no tuner
      and what looks like and audio input. After doing some research I managed
      to get only eight channels working by forcing card=125 and those DID NOT
      match channels 0-7 on the card, and no audio.
      
      Based on what was working for card=125, I added the card definition
      block, added a specific muxsel routine and got the card working fully
      with xawtv, where the sixteen channels show up as Composite0 to
      Composite15, matching the channel labels in the card and daughter-cards.
      I have made no efforts yet to get audio working, but would appreciate
      any pointers.
      Signed-off-by: NErnesto Hernández-Novich <emhn@usb.ve>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@infradead.org>
      97275ac5
  10. 10 10月, 2007 1 次提交
  11. 19 7月, 2007 2 次提交
  12. 28 4月, 2007 1 次提交
  13. 21 2月, 2007 1 次提交
  14. 25 6月, 2006 2 次提交
  15. 12 1月, 2006 1 次提交
  16. 10 1月, 2006 1 次提交
  17. 14 11月, 2005 1 次提交
  18. 09 11月, 2005 7 次提交
  19. 10 9月, 2005 2 次提交
  20. 13 7月, 2005 1 次提交
  21. 24 6月, 2005 1 次提交
  22. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4