1. 23 6月, 2006 3 次提交
    • E
      [PATCH] w1: Use mutexes instead of semaphores. · abd52a13
      Evgeniy Polyakov 提交于
      Use mutexes instead of semaphores.
      Patch tested on x86_64 and i386 with test bus master driver.
      Signed-off-by: NEvgeniy Polyakov <johnpol@2ka.mipt.ru>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      abd52a13
    • E
      [PATCH] w1: Userspace communication protocol over connector. · 12003375
      Evgeniy Polyakov 提交于
      There are three types of messages between w1 core and userspace:
      1. Events. They are generated each time new master or slave device found
      	either due to automatic or requested search.
      2. Userspace commands. Includes read/write and search/alarm search comamnds.
      3. Replies to userspace commands.
      
      From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      12003375
    • E
      [PATCH] w1: Added default generic read/write operations. · f522d239
      Evgeniy Polyakov 提交于
      Special file in each w1 slave device's directory called "rw" is created
      each time new slave and no appropriate w1 family is registered.
      "rw" file supports read and write operations, which allows to perform
      almost any kind of operations. Each logical operation is a transaction
      in nature, which can contain several (two or one) low-level operations.
      Let's see how one can read EEPROM context:
      1. one must write control buffer, i.e. buffer containing command byte
      and two byte address. At this step bus is reset and appropriate device
      is selected using either W1_SKIP_ROM or W1_MATCH_ROM command.
      Then provided control buffer is being written to the wire.
      2. reading. This will issue reading eeprom response.
      
      It is possible that between 1. and 2. w1 master thread will reset bus for
      searching and slave device will be even removed, but in this case 0xff will
      be read, since no device was selected.
      Signed-off-by: NEvgeniy Polyakov <johnpol@2ka.mipt.ru>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      f522d239
  2. 24 3月, 2006 4 次提交
  3. 05 1月, 2006 1 次提交
  4. 15 10月, 2005 1 次提交
  5. 09 9月, 2005 6 次提交
  6. 13 8月, 2005 1 次提交
  7. 12 7月, 2005 1 次提交
  8. 26 6月, 2005 1 次提交
    • C
      [PATCH] Cleanup patch for process freezing · 3e1d1d28
      Christoph Lameter 提交于
      1. Establish a simple API for process freezing defined in linux/include/sched.h:
      
         frozen(process)		Check for frozen process
         freezing(process)		Check if a process is being frozen
         freeze(process)		Tell a process to freeze (go to refrigerator)
         thaw_process(process)	Restart process
         frozen_process(process)	Process is frozen now
      
      2. Remove all references to PF_FREEZE and PF_FROZEN from all
         kernel sources except sched.h
      
      3. Fix numerous locations where try_to_freeze is manually done by a driver
      
      4. Remove the argument that is no longer necessary from two function calls.
      
      5. Some whitespace cleanup
      
      6. Clear potential race in refrigerator (provides an open window of PF_FREEZE
         cleared before setting PF_FROZEN, recalc_sigpending does not check
         PF_FROZEN).
      
      This patch does not address the problem of freeze_processes() violating the rule
      that a task may only modify its own flags by setting PF_FREEZE. This is not clean
      in an SMP environment. freeze(process) is therefore not SMP safe!
      Signed-off-by: NChristoph Lameter <christoph@lameter.com>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      3e1d1d28
  9. 22 6月, 2005 6 次提交
  10. 21 6月, 2005 1 次提交
  11. 19 4月, 2005 1 次提交
  12. 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