Revision: 7528
http://sourceforge.net/p/ipcop/svn/7528
Author: owes
Date: 2014-05-10 21:00:14 +0000 (Sat, 10 May 2014)
Log Message:
-----------
rtl8169 wants to load small firmware patches, seems to works without but
include anyway.
Modified Paths:
--------------
ipcop/trunk/config/rootfiles/common/linux-firmware
ipcop/trunk/lfs/linux-firmware
Modified: ipcop/trunk/config/rootfiles/common/linux-firmware
===================================================================
--- ipcop/trunk/config/rootfiles/common/linux-firmware 2014-05-10 08:10:19 UTC
(rev 7527)
+++ ipcop/trunk/config/rootfiles/common/linux-firmware 2014-05-10 21:00:14 UTC
(rev 7528)
@@ -1,2 +1,14 @@
#lib/firmware/bnx2
lib/firmware/bnx2/bnx2-mips-09-6.2.1b.fw
+#lib/firmware/rtl_nic
+lib/firmware/rtl_nic/rtl8105e-1.fw
+lib/firmware/rtl_nic/rtl8168d-1.fw
+lib/firmware/rtl_nic/rtl8168d-2.fw
+lib/firmware/rtl_nic/rtl8168e-1.fw
+lib/firmware/rtl_nic/rtl8168e-2.fw
+lib/firmware/rtl_nic/rtl8168e-3.fw
+lib/firmware/rtl_nic/rtl8168f-1.fw
+lib/firmware/rtl_nic/rtl8168f-2.fw
+lib/firmware/rtl_nic/rtl8168g-1.fw
+lib/firmware/rtl_nic/rtl8168g-2.fw
+lib/firmware/rtl_nic/rtl8168g-3.fw
Modified: ipcop/trunk/lfs/linux-firmware
===================================================================
--- ipcop/trunk/lfs/linux-firmware 2014-05-10 08:10:19 UTC (rev 7527)
+++ ipcop/trunk/lfs/linux-firmware 2014-05-10 21:00:14 UTC (rev 7528)
@@ -99,9 +99,11 @@
# TODO
# We will need to walk the driver tree and find those drivers we build
with 'missing' firmware blobs.
- # Q&D hack to copy a single firmware blob that's already been
identified as missing
+ # Q&D hack to copy firmware blobs that've already been identified as
missing
mkdir -p /lib/firmware/bnx2
cp -p $(DIR_APP)/bnx2/bnx2-mips-09-6.2.1b.fw /lib/firmware/bnx2
+ mkdir -p /lib/firmware/rtl_nic
+ cp -p $(DIR_APP)/rtl_nic/{rtl8105e-1.fw,rtl8168*} /lib/firmware/rtl_nic
# do not remove for now
#@rm -rf $(DIR_APP)
This was sent by the SourceForge.net collaborative development platform, the
world's largest Open Source development site.
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Ipcop-svn mailing list
Ipcop-svn@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipcop-svn
