1. 21 1月, 2011 1 次提交
    • D
      kconfig: rename CONFIG_EMBEDDED to CONFIG_EXPERT · 6a108a14
      David Rientjes 提交于
      The meaning of CONFIG_EMBEDDED has long since been obsoleted; the option
      is used to configure any non-standard kernel with a much larger scope than
      only small devices.
      
      This patch renames the option to CONFIG_EXPERT in init/Kconfig and fixes
      references to the option throughout the kernel.  A new CONFIG_EMBEDDED
      option is added that automatically selects CONFIG_EXPERT when enabled and
      can be used in the future to isolate options that should only be
      considered for embedded systems (RISC architectures, SLOB, etc).
      
      Calling the option "EXPERT" more accurately represents its intention: only
      expert users who understand the impact of the configuration changes they
      are making should enable it.
      Reviewed-by: NIngo Molnar <mingo@elte.hu>
      Acked-by: NDavid Woodhouse <david.woodhouse@intel.com>
      Signed-off-by: NDavid Rientjes <rientjes@google.com>
      Cc: Greg KH <gregkh@suse.de>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Jens Axboe <axboe@kernel.dk>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Robin Holt <holt@sgi.com>
      Cc: <linux-arch@vger.kernel.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      6a108a14
  2. 08 1月, 2011 2 次提交
    • N
      pata_platform: Remove CONFIG_HAVE_PATA_PLATFORM's dependencies. · 2ad2c320
      Nick Bowler 提交于
      CONFIG_HAVE_PATA_PLATFORM, by virtue of where its defined, has a
      dependency on CONFG_ATA and CONFIG_ATA_SFF.  This causes Kconfig
      warnings when it is selected by various architectures, such as
      
        warning: (ARCH_VEXPRESS && <choice> || ARCH_RPC && <choice> || MACH_VPAC270 && ARCH_PXA || MACH_REALVIEW_PB11MP && ARCH_REALVIEW || MACH_REALVIEW_PBA8 && ARCH_REALVIEW || MACH_REALVIEW_PBX && ARCH_REALVIEW || MACH_BAST_IDE && ARCH_S3C2410 || MACH_ANUBIS && ARCH_S3C2410) selects HAVE_PATA_PLATFORM which has unmet direct dependencies (ATA && ATA_SFF)
      
      Since this option is only used to control visibility of the
      CONFIG_PATA_PLATFORM option and isn't itself visible in the menu,
      it is straightforward to simply remove these dependencies rather
      than adjust all the architectures.
      Signed-off-by: NNick Bowler <nbowler@elliptictech.com>
      Signed-off-by: NJeff Garzik <jgarzik@redhat.com>
      2ad2c320
    • S
      pata_hpt3x2n: clarify about HPT371N support · 0ca646db
      Sergei Shtylyov 提交于
      Commit 28e21c8c (pata_hpt3x2n: Add HPT371N
      support and other bits) forgot to update the driver's Kconfig entry, heading
      comment, and module description (that also wrongly claims support of HPT302)
      which may confuse users...
      Signed-off-by: NSergei Shtylyov <sshtylyov@ru.mvista.com>
      Signed-off-by: NJeff Garzik <jgarzik@redhat.com>
      0ca646db
  3. 06 1月, 2011 1 次提交
  4. 25 12月, 2010 2 次提交
  5. 26 8月, 2010 1 次提交
  6. 02 8月, 2010 2 次提交
  7. 18 6月, 2010 1 次提交
  8. 03 6月, 2010 1 次提交
  9. 26 5月, 2010 1 次提交
    • T
      libata-sff: make BMDMA optional · 9a7780c9
      Tejun Heo 提交于
      Make BMDMA optional depending on new config variable CONFIG_ATA_BMDMA.
      In Kconfig, drivers are grouped into five groups - non-SFF native, SFF
      w/ custom DMA interface, SFF w/ BMDMA, PIO-only SFF, and generic
      fallback / legacy ones.  Kconfig and Makefile are reorganized
      according to the groups and ordered alphabetically inside each group.
      
      ata_ioports.bmdma_addr and ata_port.bmdma_prd[_dma] are put into
      CONFIG_ATA_BMDMA, as are all bmdma related ops, variables and
      functions.
      
      This increase the binary size slightly when BMDMA is enabled but on
      both native-only and PIO-only configurations the size is slightly
      reduced.  Either way, the size difference is insignificant.  This
      change is more meaningful to signify the separation between SFF and
      BMDMA and as a tool to verify the separation.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Signed-off-by: NJeff Garzik <jgarzik@redhat.com>
      9a7780c9
  10. 15 5月, 2010 2 次提交
  11. 02 3月, 2010 1 次提交
  12. 24 12月, 2009 1 次提交
  13. 09 12月, 2009 1 次提交
  14. 04 12月, 2009 1 次提交
  15. 03 12月, 2009 2 次提交
  16. 18 9月, 2009 1 次提交
  17. 02 9月, 2009 2 次提交
    • A
      [libata] Add pata_rdc driver for RDC ATA devices · 6b406782
      Alan Cox 提交于
      From: Alan Cox <alan@linux.intel.com>
      Signed-off-by: NAlan Cox <alan@linux.intel.com>
      Signed-off-by: NJeff Garzik <jgarzik@redhat.com>
      6b406782
    • R
      libata: add command name parsing for error output · 6521148c
      Robert Hancock 提交于
      This patch improve libata's output for error/notification messages
      to allow easier comprehension and debugging:
      
      When ATAPI commands issued through the SCSI layer fail, use SCSI
      functions to print the CDB in human-readable form instead of just
      dumping out the CDB in hex.
      
      Print out the name of the failed command (as defined by the ATA
      specification) in error handling output along with the raw register
      contents.
      
      When reporting status of ACPI taskfile commands executed on resume,
      also output the names of the commands being executed (or not) in
      readable form.
      
      Since the extra data for printing command names increases kernel
      size slightly, a config option has been added to allow disabling
      command name output (as well as some of the error register parsing)
      for those highly sensitive to kernel text size.
      Signed-off-by: NRobert Hancock <hancockrwd@gmail.com>
      Signed-off-by: NJeff Garzik <jgarzik@redhat.com>
      6521148c
  18. 23 6月, 2009 1 次提交
  19. 31 5月, 2009 1 次提交
  20. 30 3月, 2009 1 次提交
  21. 26 1月, 2009 1 次提交
  22. 16 1月, 2009 1 次提交
  23. 21 12月, 2008 1 次提交
  24. 09 12月, 2008 1 次提交
  25. 29 9月, 2008 1 次提交
  26. 09 9月, 2008 1 次提交
    • A
      ahci, pata_marvell: play nicely together · 5b66c829
      Alan Cox 提交于
      I've been chasing Jeff about this for months.  Jeff added the Marvell
      device identifiers to the ahci driver without making the AHCI driver
      handle the PATA port. This means a lot of users can't use current
      kernels and in most distro cases can't even install.
      
      This has been going on since March 2008 for the 6121 Marvell, and late 2007
      for the 6145!!!
      
      This was all pointed out at the time and repeatedly ignored. Bugs assigned
      to Jeff about this are ignored also.
      
      To quote Jeff in email
      
      > "Just switch the order of 'ahci' and 'pata_marvell' in
      > /etc/modprobe.conf, then use Fedora's tools regenerate the initrd.
      
      > See?  It's not rocket science, and the current configuration can be
      > easily made to work for Fedora users."
      
      (Which isn't trivial, isn't end user, shouldn't be needed, and as it usually
      breaks at install time is in fact impossible)
      
      To quote Jeff in August 2007
      
      > "   mv-ahci-pata
      > Marvell 6121/6141 PATA support.  Needs fixing in the 'PATA controller
      > command' area before it is usable, and can go upstream."
      
      Only he add the ids anyway later and caused regressions, adding a further
      id in March causing more regresions.
      
      The actual fix for the moment is very simple. If the user has included
      the pata_marvell driver let it drive the ports. If they've only selected
      for SATA support give them the AHCI driver which will run the port a fraction
      faster. Allow the user to control this decision via ahci.marvell_enable as
      a module parameter so that distributions can ship 'it works' defaults and
      smarter users (or config tools) can then flip it over it desired.
      Signed-off-by: NAlan Cox <alan@redhat.com>
      Signed-off-by: NJeff Garzik <jgarzik@redhat.com>
      5b66c829
  27. 01 9月, 2008 1 次提交
    • A
      sparc: remove CONFIG_SUN4 · 5110bd21
      Adrian Bunk 提交于
      While doing some easy cleanups on the sparc code I noticed that the
      CONFIG_SUN4 code seems to be worse than the rest - there were some
      "I don't know how it should work, but the current code definitely cannot
      work." places.
      
      And while I have seen people running Linux on machines like a
      SPARCstation 5 a few years ago I don't recall having seen sun4
      machines, even less ones running Linux.
      Signed-off-by: NAdrian Bunk <bunk@kernel.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      5110bd21
  28. 19 6月, 2008 1 次提交
  29. 06 5月, 2008 2 次提交
  30. 29 4月, 2008 1 次提交
  31. 18 4月, 2008 3 次提交