1. 24 9月, 2007 1 次提交
  2. 23 9月, 2007 3 次提交
  3. 26 7月, 2007 1 次提交
  4. 01 5月, 2007 3 次提交
  5. 05 2月, 2007 1 次提交
    • P
      mmc: Add support for SDHC cards · fba68bd2
      Philip Langdale 提交于
      Thanks to the generous donation of an SDHC card by John Gilmore, and
      the surprisingly enlightened decision by the SD Card Association to
      publish useful specs, I've been able to bash out support for SDHC. The
      changes are not too profound:
      
      i) Add a card flag indicating the card uses block level addressing and
      check it in the block driver. As we never took advantage of byte-level
      addressing, this simply involves skipping the block -> byte
      translation when sending commands.
      
      ii) The layout of the CSD is changed - a set of fields are discarded
      to make space for a larger C_SIZE. We did not reference any of the
      discarded fields except those related to the C_SIZE.
      
      iii) Read and write timeouts are fixed values and not calculated from
      CSD values.
      
      iv) Before invoking SEND_APP_OP_COND, we must invoke the new
      SEND_IF_COND to inform the card we support SDHC.
      Signed-off-by: NPhilipl Langdale <philipl@overt.org>
      Signed-off-by: NPierre Ossman <drzeus@drzeus.cx>
      fba68bd2
  6. 15 1月, 2007 1 次提交
  7. 16 9月, 2006 1 次提交
  8. 07 9月, 2006 1 次提交
  9. 20 5月, 2006 1 次提交
  10. 22 2月, 2006 1 次提交
  11. 02 2月, 2006 1 次提交
  12. 10 1月, 2006 2 次提交
  13. 28 10月, 2005 1 次提交
  14. 08 9月, 2005 1 次提交
    • P
      [PATCH] sd: initialize SD cards · 335eadf2
      Pierre Ossman 提交于
      Support for the Secure Digital protocol in the MMC layer.
      
      A summary of the legal issues surrounding SD cards, as understood by yours
      truly:
      
      Members of the Secure Digital Association, hereafter SDA, are required to sign
      a NDA[1] before given access to any specifications.  It has been speculated
      that including an SD implementation would forbid these members to redistribute
      Linux.  This is the basic problem with SD support so it is unclear if it even
      is a problem since it has no effect on those of us that aren't members.
      
      The SDA doesn't seem to enforce these rules though since the patches included
      here are based on documentation made public by some of the members.  The most
      complete specs[2] are actually released by Sandisk, one of the founding
      companies of the SDA.
      
      Because of this the NDA is considered a non-issue by most involved in the
      discussions concerning these patches.  It might be that the SDA is only
      interested in protecting the so called "secure" bits of SD, which so far
      hasn't been found in any public spec.  (The card is split into two sections,
      one "normal" and one "secure" which has an access scheme similar to TPM:s).
      
      (As a side note, Microsoft is working to make things easier for us since they
      want to be able to include the source code for a SD driver in one of their
      development kits.  HP is making sure that the new NDA will allow a Linux
      implementation.  So far only the SDIO specs have been opened up[3].  More will
      hopefully follow.)
      
       [1] http://www.sdcard.org/membership/images/ippolicy.pdf
       [2] http://www.sandisk.com/pdf/oem/ProdManualSDCardv1.9.pdf
       [3] http://www.sdcard.org/sdio/Simplified%20SDIO%20Card%20Specification.pdf
      
      This patch contains the central parts of the SD support.  If no MMC cards are
      found on a bus then the MMC layer proceeds looking for SD cards.  Helper
      functions are extended to handle the special needs of SD cards.
      Signed-off-by: NPierre Ossman <drzeus@drzeus.cx>
      Cc: Russell King <rmk@arm.linux.org.uk>
      Cc: David Brownell <david-b@pacbell.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      335eadf2
  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