[leaf-devel] Wifi 802ac card
Hi all, i'm looking for a 802ac wifi card in mini pcie format that was compatible with our leaf kernel. Do you have see something that works ? Regards, Yves -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] commits for 5.1.3
Yes thanks a lot david for the documentation you havec made in the wiki. Regards, Yves Le 27 déc. 2014 à 00:24, kp kirchdoerfer kap...@users.sourceforge.net a écrit : Hi David - nice to see you! If you want to see your commits in 5.13, and I bet you will, you have to commit to the maint branch instead of the master branch. maint is for 5.1. master for 5.2 - based on a new kernel and so on kp btw. interesting reading your new wiki additions -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] b43 firmware
Hi folks I am playing with the b43 driver and it appears there is firmware needed to usre this card. This firmware is not included in the firmware.tgz tarball. I built b43-fwcutter and extracted the firmware from broadcom's binary distribution. root@leafbuilder:/home/mega/leaf/firmware/broadcom/fwdir# find b43 b43 b43/ucode16_sslpn.fw b43/sslpn2bsinitvals19.fw b43/lp0initvals13.fw b43/ucode15.fw . Now a few questions pop up 1) where is the firmware loaded at boot I could not find any code in linuxrc to load firmware. Would it make sense to package it into a .lrp file? 2) What is the correct path to include this firmware in the firmware tarball The local path is b43, so I assume it could be either broadcom or broadcom/b43 cheers Erich smime.p7s Description: S/MIME Cryptographic Signature -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] images and valgrind
Hi all; as you mave seen; I've released beta1 for Bering-uClibc 5.1.3 today. With the addition of valgrind.lrp the images are about 110MB, where valgrind.lrp with 13MB is more then 10% of the image size. As valgrind is only useful for developers, I thought about restrictions for images, where developer-only lrp's are not shipped by default. Developers using valgrind and other packages like kdebuginfo (2MB), oprofile(2,8MB), will be able to build themself from toolchain. What about a using blacklist in buildimages, and who can implement it? Thoughts? kp -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] images and valgrind
Hi. Yes, valgrind is mostly useful for developers (I ported it due to bird crashes diagnostics). But oprofile with kernel debuginfo is widely used, for ex., for high-load routers tuning. 29.12.2014 20:09, kp kirchdoerfer пишет: Hi all; as you mave seen; I've released beta1 for Bering-uClibc 5.1.3 today. With the addition of valgrind.lrp the images are about 110MB, where valgrind.lrp with 13MB is more then 10% of the image size. As valgrind is only useful for developers, I thought about restrictions for images, where developer-only lrp's are not shipped by default. Developers using valgrind and other packages like kdebuginfo (2MB), oprofile(2,8MB), will be able to build themself from toolchain. What about a using blacklist in buildimages, and who can implement it? Thoughts? kp -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] commits for 5.1.3
Hi Yves, kp, I've just switched to a new ISP and I'm using PPPoE for the first time so I've updated the relevant sections of the Wiki (along with upgrading dhcpcd to add IPv6 support). My new ISP provides native IPv6 in addition to IPv4, and IPv6 via PPP isn't as straightforward as with IPv4, so I've documented how I got it to work. kp and I have had some discussions off-list due to some problems with the mailing list server. I'm going to do some more testing of the new dhcpcd (and likely a further update) so it will probably go into 5.2. I have limited time available to devote to Bering-uClibc development these days but I am happy to ensure that the Wiki is up-to-date for the configuration options I rely on. David On 29 Dec 2014, at 14:13, Yves Blusseau wrote: Yes thanks a lot david for the documentation you havec made in the wiki. Regards, Yves Le 27 déc. 2014 à 00:24, kp kirchdoerfer kap...@users.sourceforge.net a écrit : Hi David - nice to see you! If you want to see your commits in 5.13, and I bet you will, you have to commit to the maint branch instead of the master branch. maint is for 5.1. master for 5.2 - based on a new kernel and so on kp btw. interesting reading your new wiki additions -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] images and valgrind
Hi KP Am 29.12.2014 um 19:09 schrieb kp kirchdoerfer: Hi all; as you mave seen; I've released beta1 for Bering-uClibc 5.1.3 today. With the addition of valgrind.lrp the images are about 110MB, where valgrind.lrp with 13MB is more then 10% of the image size. As valgrind is only useful for developers, I thought about restrictions for images, where developer-only lrp's are not shipped by default. Developers using valgrind and other packages like kdebuginfo (2MB), oprofile(2,8MB), will be able to build themself from toolchain. What about a using blacklist in buildimages, and who can implement it? Thoughts? Leave it out from the standard images. Developers have sufficient skills to add them from a complete iso image. cheers Erich smime.p7s Description: S/MIME Cryptographic Signature -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
