1. 25 6月, 2006 3 次提交
  2. 24 5月, 2006 1 次提交
  3. 13 5月, 2006 3 次提交
  4. 04 4月, 2006 1 次提交
  5. 02 4月, 2006 4 次提交
  6. 25 3月, 2006 2 次提交
  7. 22 3月, 2006 6 次提交
  8. 27 2月, 2006 3 次提交
  9. 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
  10. 10 1月, 2006 3 次提交
  11. 14 11月, 2005 3 次提交
  12. 09 11月, 2005 3 次提交
  13. 10 9月, 2005 1 次提交
  14. 08 9月, 2005 1 次提交
  15. 29 6月, 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