I've duplicated bug 1051095 with this one, since they both ask for microcode for family 10h-14h and 15h processors. With regard to the question of "How does Intel do it", they have a license that is included in /usr/share/doc/intel-microcode/copyright that allows redistribution.
With regard to comment #7, the email granting us permission to redistribute still doesn't give us a license to distribute it under. For example, you probably want to say the code remains copyright AMD, and disclaim warranty. We would need such text for either #1 or #2. To see other licenses already in linux-firmware, you could clone the linux-firmware git tree and see the LICENSE.$vendor files within.
With regard to #3 that would mean that users would do an apt-get linux-firmware-nonfree to get the microcode, but personally I'd rather not go that route.
I've duplicated bug 1051095 with this one, since they both ask for microcode for family 10h-14h and 15h processors. With regard to the question of "How does Intel do it", they have a license that is included in /usr/share/ doc/intel- microcode/ copyright that allows redistribution.
With regard to comment #7, the email granting us permission to redistribute still doesn't give us a license to distribute it under. For example, you probably want to say the code remains copyright AMD, and disclaim warranty. We would need such text for either #1 or #2. To see other licenses already in linux-firmware, you could clone the linux-firmware git tree and see the LICENSE.$vendor files within.
With regard to #3 that would mean that users would do an apt-get linux-firmware- nonfree to get the microcode, but personally I'd rather not go that route.
https:/ /git.kernel. org/?p= linux/kernel/ git/dwmw2/ linux-firmware. git;a=tree /git.kernel. org/?p= linux/kernel/ git/dwmw2/ linux-firmware. git;a=blob; f=LICENCE. atheros_ firmware
https:/