Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
大约 1 年 前同步成功

通知 158
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 25 4月, 2008 2 次提交
  3. 26 1月, 2008 2 次提交
  5. 10 10月, 2007 7 次提交
  7. 19 7月, 2007 4 次提交
  9. 23 5月, 2007 1 次提交
  11. 10 12月, 2006 2 次提交
  13. 26 9月, 2006 3 次提交
  15. 30 7月, 2006 1 次提交
  17. 01 7月, 2006 1 次提交
  19. 25 6月, 2006 1 次提交
  21. 22 3月, 2006 1 次提交
  23. 07 2月, 2006 6 次提交
  25. 24 1月, 2006 2 次提交
  27. 16 1月, 2006 1 次提交
    • H
      V4L/DVB (3384): Separate tv & radio freqs, fix cb/freq transmit order for tuners that need this. · 27487d44
      由 Hans Verkuil 提交于 
      - Moved MSP_SET_MATRIX to v4l2-common.h
- Fix typos and integer overflows in tea5767.c
- Split old freq field into a tv_freq and a radio_freq. Prevents
  that a radio tuner is initialized with a tv frequency or vice versa.
- When switching to radio mode initialize the tuner with the last
  used radio frequency (this was already done for the TV mode).
  As a result of these changes the tuner module now remembers the
  last set radio and TV frequencies, which is what you would expect
  to happen.
- Move out of range frequencies to the closest valid frequency as per
  v4l2 API spec.
- Fix incorrect initial radio frequency (multiplier is 16000, not 16)
- Add boundary check for out of range frequencies.
- Use new flag to check if the order of the CB and freq. depends on
  the last set frequency. That is needed for some tuners or you can
  get static as a result. The flag is added for those tuners where I know
  that the datasheet indicates that this is necessary.
- For this new check use the last set div value, not the last frequency
  as radio frequencies are always much higher due to the 16000 multiplier.
Signed-off-by: NHans Verkuil <hverkuil@xs4all.nl>
Signed-off-by: NMauro Carvalho Chehab <mchehab@infradead.org>
      27487d44
  29. 14 1月, 2006 1 次提交
    • M
      V4L/DVB (3359): Redesign tuners struct for maximum flexibility · 7b0ac9cd
      由 Michael Krufky 提交于 
      - Tunertype struct redefined to allow one or more tuner_params structs
  per tuner definition, one for each video standard.
- Each tuner_params struct has an element containing an arbitrary
  amount of tuner_ranges.
  (this is needed for dvb tuners - to be handled later)
- A tuner_range may be referenced by multiple tuner_params structs.
  There are many duplicates in here. Reusing tuner_range structs,
  rather than defining new ones for each tuner, will cut down on
  memory usage, and is preferred when possible.
- tunertype struct contains an element, has_tda988x.
  We must set this for all tunertypes that contain a tda988x
  chip, and then we can remove this setting from the various
  card structs.
- Improves tuners array memory usage efficiency.
- Right now, all tuners are using the first tuner_params[] array element
  for analog mode. In the future, we will be merging similar tuner
  definitions together, such that each tuner definition will have a
  tuner_params struct for each available video standard. At that point,
  the tuner_params[] array element will be chosen based on the video
  standard in use.
Signed-off-by: NMichael Krufky <mkrufky@m1k.net>
Signed-off-by: NMauro Carvalho Chehab <mchehab@infradead.org>
      7b0ac9cd
  31. 10 1月, 2006 5 次提交