1. 31 Mar, 2011 1 commit
  2. 13 Jan, 2011 1 commit
    • Mika Laitio's avatar
      w1: DS2423 counter driver and documentation · 17fecb55
      Mika Laitio authored
      This is a 1-wire/w1 DS2423 slave driver for reading the values from all 4
      counters available DS2423 devices by using standard w1_slave file.  In
      ds2423 the counters are tied to ram pages 12-15 in and each of those
      ram-pages.  Each of these counter values (and asoociated ram page values)
      are represented as a own line in w1_slave file.  Driver has been tested on
      mips and x86.
      usage example:
      cat /sys/bus/w1/devices/1d-00000009b964/w1_slave
      00 02 00 00 00 00 00 00 00 6d 38 00 ff ff 00 00 fe ff 00 00 ff ff 00 00 ff
      ff 00 00 ff ff 00 00 ff ff 00 00 ff ff 00 00 ff ff crc=YES c=2
      00 02 00 00 00 00 00 00 00 e0 1f 00 ff ff 00 00 ff ff 00 00 ff ff 00 00 ff
      ff 00 00 ff ff 00 00 ff ff 00 00 ff ff 00 00 ff ff crc=YES c=2
      00 5a 0e 5f 18 00 00 00 00 0b 28 00 ff ff 00 00 ff ff 00 00 ff ff 00 00 ff
      ff 00 00 ff ff 00 00 ff ff 00 00 ff ff 00 00 ff ff crc=YES c=408882778
      00 05 00 00 00 00 00 00 00 8d 39 ff ff ff ff ff ff ff ff ff ff ff ff ff ff
      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff crc=YES c=5
      Patch includes also the documentation.
      [randy.dunlap@oracle.com: fix ds2423 build, needs to select CRC16]
      Signed-off-by: default avatarMika Laitio <lamikr@pilppa.org>
      Signed-off-by: default avatarRandy Dunlap <randy.dunlap@oracle.com>
      Cc: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
  3. 04 Aug, 2010 1 commit
    • Justin P. Mattock's avatar
      Documentation: update broken web addresses. · 0ea6e611
      Justin P. Mattock authored
      Below you will find an updated version from the original series bunching all patches into one big patch
      updating broken web addresses that are located in Documentation/*
      Some of the addresses date as far far back as 1995 etc... so searching became a bit difficult,
      the best way to deal with these is to use web.archive.org to locate these addresses that are outdated.
      Now there are also some addresses pointing to .spec files some are located, but some(after searching
      on the companies site)where still no where to be found. In this case I just changed the address
      to the company site this way the users can contact the company and they can locate them for the users.
      Signed-off-by: default avatarJustin P. Mattock <justinmattock@gmail.com>
      Signed-off-by: default avatarThomas Weber <weber@corscience.de>
      Signed-off-by: default avatarMike Frysinger <vapier.adi@gmail.com>
      Cc: Paulo Marques <pmarques@grupopie.com>
      Cc: Randy Dunlap <rdunlap@xenotime.net>
      Cc: Michael Neuling <mikey@neuling.org>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
  4. 23 Apr, 2010 1 commit
  5. 04 Oct, 2009 1 commit
  6. 08 Jan, 2009 4 commits
  7. 13 Nov, 2008 1 commit
  8. 16 Oct, 2008 3 commits
  9. 06 Feb, 2008 1 commit
  10. 17 Oct, 2007 1 commit
  11. 22 Jun, 2006 3 commits
    • Evgeniy Polyakov's avatar
      [PATCH] w1: Userspace communication protocol over connector. · 12003375
      Evgeniy Polyakov authored
      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: default avatarGreg Kroah-Hartman <gregkh@suse.de>
    • Evgeniy Polyakov's avatar
    • Evgeniy Polyakov's avatar
      [PATCH] w1: Added default generic read/write operations. · f522d239
      Evgeniy Polyakov authored
      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: default avatarEvgeniy Polyakov <johnpol@2ka.mipt.ru>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
  12. 24 Mar, 2006 1 commit
  13. 22 Jun, 2005 1 commit
  14. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      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!