1. 23 8月, 2007 1 次提交
  2. 10 7月, 2007 2 次提交
  3. 13 6月, 2007 1 次提交
  4. 16 5月, 2007 1 次提交
  5. 08 5月, 2007 1 次提交
  6. 30 4月, 2007 2 次提交
  7. 18 2月, 2007 1 次提交
  8. 10 2月, 2007 1 次提交
  9. 10 10月, 2006 1 次提交
  10. 24 6月, 2006 1 次提交
  11. 30 1月, 2006 1 次提交
  12. 23 12月, 2005 1 次提交
  13. 20 11月, 2005 2 次提交
    • A
      Input: wistron - disable for x86_64 · e9fb028e
      Andrew Morton 提交于
      On x86_64:
      
      {standard input}:233: Error: suffix or operands invalid for `push'
      {standard input}:233: Error: suffix or operands invalid for `pop'
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      e9fb028e
    • D
      Input: add Wistron driver · 5fc14680
      Dmitry Torokhov 提交于
      A driver for laptop buttons using an x86 BIOS interface that is
      apparently used on quite a few laptops and seems to be originating
      from Wistron.
      
      This driver currently "knows" only about Fujitsu-Siemens Amilo Pro V2000
      (i.e. it can detect the laptop using DMI and it contains the
      keycode->key meaning mapping for this laptop) and Xeron SonicPro X 155G
      (probably can't be reliably autodetected, requires a module parameter),
      adding other laptops should be easy.
      
      In addition to reporting button presses to the input layer the driver
      also allows enabling/disabling the embedded wireless NIC (using the
      "Wifi" button); this is done using the same BIOS interface, so it seems
      only logical to keep the implementation together.  Any flexibility
      possibly gained by allowing users to remap the function of the "Wifi"
      button is IMHO not worth it when weighted against the necessity to run
      an user-space daemon to convert button presses to wifi state changes.
      Signed-off-by: NMiloslav Trmac <mitr@volny.cz>
      Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      5fc14680
  14. 31 10月, 2005 1 次提交
  15. 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