1. 10 7月, 2008 2 次提交
    • D
      firmware: allow firmware files to be built into kernel image · 5658c769
      David Woodhouse 提交于
      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: NDavid Woodhouse <dwmw2@infradead.org>
      5658c769
    • D
      firmware: make fw->data const · b7a39bd0
      David Woodhouse 提交于
      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: NDavid Woodhouse <dwmw2@infradead.org>
      b7a39bd0
  2. 29 4月, 2008 1 次提交
  3. 20 4月, 2008 1 次提交
  4. 08 2月, 2008 1 次提交
  5. 13 10月, 2007 2 次提交
  6. 31 7月, 2007 1 次提交
  7. 12 7月, 2007 2 次提交
    • Z
      sysfs: add parameter "struct bin_attribute *" in .read/.write methods for sysfs binary attributes · 91a69029
      Zhang Rui 提交于
      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: NZhang Rui <rui.zhang@intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      91a69029
    • T
      sysfs: kill unnecessary attribute->owner · 7b595756
      Tejun Heo 提交于
      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: NTejun Heo <htejun@gmail.com>
      Cc: Cornelia Huck <cornelia.huck@de.ibm.com>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      7b595756
  8. 09 6月, 2007 1 次提交
  9. 28 4月, 2007 1 次提交
  10. 08 2月, 2007 1 次提交
  11. 23 12月, 2006 1 次提交
  12. 02 12月, 2006 1 次提交
  13. 30 9月, 2006 1 次提交
  14. 27 9月, 2006 1 次提交
    • S
      [PATCH] x86 microcode: using request_firmware to pull microcode · a30a6a2c
      Shaohua Li 提交于
      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: NShaohua Li <shaohua.li@intel.com>
      Acked-by: NTigran Aivazian <tigran@veritas.com>
      Cc: Greg KH <greg@kroah.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      a30a6a2c
  15. 22 6月, 2006 1 次提交
  16. 22 5月, 2006 1 次提交
  17. 21 3月, 2006 1 次提交
    • J
      [PATCH] firmware: fix BUG: in fw_realloc_buffer · 30560ba6
      Jeff Moyer 提交于
      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: NJeff Moyer <jmoyer@redhat.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      30560ba6
  18. 15 1月, 2006 1 次提交
  19. 12 1月, 2006 1 次提交
  20. 05 1月, 2006 1 次提交
  21. 14 11月, 2005 1 次提交
  22. 31 10月, 2005 1 次提交
  23. 13 9月, 2005 1 次提交
  24. 08 9月, 2005 1 次提交
  25. 29 6月, 2005 1 次提交
  26. 19 4月, 2005 1 次提交
  27. 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