linux-kernel - linux-firmware tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <BANLkTimmr=rD84cAkQ2xGsG7PccxQKKqVg@mail.gmail.com>
Date:	Mon, 2 May 2011 11:57:35 -0700
From:	Mike Waychison <mikew@...gle.com>
To:	david.woodhouse@...el.com
Cc:	linux-kernel@...r.kernel.org
Subject: linux-firmware tree

Hi David,

I'm trying to understand the purpose of the linux-firmware tree.
Forgive me if this is a stupid question, but the only information
about it I could find was your original post back in 2008:
https://lwn.net/Articles/294308/

Will the Linux kernel sources always continue to have the firmware
blobs and the linux-firmware tree is only for those users of distros
that strip the firmware out?

I'm trying to understand if there would ever be a need to integrate
the linux-firmware tree into our builds (we build a derivative of
Linus' tree).

Thanks,

Mike Waychison
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/