<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for electrons on radio</title>
	<atom:link href="http://www.electronsonradio.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.electronsonradio.com</link>
	<description>a blog about math, science and engineering</description>
	<lastBuildDate>Tue, 07 Feb 2012 22:12:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Building Ångström for the BeagleBoard using OpenEmbedded by Lab 2/7 &#124; Autonomous Quadrocopter</title>
		<link>http://www.electronsonradio.com/2011/04/building-angstrom-for-the-beagleboard-using-openembedded/#comment-221</link>
		<dc:creator>Lab 2/7 &#124; Autonomous Quadrocopter</dc:creator>
		<pubDate>Tue, 07 Feb 2012 22:12:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.electronsonradio.com/?p=43#comment-221</guid>
		<description>[...] a while I found a guide to using OpenEmbedded to install Angstrom on the BeagleBoard which had a lot of good information on it. I plan to utilize the information in this guide on [...]</description>
		<content:encoded><![CDATA[<p>[...] a while I found a guide to using OpenEmbedded to install Angstrom on the BeagleBoard which had a lot of good information on it. I plan to utilize the information in this guide on [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Intro to basic cross-compiling for the BeagleBoard by Dave</title>
		<link>http://www.electronsonradio.com/2011/04/intro-to-basic-cross-compiling-for-the-beagleboard/#comment-212</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 18 Jan 2012 06:08:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.electronsonradio.com/?p=36#comment-212</guid>
		<description>This question seems to be asked a lot, is this for a class?
I personally haven&#039;t built opencv, but to build your own applications for the BeagleBoard you&#039;ll need a development environment like the Narciss SDK or OpenEmbedded which contains opencv libraries which you can link. I would search the Angstrom / BeagleBoard mailing lists as you&#039;ll find this is a very popular topic.</description>
		<content:encoded><![CDATA[<p>This question seems to be asked a lot, is this for a class?<br />
I personally haven&#8217;t built opencv, but to build your own applications for the BeagleBoard you&#8217;ll need a development environment like the Narciss SDK or OpenEmbedded which contains opencv libraries which you can link. I would search the Angstrom / BeagleBoard mailing lists as you&#8217;ll find this is a very popular topic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Intro to basic cross-compiling for the BeagleBoard by nikhila</title>
		<link>http://www.electronsonradio.com/2011/04/intro-to-basic-cross-compiling-for-the-beagleboard/#comment-211</link>
		<dc:creator>nikhila</dc:creator>
		<pubDate>Wed, 18 Jan 2012 05:52:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.electronsonradio.com/?p=36#comment-211</guid>
		<description>hi

I&#039;m a newbee on the beagleboard and the software toolchain flow. I need to port Angstrom/Ubuntu on the Beagle board and run opencv on it. 

Should I use the Narciss SDK or is there any alternative to it? I need step by step instructions on installing opencv.

Till now, I&#039;ve got angstrom running using a prebuilt image from the beagleboard website.

I&#039;m stuck. Can u please help me?</description>
		<content:encoded><![CDATA[<p>hi</p>
<p>I&#8217;m a newbee on the beagleboard and the software toolchain flow. I need to port Angstrom/Ubuntu on the Beagle board and run opencv on it. </p>
<p>Should I use the Narciss SDK or is there any alternative to it? I need step by step instructions on installing opencv.</p>
<p>Till now, I&#8217;ve got angstrom running using a prebuilt image from the beagleboard website.</p>
<p>I&#8217;m stuck. Can u please help me?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BeagleBoard: DVI Video modes by Josh Palmer</title>
		<link>http://www.electronsonradio.com/2011/02/beagleboard-dvi-video-modes/#comment-205</link>
		<dc:creator>Josh Palmer</dc:creator>
		<pubDate>Sun, 01 Jan 2012 23:09:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.electronsonradio.com/?p=16#comment-205</guid>
		<description>Words cannot describe how excellent this post it. Thank you sir.</description>
		<content:encoded><![CDATA[<p>Words cannot describe how excellent this post it. Thank you sir.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Intro to basic cross-compiling for the BeagleBoard by Dave</title>
		<link>http://www.electronsonradio.com/2011/04/intro-to-basic-cross-compiling-for-the-beagleboard/#comment-204</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 28 Dec 2011 12:02:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.electronsonradio.com/?p=36#comment-204</guid>
		<description>I&#039;ve never tried to compile anything &lt;strong&gt;on&lt;/strong&gt; the BeagleBoard before. I know this doesn&#039;t answer your question, but if you want to make changes on the fly maybe a scripting language for your programs would be more appropriate- maybe even python? You could try to cross-compile GCC (ie using your desktop to compile to the ARM tagket), which is how the binaries in the OPKG repo would have been built. Openembedded has the package in its repo which would be easy to build. See &lt;a href=&quot;http://www.angstrom-distribution.org/repo/?pkgname=gcc&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve never tried to compile anything <strong>on</strong> the BeagleBoard before. I know this doesn&#8217;t answer your question, but if you want to make changes on the fly maybe a scripting language for your programs would be more appropriate- maybe even python? You could try to cross-compile GCC (ie using your desktop to compile to the ARM tagket), which is how the binaries in the OPKG repo would have been built. Openembedded has the package in its repo which would be easy to build. See <a href="http://www.angstrom-distribution.org/repo/?pkgname=gcc" rel="nofollow">here</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on cp210x usb to serial converter linux driver by Dave</title>
		<link>http://www.electronsonradio.com/2011/07/cp210x-usb-to-serial-converter-linux-driver/#comment-203</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 28 Dec 2011 11:47:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.electronsonradio.com/?p=90#comment-203</guid>
		<description>I&#039;m afraid I haven&#039;t experienced this problem before. Have you tried updating the drivers in the kernel?</description>
		<content:encoded><![CDATA[<p>I&#8217;m afraid I haven&#8217;t experienced this problem before. Have you tried updating the drivers in the kernel?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on cp210x usb to serial converter linux driver by Mike</title>
		<link>http://www.electronsonradio.com/2011/07/cp210x-usb-to-serial-converter-linux-driver/#comment-200</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 07 Dec 2011 04:18:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.electronsonradio.com/?p=90#comment-200</guid>
		<description>Have used these driver with a Device ID 10c4:ea70, it can connect initially, but when we disconnect and reconect again, it can not connect anymore. Do you encounter these problem before?
Please advise.</description>
		<content:encoded><![CDATA[<p>Have used these driver with a Device ID 10c4:ea70, it can connect initially, but when we disconnect and reconect again, it can not connect anymore. Do you encounter these problem before?<br />
Please advise.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Intro to basic cross-compiling for the BeagleBoard by Victor Aldecôa</title>
		<link>http://www.electronsonradio.com/2011/04/intro-to-basic-cross-compiling-for-the-beagleboard/#comment-199</link>
		<dc:creator>Victor Aldecôa</dc:creator>
		<pubDate>Tue, 06 Dec 2011 20:07:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.electronsonradio.com/?p=36#comment-199</guid>
		<description>Hi,
thank you very much for this post. It was very helpful.
I have a question... my BeagleBoard has no internet access, and I want to install gcc on it (not for full development, but in case I want to do little modifications on the code using vi). How do I do that?
For example, I needed to install lrzsz to easily transfer files to it, and what I did was install with opkg-target and copy the installed binaries from my PC to BeagleBoard&#039;s /usr/bin. But &quot;opkg-target install gcc&quot; downloaded a bunch of files and no binary. Should I copy the whole &quot;.../arm/arm-angstrom-linux-gnueabi&quot; folder?
The strange thing is that arm-angstrom-linux-gnueabi/bin/gcc is just a link to ../../bin/arm-angstrom-linux-gnueabi-gcc, which was compiled for AMD64, not for ARM.

Thank you in advance. Sorry for the long question, and I hope it isn&#039;t too much confusing.</description>
		<content:encoded><![CDATA[<p>Hi,<br />
thank you very much for this post. It was very helpful.<br />
I have a question&#8230; my BeagleBoard has no internet access, and I want to install gcc on it (not for full development, but in case I want to do little modifications on the code using vi). How do I do that?<br />
For example, I needed to install lrzsz to easily transfer files to it, and what I did was install with opkg-target and copy the installed binaries from my PC to BeagleBoard&#8217;s /usr/bin. But &#8220;opkg-target install gcc&#8221; downloaded a bunch of files and no binary. Should I copy the whole &#8220;&#8230;/arm/arm-angstrom-linux-gnueabi&#8221; folder?<br />
The strange thing is that arm-angstrom-linux-gnueabi/bin/gcc is just a link to ../../bin/arm-angstrom-linux-gnueabi-gcc, which was compiled for AMD64, not for ARM.</p>
<p>Thank you in advance. Sorry for the long question, and I hope it isn&#8217;t too much confusing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Intro to basic cross-compiling for the BeagleBoard by Dave</title>
		<link>http://www.electronsonradio.com/2011/04/intro-to-basic-cross-compiling-for-the-beagleboard/#comment-166</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Sat, 05 Nov 2011 02:41:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.electronsonradio.com/?p=36#comment-166</guid>
		<description>Hi Gabrijel,
You can do it with the toolchain, but I haven&#039;t actually done that myself. I assume you also need to link the kernel headers. If you do end up getting it to work this way, I&#039;d be interested to know how you did it.
I have updated drivers in OpenEmbedded before, what you need to do is create a kernel patch to update the driver to the latest version. I have briefly gone through the process here: http://www.electronsonradio.com/2011/05/openembbeded-linux-kernel-adding-pseye-patched-modules/
Basically what you need to do is get the source for the latest driver (the link you provided) and the source for the kernel (you&#039;ll find this in your OE temp directory) then do a diff to create a patch file (similar to what I&#039;ve done here: http://www.electronsonradio.com/2011/06/building-the-bleeding-edge-pseye-driver-for-your-specific-kernel-version/ (although this is more complicated than your case))
Then you add the patch to your OE kernel build and can recompile the kernel with the new driver. 

Dave</description>
		<content:encoded><![CDATA[<p>Hi Gabrijel,<br />
You can do it with the toolchain, but I haven&#8217;t actually done that myself. I assume you also need to link the kernel headers. If you do end up getting it to work this way, I&#8217;d be interested to know how you did it.<br />
I have updated drivers in OpenEmbedded before, what you need to do is create a kernel patch to update the driver to the latest version. I have briefly gone through the process here: <a href="http://www.electronsonradio.com/2011/05/openembbeded-linux-kernel-adding-pseye-patched-modules/" rel="nofollow">http://www.electronsonradio.com/2011/05/openembbeded-linux-kernel-adding-pseye-patched-modules/</a><br />
Basically what you need to do is get the source for the latest driver (the link you provided) and the source for the kernel (you&#8217;ll find this in your OE temp directory) then do a diff to create a patch file (similar to what I&#8217;ve done here: <a href="http://www.electronsonradio.com/2011/06/building-the-bleeding-edge-pseye-driver-for-your-specific-kernel-version/" rel="nofollow">http://www.electronsonradio.com/2011/06/building-the-bleeding-edge-pseye-driver-for-your-specific-kernel-version/</a> (although this is more complicated than your case))<br />
Then you add the patch to your OE kernel build and can recompile the kernel with the new driver. </p>
<p>Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Intro to basic cross-compiling for the BeagleBoard by Gabrijel</title>
		<link>http://www.electronsonradio.com/2011/04/intro-to-basic-cross-compiling-for-the-beagleboard/#comment-163</link>
		<dc:creator>Gabrijel</dc:creator>
		<pubDate>Fri, 04 Nov 2011 12:56:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.electronsonradio.com/?p=36#comment-163</guid>
		<description>Hi,

I don&#039;t know if I am on the right way and site, but I will post this question here. I am doing something with beagleboard using Angstrom distribution. I have Wireless dongle based on Atheros chip that needs ath9k_htc driver. I managed to compile kernel with that driver using OpenEmbedded and bitbake. The dongle is working but the connection gets dropped randomly. I find out that the driver is older and now I would like to give a try recompiling new driver. I don&#039;t know how to do that using OpenEmbedded (while there I only activated ATH9K_HTC in config, and run bitbake). Is there any way I can use toolchain to compile this: http://linuxwireless.org/en/users/Drivers/ath9k ?
While, in the text for that driver, there is no information fro ./configure but only make...

Thanks,
Gabrijel, Croatia</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I don&#8217;t know if I am on the right way and site, but I will post this question here. I am doing something with beagleboard using Angstrom distribution. I have Wireless dongle based on Atheros chip that needs ath9k_htc driver. I managed to compile kernel with that driver using OpenEmbedded and bitbake. The dongle is working but the connection gets dropped randomly. I find out that the driver is older and now I would like to give a try recompiling new driver. I don&#8217;t know how to do that using OpenEmbedded (while there I only activated ATH9K_HTC in config, and run bitbake). Is there any way I can use toolchain to compile this: <a href="http://linuxwireless.org/en/users/Drivers/ath9k" rel="nofollow">http://linuxwireless.org/en/users/Drivers/ath9k</a> ?<br />
While, in the text for that driver, there is no information fro ./configure but only make&#8230;</p>
<p>Thanks,<br />
Gabrijel, Croatia</p>
]]></content:encoded>
	</item>
</channel>
</rss>

