<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.sharpfin.org/index.php?action=history&amp;feed=atom&amp;title=Linux</id>
	<title>Linux - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://www.sharpfin.org/index.php?action=history&amp;feed=atom&amp;title=Linux"/>
	<link rel="alternate" type="text/html" href="https://www.sharpfin.org/index.php?title=Linux&amp;action=history"/>
	<updated>2026-04-23T17:56:50Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.4</generator>
	<entry>
		<id>https://www.sharpfin.org/index.php?title=Linux&amp;diff=126&amp;oldid=prev</id>
		<title>Philipp: Created page with &quot;Reciva provides sources for the Linux kernel used on the Barracuda on the GPL archive page. First inspection of these sources show the following:  * A UART should be available somewhere on the hardware and a console is enabled  * LIRC (linux remote control) might be available  * more to discover here of course  == Building ==   The following worked for me:  === Creating the toolchain ===  It seems that reciva uses glibc 2.3.2 and gcc 3.3.4 at this moment. We&#039;ll c...&quot;</title>
		<link rel="alternate" type="text/html" href="https://www.sharpfin.org/index.php?title=Linux&amp;diff=126&amp;oldid=prev"/>
		<updated>2025-06-08T11:28:22Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;Reciva provides sources for the Linux kernel used on the Barracuda on the GPL archive page. First inspection of these sources show the following:  * A &lt;a href=&quot;/index.php?title=UART&amp;amp;action=edit&amp;amp;redlink=1&quot; class=&quot;new&quot; title=&quot;UART (page does not exist)&quot;&gt;UART&lt;/a&gt; should be available somewhere on the hardware and a console is enabled  * &lt;a href=&quot;/index.php?title=LIRC&amp;amp;action=edit&amp;amp;redlink=1&quot; class=&quot;new&quot; title=&quot;LIRC (page does not exist)&quot;&gt;LIRC&lt;/a&gt; (linux remote control) might be available  * more to discover here of course  == Building ==   The following worked for me:  === Creating the toolchain ===  It seems that reciva uses glibc 2.3.2 and gcc 3.3.4 at this moment. We&amp;#039;ll c...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Reciva provides sources for the Linux kernel used on the Barracuda on the GPL archive page. First inspection of these sources show the following:&lt;br /&gt;
&lt;br /&gt;
* A [[UART]] should be available somewhere on the hardware and a console is enabled&lt;br /&gt;
&lt;br /&gt;
* [[LIRC]] (linux remote control) might be available&lt;br /&gt;
&lt;br /&gt;
* more to discover here of course&lt;br /&gt;
&lt;br /&gt;
== Building ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following worked for me:&lt;br /&gt;
&lt;br /&gt;
=== Creating the toolchain ===&lt;br /&gt;
&lt;br /&gt;
It seems that reciva uses glibc 2.3.2 and gcc 3.3.4 at this moment. We&amp;#039;ll create a&lt;br /&gt;
toolchain with the same versions:&lt;br /&gt;
&lt;br /&gt;
* make sure you are not logged in as root&lt;br /&gt;
* download and unpack crosstool &lt;br /&gt;
* eval `cat arm.dat gcc-3.3.4-glibc-2.3.2.dat`  sh all.sh --notest&lt;br /&gt;
* In case of PATH_MAX undeclared error, copy the patch from the gcc-3.3.6 directory with&lt;br /&gt;
  &lt;br /&gt;
  cp  patches/gcc-3.3.6/fix-fixincl.patch patches/gcc-3.3.4/  &lt;br /&gt;
&lt;br /&gt;
* and run the eval again.&lt;br /&gt;
* Have some &amp;lt;s&amp;gt;coffee&amp;lt;/s&amp;gt; beer&lt;br /&gt;
&lt;br /&gt;
=== Compiling the linux kernel ===&lt;br /&gt;
&lt;br /&gt;
* Download linux sources from Reciva and unpack&lt;br /&gt;
* make bast_config&lt;br /&gt;
* make menuconfig - exact configuration to be determined&lt;br /&gt;
* Edit the top-level makefile in the bast_linux directory and point CROSS_COMPILER to the freshly built toolchain&lt;br /&gt;
* The same as above in the recive/Makefile&lt;br /&gt;
* make&lt;br /&gt;
* make&lt;br /&gt;
* make modules&lt;br /&gt;
* make -C reciva&lt;/div&gt;</summary>
		<author><name>Philipp</name></author>
	</entry>
</feed>