1. 08 Feb, 2008 3 commits
    • Jan Kara's avatar
      udf: change maintainer · 800fdfb9
      Jan Kara authored
      I've tried to contact Ben Fennema a few times but without success.  Since I'm
      currently probably closest to being an UDF maintainer, I guess it's fine to
      also change the entry in MAINTAINERS.
      Signed-off-by: default avatarJan Kara <jack@suse.cz>
      Cc: <bfennema@falcon.csc.calpoly.edu>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
    • Nick Piggin's avatar
      rewrite rd · 9db5579b
      Nick Piggin authored
      This is a rewrite of the ramdisk block device driver.
      The old one is really difficult because it effectively implements a block
      device which serves data out of its own buffer cache.  It relies on the dirty
      bit being set, to pin its backing store in cache, however there are non
      trivial paths which can clear the dirty bit (eg.  try_to_free_buffers()),
      which had recently lead to data corruption.  And in general it is completely
      wrong for a block device driver to do this.
      The new one is more like a regular block device driver.  It has no idea about
      vm/vfs stuff.  It's backing store is similar to the buffer cache (a simple
      radix-tree of pages), but it doesn't know anything about page cache (the pages
      in the radix tree are not pagecache pages).
      There is one slight downside -- direct block device access and filesystem
      metadata access goes through an extra copy and gets stored in RAM twice.
      However, this downside is only slight, because the real buffercache of the
      device is now reclaimable (because we're not playing crazy games with it), so
      under memory intensive situations, footprint should effectively be the same --
      maybe even a slight advantage to the new driver because it can also reclaim
      buffer heads.
      The fact that it now goes through all the regular vm/fs paths makes it
      much more useful for testing, too.
         text    data     bss     dec     hex filename
         2837     849     384    4070     fe6 drivers/block/rd.o
         3528     371      12    3911     f47 drivers/block/brd.o
      Text is larger, but data and bss are smaller, making total size smaller.
      A few other nice things about it:
      - Similar structure and layout to the new loop device handlinag.
      - Dynamic ramdisk creation.
      - Runtime flexible buffer head size (because it is no longer part of the
        ramdisk code).
      - Boot / load time flexible ramdisk size, which could easily be extended
        to a per-ramdisk runtime changeable size (eg. with an ioctl).
      - Can use highmem for the backing store.
      [akpm@linux-foundation.org: fix build]
      [byron.bbradley@gmail.com: make rd_size non-static]
      Signed-off-by: default avatarNick Piggin <npiggin@suse.de>
      Signed-off-by: default avatarByron Bradley <byron.bbradley@gmail.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
    • David Howells's avatar
      mn10300: add the MN10300/AM33 architecture to the kernel · b920de1b
      David Howells authored
      Add architecture support for the MN10300/AM33 CPUs produced by MEI to the
      This patch also adds board support for the ASB2303 with the ASB2308 daughter
      board, and the ASB2305.  The only processor supported is the MN103E010, which
      is an AM33v2 core plus on-chip devices.
      [akpm@linux-foundation.org: nuke cvs control strings]
      Signed-off-by: default avatarMasakazu Urade <urade.masakazu@jp.panasonic.com>
      Signed-off-by: default avatarKoichi Yasutake <yasutake.koichi@jp.panasonic.com>
      Signed-off-by: default avatarDavid Howells <dhowells@redhat.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
  2. 07 Feb, 2008 2 commits
  3. 06 Feb, 2008 4 commits
  4. 05 Feb, 2008 3 commits
    • Carlos Corbacho's avatar
      tc1100-wmi: Add driver for HP Compaq TC1100 Tablets · dd8cd779
      Carlos Corbacho authored
      This is based on the 2004 out-of-tree work of Jamey Hicks, to add
      support via WMI for controlling the jog dial and wireless on these
      Original release
      As per Joshua Wise's comments, change bluetooth to jogdial (an error from
      the original driver).
      Signed-off-by: default avatarCarlos Corbacho <carlos@strangeworlds.co.uk>
      CC: Matthew Garrett <mjg59@srcf.ucam.org>
      CC: Jamey Hicks <jamey.hicks@nokia.com>
      CC: Joshua Wise <joshua@joshuawise.com>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
    • Carlos Corbacho's avatar
      acer-wmi: Add driver for newer Acer laptops · 745a5d21
      Carlos Corbacho authored
      This is a driver for newer Acer (and Wistron) laptops. It adds wireless
      radio and bluetooth control, and on some laptops, exposes the mail LED and
      LCD backlight.
      * Initial release
      * Replace left over ACPI references with WMI
      * Add GUID based autoloading (depends on future work to WMI)
      * Add DMI based autoloading (backup solution until WMI sysfs/ class
        work is available)
      * Checkpatch fixes
      * Add new EC quirks for Aspire 3100 & 5100, and Extensa 5220
      * Simplified internal handling of WMID and AMW0 devices
      * Add autodetection for bluetooth and maximum brightness on AMW0 V2 and
        WMID laptops.
      * Add EC quirk for Medion MD 98000
      * Add autodetection for AMW0, and mail LED on AMW0 and AMW0 V2.
      * Improve error handling
      * Fix AMW0 V2 bluetooth and wireless, by using both WMID and AMW0 methods
        to ensure that the correct value is always set.
      * Fix 'use before initialisation' bug with quirks.
      * Fix bug on AMW0 where acer-wmi would exit if a mail LED was not
      * Add Acer Aspire 9110 mail LED support
      * Fix section mismatch warnings
      Signed-off-by: default avatarCarlos Corbacho <carlos@strangeworlds.co.uk>
      CC: Matthew Garrett <mjg59@srcf.ucam.org>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
    • Carlos Corbacho's avatar
      ACPI: WMI: Add ACPI-WMI mapping driver · bff431e4
      Carlos Corbacho authored
      The following is an implementation of the Windows Management
      Instrumentation (WMI) ACPI interface mapper (PNP0C14).
      What it does:
      Parses the _WDG method and exports functions to process WMI method calls,
      data block query/ set commands (both based on GUID) and does basic event
      How: WMI presents an in kernel interface here (essentially, a minimal
      wrapper around ACPI)
      (const char *guid assume the 36 character ASCII representation of
      a GUID - e.g. 67C3371D-95A3-4C37-BB61-DD47B491DAAB)
      wmi_evaluate_method(const char *guid, u8 instance, u32 method_id,
      const struct acpi_buffer *in, struct acpi_buffer *out)
      wmi_query_block(const char *guid, u8 instance,
      struct acpi_buffer *out)
      wmi_set_block(const char *guid, u38 instance,
      const struct acpi_buffer *in)
      wmi_install_notify_handler(acpi_notify_handler handler);
      wmi_get_event_data(u32 event, struct acpi_buffer *out)
      wmi_has_guid(const char guid*)
      wmi_has_guid() is a helper function to find if a GUID exists or not on the
      system (a quick and easy way for WMI dependant drivers to see if the
      the method/ block they want exists, since GUIDs are supposed to be unique).
      Event handling - allow a WMI based driver to register a notifier handler
      for each GUID with WMI. When a notification is sent to a GUID in WMI, the
      handler registered with WMI is then called (it is left to the caller to
      ask for the WMI event data associated with the GUID, if needed).
      What it won't do:
      Unicode - The MS article[1] calls for converting between ASCII and Unicode (or
      vice versa) if a GUID is marked as "string". This is left up to the calling
      Handle a MOF[1] - the WMI mapper just exports methods, data and events to
      userspace. MOF handling is down to userspace.
      Userspace interface - this will be added later.
      [1] http://www.microsoft.com/whdc/system/pnppwr/wmi/wmi-acpi.mspx
      v1 (2007-10-02):
      * Initial release
      v2 (2007-10-05):
      * Cleaned up code - split up super "wmi_evaluate_block" -> each external
        symbol now handles its own ACPI calls, rather than handing off to
        a "super" method (and in turn, is a lot simpler to read)
      * Added a find_guid() symbol - return true if a given GUID exists on
        the system
      * wmi_* functions now return type acpi_status (since they are just
        fancy wrappers around acpi_evaluate_object())
      * Removed extra debug code
      v3 (2007-10-27)
      * More code clean up - now passes checkpatch.pl
      * Change data block calls - ref MS spec, method ID is not required for
        them, so drop it from the function parameters.
      * Const'ify guid in the function call parameters.
      * Fix _WDG buffer handling - copy the data to our own private structure.
      * Change WMI from tristate to bool - otherwise the external functions are
        not exported in linux/acpi.h if you try to build WMI as a module.
      * Fix more flag comparisons.
      * Add a maintainers entry - since I wrote this, I should take the blame
        for it.
      v4 (2007-10-30)
      * Add missing brace from after fixing checkpatch errors.
      * Rewrote event handling - allow external drivers to register with WMI to
        handle WMI events
      * Clean up flags and sanitise flag handling
      v5 (2007-11-03)
      * Add sysfs interface for userspace. Export events over netlink again.
      * Remove module left overs, fully convert to built-in driver.
      * Tweak in-kernel API to use u8 for instance, since this is what the GUID
        blocks use (so instance cannot be greater than u8).
      * Export wmi_get_event_data() for in kernel WMI drivers.
      v6 (2007-11-07)
      * Split out userspace into a different patch
      v7 (2007-11-20)
      * Fix driver to handle multiple PNP0C14 devices - store all GUIDs using
        the kernel's built in list functions, and just keep adding to the list
        every time we handle a PNP0C14 devices - GUIDs will always be unique,
        and WMI callers do not know or care about different devices.
      * Change WMI event handler registration to use its' own event handling
        struct; we should not pass an acpi_handle down to any WMI based drivers
        - they should be able to function with only the calls provided in WMI.
      * Update my e-mail address
      v8 (2007-11-28)
      * Convert back to a module.
      * Update Kconfig to default to building as a module.
      * Remove an erroneous printk.
      * Simply comments for string flag (since we now leave the handling to the
      v9 (2007-12-07)
      * Add back missing MODULE_DEVICE_TABLE for autoloading
      * Checkpatch fixes
      v10 (2007-12-12)
      * Workaround broken GUIDs declared expensive without a WCxx method.
      * Minor cleanups
      v11 (2007-12-17)
      * More fixing for broken GUIDs declared expensive without a WCxx method.
      * Add basic EmbeddedControl region handling.
      v12 (2007-12-18)
      * Changed EC region handling code, as per Alexey's comments.
      v13 (2007-12-27)
      * Changed event handling so that we can have one event handler registered
        per GUID, as per Matthew Garrett's suggestion.
      v14 (2008-01-12)
      * Remove ACPI debug statements
      v15 (2008-02-01)
      * Replace two remaining 'x == NULL' type tests with '!x'
      v16 (2008-02-05)
      * Change MAINTAINERS entry, as I am not, and never have been, paid to work
        on WMI
      * Remove 'default' line from Kconfig
      Signed-off-by: default avatarCarlos Corbacho <carlos@strangeworlds.co.uk>
      CC: Matthew Garrett <mjg59@srcf.ucam.org>
      CC: Alexey Starikovskiy <aystarik@gmail.com>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
  5. 04 Feb, 2008 2 commits
  6. 03 Feb, 2008 5 commits
  7. 01 Feb, 2008 2 commits
  8. 31 Jan, 2008 2 commits
  9. 30 Jan, 2008 1 commit
  10. 28 Jan, 2008 6 commits
  11. 25 Jan, 2008 1 commit
  12. 14 Jan, 2008 1 commit
  13. 12 Jan, 2008 2 commits
  14. 11 Jan, 2008 1 commit
    • Swen Schillig's avatar
      [SCSI] zfcp: update MAINTAINERS · 0033bb47
      Swen Schillig authored
      we are planning a major rewrite of the zfcp driver,
      meaning that a lot of patches will hit the mailing-list in the near future.
      Since I can't support this additional work-load along with my other
      responsibilities we are shifting the maintainership to
      Christof Schmitt as the maintainer and
      Martin Peschke as the co-maintainer.
      Please support the two in providing us a new and more stable
      zfcp environment.
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@HansenPartnership.com>
  15. 09 Jan, 2008 1 commit
  16. 08 Jan, 2008 1 commit
  17. 24 Dec, 2007 1 commit
  18. 23 Dec, 2007 2 commits