An error occurred fetching the project authors.
  1. 28 Jul, 2009 1 commit
  2. 12 Jul, 2009 1 commit
  3. 08 Jul, 2009 1 commit
  4. 16 Jun, 2009 4 commits
  5. 15 May, 2009 1 commit
    • David Woodhouse's avatar
      firmware: speed up request_firmware(), v3 · 6e03a201
      David Woodhouse authored
      Rather than calling vmalloc() repeatedly to grow the firmware image as
      we receive data from userspace, just allocate and fill individual pages.
      Then vmap() the whole lot in one go when we're done.
      
      A quick test with a 337KiB iwlagn firmware shows the time taken for
      request_firmware() going from ~32ms to ~5ms after I apply this patch.
      
      [v2: define PAGE_KERNEL_RO as PAGE_KERNEL where necessary, use min_t()]
      [v3: kunmap() takes the struct page *, not the virtual address]
      Signed-off-by: default avatarDavid Woodhouse <David.Woodhouse@intel.com>
      Tested-by: default avatarSachin Sant <sachinp@in.ibm.com>
      6e03a201
  6. 24 Mar, 2009 1 commit
    • Ming Lei's avatar
      Driver core: implement uevent suppress in kobject · f67f129e
      Ming Lei authored
      This patch implements uevent suppress in kobject and removes it
      from struct device, based on the following ideas:
      
      1,Uevent sending should be one attribute of kobject, so suppressing it
      in kobject layer is more natural than in device layer. By this way,
      we can do it for other objects embedded with kobject.
      
      2,It may save several bytes for each instance of struct device.(On my
      omap3(32bit ARM) based box, can save 8bytes per device object)
      
      This patch also introduces dev_set|get_uevent_suppress() helpers to
      set and query uevent_suppress attribute in case to help kobject
      as private part of struct device in future.
      
      [This version is against the latest driver-core patch set of Greg,please
      ignore the last version.]
      Signed-off-by: default avatarMing Lei <tom.leiming@gmail.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      f67f129e
  7. 06 Jan, 2009 1 commit
  8. 16 Oct, 2008 1 commit
  9. 25 Jul, 2008 1 commit
  10. 10 Jul, 2008 2 commits
    • David Woodhouse's avatar
      firmware: allow firmware files to be built into kernel image · 5658c769
      David Woodhouse authored
      Some drivers have their own hacks to bypass the kernel's firmware loader
      and build their firmware into the kernel; this renders those unnecessary.
      
      Other drivers don't use the firmware loader at all, because they always
      want the firmware to be available. This allows them to start using the
      firmware loader.
      
      A third set of drivers already use the firmware loader, but can't be
      used without help from userspace, which sometimes requires an initrd.
      This allows them to work in a static kernel.
      Signed-off-by: default avatarDavid Woodhouse <dwmw2@infradead.org>
      5658c769
    • David Woodhouse's avatar
      firmware: make fw->data const · b7a39bd0
      David Woodhouse authored
      In preparation for supporting firmware files linked into the static
      kernel, make fw->data const to ensure that users aren't modifying it (so
      that we can pass a pointer to the original in-kernel copy, rather than
      having to copy it).
      Signed-off-by: default avatarDavid Woodhouse <dwmw2@infradead.org>
      b7a39bd0
  11. 29 Apr, 2008 1 commit
  12. 20 Apr, 2008 1 commit
  13. 07 Feb, 2008 1 commit
  14. 12 Oct, 2007 2 commits
  15. 30 Jul, 2007 1 commit
  16. 11 Jul, 2007 2 commits
    • Zhang Rui's avatar
      sysfs: add parameter "struct bin_attribute *" in .read/.write methods for sysfs binary attributes · 91a69029
      Zhang Rui authored
      Well, first of all, I don't want to change so many files either.
      
      What I do:
      Adding a new parameter "struct bin_attribute *" in the
      .read/.write methods for the sysfs binary attributes.
      
      In fact, only the four lines change in fs/sysfs/bin.c and
      include/linux/sysfs.h do the real work.
      But I have to update all the files that use binary attributes
      to make them compatible with the new .read and .write methods.
      I'm not sure if I missed any. :(
      
      Why I do this:
      For a sysfs attribute, we can get a pointer pointing to the
      struct attribute in the .show/.store method,
      while we can't do this for the binary attributes.
      I don't know why this is different, but this does make it not
      so handy to use the binary attributes as the regular ones.
      So I think this patch is reasonable. :)
      
      Who benefits from it:
      The patch that exposes ACPI tables in sysfs
      requires such an improvement.
      All the table binary attributes share the same .read method.
      Parameter "struct bin_attribute *" is used to get
      the table signature and instance number which are used to
      distinguish different ACPI table binary attributes.
      
      Without this parameter, we need to offer different .read methods
      for different ACPI table binary attributes.
      This is impossible as there are various ACPI tables on different
      platforms, and we don't know what they are until they are loaded.
      Signed-off-by: default avatarZhang Rui <rui.zhang@intel.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      91a69029
    • Tejun Heo's avatar
      sysfs: kill unnecessary attribute->owner · 7b595756
      Tejun Heo authored
      sysfs is now completely out of driver/module lifetime game.  After
      deletion, a sysfs node doesn't access anything outside sysfs proper,
      so there's no reason to hold onto the attribute owners.  Note that
      often the wrong modules were accounted for as owners leading to
      accessing removed modules.
      
      This patch kills now unnecessary attribute->owner.  Note that with
      this change, userland holding a sysfs node does not prevent the
      backing module from being unloaded.
      
      For more info regarding lifetime rule cleanup, please read the
      following message.
      
        http://article.gmane.org/gmane.linux.kernel/510293
      
      (tweaked by Greg to not delete the field just yet, to make it easier to
      merge things properly.)
      Signed-off-by: default avatarTejun Heo <htejun@gmail.com>
      Cc: Cornelia Huck <cornelia.huck@de.ibm.com>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      7b595756
  17. 08 Jun, 2007 1 commit
  18. 27 Apr, 2007 1 commit
  19. 07 Feb, 2007 1 commit
  20. 22 Dec, 2006 1 commit
  21. 01 Dec, 2006 1 commit
  22. 29 Sep, 2006 1 commit
  23. 27 Sep, 2006 1 commit
    • Shaohua Li's avatar
      [PATCH] x86 microcode: using request_firmware to pull microcode · a30a6a2c
      Shaohua Li authored
      Using request_firmware to pull ucode from userspace, so we don't need the
      application 'microcode_ctl' to assist.  We name each ucode file according
      to CPU's info as intel-ucode/family-model-stepping.  In this way we could
      split ucode file as small one.  This has a lot of advantages such as
      selectively update and validate microcode for specific models, better
      manage microcode file, easily write tools for administerators and so on.
      with the changes, we should put all intel-ucode/xx-xx-xx microcode files
      into the firmware dir (I had a tool to split previous big data file into
      small one and later we will release new style data file).  The init script
      should be changed to just loading the driver without unloading
      Signed-off-by: default avatarShaohua Li <shaohua.li@intel.com>
      Acked-by: default avatarTigran Aivazian <tigran@veritas.com>
      Cc: Greg KH <greg@kroah.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      a30a6a2c
  24. 21 Jun, 2006 1 commit
  25. 21 May, 2006 1 commit
  26. 20 Mar, 2006 1 commit
    • Jeff Moyer's avatar
      [PATCH] firmware: fix BUG: in fw_realloc_buffer · 30560ba6
      Jeff Moyer authored
      The fw_realloc_buffer routine does not handle an increase in buffer size of
      more than 4k.  It's not clear to me why it expects that it will only get an
      extra 4k of data.  The attached patch modifies fw_realloc_buffer to vmalloc
      as much memory as is requested, instead of what we previously had + 4k.
      
      I've tested this on my laptop, which would crash occaisionally on boot
      without the patch.  With the patch, it hasn't crashed, but I can't be
      certain that this code path is exercised.
      Signed-off-by: default avatarJeff Moyer <jmoyer@redhat.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      30560ba6
  27. 15 Jan, 2006 1 commit
  28. 12 Jan, 2006 1 commit
  29. 05 Jan, 2006 1 commit
  30. 14 Nov, 2005 1 commit
  31. 31 Oct, 2005 1 commit
  32. 13 Sep, 2005 1 commit
  33. 07 Sep, 2005 1 commit
  34. 29 Jun, 2005 1 commit