[lkml]   [2006]   [Jul]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RFC][PATCH 1/2] firmware version management: add firmware_version()
    On Sunday 09 July 2006 17:25, you wrote:
    > > yes it does. bcm43xx asks userspace to upload firmware (via
    > > request_firmware() ) and a userspace app (udev most of the time) will
    > > upload it. That app, eg udev, can do the md5sum and checking it against
    > > a list of "known good" firmwares. Voila problem solved ;)
    > I see. It's an interesting way that I didn't noticed.
    > Thanks for the guidance.

    Nono, stop. Not too fast. :)
    Where is this "list of "known good" firmwares" actually stored?
    In userspace (udev)? That would be guaranteed to be out of sync
    with the driver.
    As said previously, we need to tie a specific driver version to
    one or more firmware versions. So the only sane place to put the
    MD5 sums (or whatever) in, is the driver. Otherwise it will not
    be in sync.

    So, if we want to verify the checksum in userspace, we must
    export a list of known good checksums to userspace.
    Could be done through a sysfs file with a list of checksums.

    cat /sys/foo/device/acceptable_firmwares
    MD5: cbd8320a2a458d1cfad5420c6fa6a823
    MD5: b812d7dd3d3b88fbc113e0bbf7e07c8d

    That would also allow other hash algorithms in future
    while providing backward compat.

    Greetings Michael.
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-07-09 21:09    [W:1.047 / U:56.596 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site