1. 25 4月, 2008 1 次提交
    • P
      V4L/DVB (7293): DMX_OUT_TSDEMUX_TAP: record two streams from same mux, resend · b01cd937
      Peter Hartley 提交于
      Currently (in linux-2.6.24, but linux-dvb hg looks similar), the
      dmx_output_t in the dmx_pes_filter_params decides two things: whether
      output is sent to demux0 or dvr0 (in dmxdev.c:dvb_dmxdev_ts_callback),
      *and* whether to depacketise TS (in dmxdev.c:dvb_dmxdev_filter_start).
      As it stands, those two things can't be set independently: output
      destined for demux0 is depacketised, output for dvr0 isn't.
      
      This is what you want for capturing multiple audio streams from the same
      multiplex simultaneously: open demux0 several times and send
      depacketised output there. And capturing a single video stream is fine
      not what you want: you want multi-open (so demux0, not dvr0), but you
      want the TS nature preserved (because that's what you want on output, as
      you're going to re-multiplex it with the audio).
      
      At least one existing solution -- GStreamer -- sends all its streams
      simultaneously via dvr0 and demuxes again in userland, but it seems a
      bit of a shame to pick out all the PIDs in kernel, stick them back
      together in kernel, and send them to userland only to get unpicked
      again, when the alternative is such a small API addition.
      
      The attached patch adds a new value for dmx_output_t:
      DMX_OUT_TSDEMUX_TAP, which sends TS to the demux0 device. With this
      patch and a dvb-usb-dib0700 (and UK Freeview from Sandy Heath), I can
      successfully capture an audio/video PID pair into a TS file that mplayer
      can play back.
      Signed-off-by: NPeter Hartley <pdh@utter.chaos.org.uk>
      Acked-by: NAndreas Oberritter <obi@linuxtv.org>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@infradead.org>
      b01cd937
  2. 10 10月, 2007 1 次提交
  3. 19 7月, 2007 1 次提交
  4. 28 4月, 2007 1 次提交
  5. 27 3月, 2007 1 次提交
  6. 15 2月, 2007 1 次提交
    • T
      [PATCH] remove many unneeded #includes of sched.h · cd354f1a
      Tim Schmielau 提交于
      After Al Viro (finally) succeeded in removing the sched.h #include in module.h
      recently, it makes sense again to remove other superfluous sched.h includes.
      There are quite a lot of files which include it but don't actually need
      anything defined in there.  Presumably these includes were once needed for
      macros that used to live in sched.h, but moved to other header files in the
      course of cleaning it up.
      
      To ease the pain, this time I did not fiddle with any header files and only
      removed #includes from .c-files, which tend to cause less trouble.
      
      Compile tested against 2.6.20-rc2 and 2.6.20-rc2-mm2 (with offsets) on alpha,
      arm, i386, ia64, mips, powerpc, and x86_64 with allnoconfig, defconfig,
      allmodconfig, and allyesconfig as well as a few randconfigs on x86_64 and all
      configs in arch/arm/configs on arm.  I also checked that no new warnings were
      introduced by the patch (actually, some warnings are removed that were emitted
      by unnecessarily included header files).
      Signed-off-by: NTim Schmielau <tim@physik3.uni-rostock.de>
      Acked-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      cd354f1a
  7. 25 6月, 2006 1 次提交
  8. 02 4月, 2006 1 次提交
  9. 22 3月, 2006 4 次提交
  10. 27 2月, 2006 1 次提交
  11. 07 2月, 2006 1 次提交
  12. 13 12月, 2005 1 次提交
  13. 10 9月, 2005 2 次提交
  14. 08 7月, 2005 2 次提交
  15. 17 5月, 2005 1 次提交
  16. 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