26 Jul, 2008

1 commit


10 Jul, 2008

2 commits

  • 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: David Woodhouse

    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: David Woodhouse

    David Woodhouse
     

29 Apr, 2008

1 commit

  • Before requesting firmware, printk a message saying what we're requesting. This
    makes it easier to see what's going on, and provides an explanation for the
    huge silent delay that one would otherwise get after accidentally building
    ipw2200 as a non-module.

    Cc: Greg KH
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Ciaran McCreesh
     

20 Apr, 2008

1 commit


08 Feb, 2008

1 commit

  • This reverts commit 109f0e93b6b728f03c1eb4af02bc25d71b646c59.

    The original patch breaks BIOS updates on all Dell machines. The path to
    the firmware file for the dell_rbu driver changes, which breaks all of
    the userspace tools which rely on it.

    Note that this patch re-introduces a problem with i2c name collision
    that was previously fixed by this patch.

    Signed-off-by: Michael E Brown
    Signed-off-by: Greg Kroah-Hartman

    Michael E Brown
     

13 Oct, 2007

2 commits

  • following patch fixes the i2c name collision with i2c-dev.

    http://mcentral.de/wiki/index.php/Bugtracker#i2c_core_problem

    This issue has been experienced with em28xx and saa7133 based devices.
    I discussed that problem with Jean Delvare a while ago and he proposed
    to add a prefix to the class name.

    Signed-off-by: Markus Rechberger
    Acked-by: Marcel Holtmann
    Signed-off-by: Greg Kroah-Hartman

    Markus Rechberger
     
  • This changes the uevent buffer functions to use a struct instead of a
    long list of parameters. It does no longer require the caller to do the
    proper buffer termination and size accounting, which is currently wrong
    in some places. It fixes a known bug where parts of the uevent
    environment are overwritten because of wrong index calculations.

    Many thanks to Mathieu Desnoyers for finding bugs and improving the
    error handling.

    Signed-off-by: Kay Sievers
    Cc: Mathieu Desnoyers
    Cc: Cornelia Huck
    Signed-off-by: Greg Kroah-Hartman

    Kay Sievers
     

31 Jul, 2007

1 commit

  • Fix undocumented function parameters in PCI and drivers/base.

    Warning(linux-2.6.23-rc1//drivers/pci/pci.c:1526): No description found for parameter 'rq'
    Warning(linux-2.6.23-rc1//drivers/base/firmware_class.c:245): No description found for parameter 'bin_attr'

    Signed-off-by: Randy Dunlap
    Signed-off-by: Greg Kroah-Hartman

    Randy Dunlap
     

12 Jul, 2007

2 commits

  • 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: Zhang Rui
    Signed-off-by: Greg Kroah-Hartman

    Zhang Rui
     
  • 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: Tejun Heo
    Cc: Cornelia Huck
    Cc: Andrew Morton
    Signed-off-by: Greg Kroah-Hartman

    Tejun Heo
     

09 Jun, 2007

1 commit

  • Manuel Estrada Sainz passed away on May 9th 2004, his email account got
    deactivated. He was in charge of the firmware_class code, and still got
    CC'ed in recent discussions about it.

    Signed-off-by: Markus Rechberger
    Signed-off-by: Greg Kroah-Hartman

    Markus Rechberger
     

28 Apr, 2007

1 commit


08 Feb, 2007

1 commit


23 Dec, 2006

1 commit


02 Dec, 2006

1 commit


30 Sep, 2006

1 commit

  • Replace kernel_thread() call in drivers/base/firmware_class.c with
    kthread_create() since kernel_thread() is deprecated in drivers.

    Signed-off-by: Sukadev Bhattiprolu
    Cc: Cedric Le Goater
    Cc: Serge E. Hallyn
    Cc: Dave Hansen
    Cc: Manuel Estrada Sainz
    Acked-by: Marcel Holtmann
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Sukadev Bhattiprolu
     

27 Sep, 2006

1 commit

  • 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: Shaohua Li
    Acked-by: Tigran Aivazian
    Cc: Greg KH
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Shaohua Li
     

22 Jun, 2006

1 commit


22 May, 2006

1 commit

  • - remove the following global function that is both unused and
    unimplemented:
    - register_firmware()

    - make the following needlessly global function static:
    - firmware_class_uevent()

    Signed-off-by: Adrian Bunk
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Adrian Bunk
     

21 Mar, 2006

1 commit

  • 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: Jeff Moyer
    Signed-off-by: Andrew Morton
    Signed-off-by: Greg Kroah-Hartman

    Jeff Moyer
     

15 Jan, 2006

1 commit


12 Jan, 2006

1 commit

  • - Move capable() from sched.h to capability.h;

    - Use where capable() is used
    (in include/, block/, ipc/, kernel/, a few drivers/,
    mm/, security/, & sound/;
    many more drivers/ to go)

    Signed-off-by: Randy Dunlap
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Randy.Dunlap
     

05 Jan, 2006

1 commit


14 Nov, 2005

1 commit


31 Oct, 2005

1 commit


13 Sep, 2005

1 commit


08 Sep, 2005

1 commit


29 Jun, 2005

1 commit


19 Apr, 2005

1 commit

  • On Tue, 2005-03-15 at 09:25 +0100, Hannes Reinecke wrote:
    > The current implementation of the firmware class breaks a fundamental
    > assumption in udevd: that the physical device can be initialised fully
    > prior to executing the next event for that device.

    Here we add a TIMEOUT value to the hotplug environment of the firmware
    requesting event. I will adapt udevd not to wait for anything else, if
    it finds a TIMEOUT key.

    Signed-off-by: Kay Sievers
    Signed-off-by: Greg Kroah-Hartman

    kay.sievers@vrfy.org
     

17 Apr, 2005

1 commit

  • 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!

    Linus Torvalds