<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Uncategorized on FreeBSD developer&#39;s notebook</title>
    <link>https://kernelnomicon.org/categories/uncategorized/</link>
    <description>Recent content in Uncategorized on FreeBSD developer&#39;s notebook</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 10 Jan 2020 22:21:01 +0000</lastBuildDate>
    <atom:link href="https://kernelnomicon.org/categories/uncategorized/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CentOS 7 VM boot issue</title>
      <link>https://kernelnomicon.org/posts/centos-7-vm-boot-issue/</link>
      <pubDate>Fri, 10 Jan 2020 22:21:01 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/centos-7-vm-boot-issue/</guid>
      <description>&lt;p&gt;If you&amp;rsquo;re building OVA based on CentOS 7 and your VM is stuck during boot at &amp;ldquo;tsc: Refined TSC clocksource calibration: NNNN.MMM MHz&amp;rdquo; message do not despair! It means the kernel can not find the root device and just waits for it to pop up. Which is not going to happen. In my case, it was a lack of required drivers loaded boot-time. Following line in an OVA build script resolved the issue:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Recreating Sneakers scene</title>
      <link>https://kernelnomicon.org/posts/recreating-sneakers-scene/</link>
      <pubDate>Sat, 28 Sep 2019 16:57:12 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/recreating-sneakers-scene/</guid>
      <description>&lt;p&gt;(Not a FreeBSD topic)&lt;/p&gt;
&lt;p&gt;A long time ago, in my teens, I watched movie &lt;a href=&#34;https://www.imdb.com/title/tt0105435/&#34;&gt;Sneakers&lt;/a&gt; and was very impressed by it. It was exactly how I imagined hackers at work: bare PCBs, signal probes, de-scrambling encrypted information right on the screen. I was so impressed by the latter part that I went to re-create a bit of &lt;a href=&#34;https://www.youtube.com/watch?v=F5bAa6gFvLs&#34;&gt;&amp;ldquo;No more secrets&amp;rdquo; scene&lt;/a&gt; using the only technologies I knew back then: Turbo Pascal running on MS-DOS. It wasn&amp;rsquo;t an exact replica but it was close enough and I was quite happy with the result. The program itself hasn&amp;rsquo;t survived my numerous moves from one apartment to another and got lost along with all the floppy discs sometime in the early aughts.&lt;/p&gt;</description>
    </item>
    <item>
      <title>FreeBSD support for pyu2f</title>
      <link>https://kernelnomicon.org/posts/freebsd-support-for-pyu2f/</link>
      <pubDate>Sun, 22 Sep 2019 13:39:41 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/freebsd-support-for-pyu2f/</guid>
      <description>&lt;p&gt;After long hiatus (because $JOB) I&amp;rsquo;m trying to find some time to spend on FreeBSD-related projects, looking for small ones that can be done over weekend or a bit more. One of the ideas came from Ed Maste&amp;rsquo;s twitter: implement FreeBSD support for pyu2f. Since I already spent some time working on FreeBSD U2F support for Chromium it felt like a good small project.&lt;/p&gt;
&lt;p&gt;The challenging part of the project was not U2F/HID but interfacing ioctl with Python, something I have never done before. It wasn&amp;rsquo;t super complex and I learned about Python&amp;rsquo;s ctype module.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Inky pHat on FreeBSD/Pi</title>
      <link>https://kernelnomicon.org/posts/inky-phat-on-freebsdpi/</link>
      <pubDate>Wed, 14 Nov 2018 10:21:27 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/inky-phat-on-freebsdpi/</guid>
      <description>&lt;p&gt;About a month ago I purchased &lt;a href=&#34;https://shop.pimoroni.com/products/inky-phat&#34;&gt;Inky pHat&lt;/a&gt; from Pimoroni, Pi hat with 220x104 red and black eInk screen. The device has an SPI interface with three additional GPIO signals: reset pin, command/data pin, and busy pin. Reset and busy pins are self-explanatory: the former resets device MCU the latter signals to the Pi whether the MCU is busy handling previous command/data. Command/data signals the type of SPI transaction that is about to be sent to Inky: low means command, high - data. It more or less matches interface to SSD1306 OLED display I played with before.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Raspberry Pi UART0 default frequency</title>
      <link>https://kernelnomicon.org/posts/raspberry-pi-uart0-default-frequency/</link>
      <pubDate>Wed, 14 Dec 2016 14:46:02 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/raspberry-pi-uart0-default-frequency/</guid>
      <description>&lt;p&gt;If you&amp;rsquo;re trying to boot FreeBSD with latest RaspberryPi firmware - be aware that &lt;a href=&#34;https://github.com/raspberrypi/firmware/commit/d0bc6ce8e2ae7850959fed4edb0695f3cddfb96a&#34;&gt;this commit&lt;/a&gt; changed default frequency for UART0 on at least RaspberryPi 2, so to get serial console working in u-boot/ubldr again you need to add this line to config.txt:&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-fallback&#34; data-lang=&#34;fallback&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;init_uart_clock=3000000
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;</description>
    </item>
    <item>
      <title>Debugging tip: checking kernel DTB from userland</title>
      <link>https://kernelnomicon.org/posts/debugging-tip-checking-kernel-dtb-from-userland/</link>
      <pubDate>Thu, 01 Dec 2016 17:23:08 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/debugging-tip-checking-kernel-dtb-from-userland/</guid>
      <description>&lt;p&gt;You can get source for current kernel FDT blob by running following command&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-fallback&#34; data-lang=&#34;fallback&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;sysctl -b hw.fdt.dtb | dtc -I dtb -O dts
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Edit 27/10/2017: added -O option, looks like it&amp;rsquo;s required in newer dtc&lt;/p&gt;</description>
    </item>
    <item>
      <title>MFC tracking tool filters</title>
      <link>https://kernelnomicon.org/posts/mfc-tracking-tool-filters/</link>
      <pubDate>Sat, 29 Oct 2016 15:20:21 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/mfc-tracking-tool-filters/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve just added extended filters to &lt;a href=&#34;http://mfc.kernelnomicon.org&#34;&gt;http://mfc.kernelnomicon.org&lt;/a&gt;. Now filter can be either committer, or path, or both. Path is indicated by adding @ character to the beginning, so &lt;code&gt;gonzo&lt;/code&gt; means all commits by gonzo, &lt;code&gt;@sys/arm&lt;/code&gt; means all commits to sys/arm directory, and &lt;code&gt;gonzo@sys/arm&lt;/code&gt; means all commits by gonzo to sys/arm directory. If there are more then one expression separated by space the result will be all filters OR-ed together: &lt;code&gt;@sys/arm  @boot/efi&lt;/code&gt; means all commits to sys/arm plus all commits to boot/efi directory.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Raspberry Pi userland repo update</title>
      <link>https://kernelnomicon.org/posts/raspberry-pi-userland-update/</link>
      <pubDate>Tue, 25 Oct 2016 11:44:40 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/raspberry-pi-userland-update/</guid>
      <description>&lt;p&gt;raspberrypi-userland git repo was synced to the latest upstream code base: &lt;a href=&#34;https://github.com/gonzoua/userland/tree/freebsd&#34;&gt;https://github.com/gonzoua/userland/tree/freebsd&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Netbooting FreeBSD with PXE/UEFI</title>
      <link>https://kernelnomicon.org/posts/netbooting-freebsd-with-pxeuefi/</link>
      <pubDate>Thu, 29 Sep 2016 16:11:10 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/netbooting-freebsd-with-pxeuefi/</guid>
      <description>&lt;p&gt;Dear Future Me,&lt;/p&gt;
&lt;p&gt;I guess you came here googling for &amp;ldquo;FreeBSD PXE UEFI&amp;rdquo; trying to find out how to netboot your x86 dev box. Or arm64 box. Who knows what you&amp;rsquo;re hacking on in the future. To do that you need follow these simple steps:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Put loader.efi to tftpboot dir&lt;/li&gt;
&lt;li&gt;Configure dhcpd along these lines:&lt;/li&gt;
&lt;/ul&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-gdscript3&#34; data-lang=&#34;gdscript3&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;host amd64 {
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;        hardware ethernet  b8:ae:ed:&lt;span style=&#34;color:#ae81ff&#34;&gt;77&lt;/span&gt;:&lt;span style=&#34;color:#ae81ff&#34;&gt;88&lt;/span&gt;:&lt;span style=&#34;color:#ae81ff&#34;&gt;99&lt;/span&gt;;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;        filename &lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;loader.efi&amp;#34;&lt;/span&gt;;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;        option root&lt;span style=&#34;color:#f92672&#34;&gt;-&lt;/span&gt;path &lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;/src/FreeBSD/tftproot/amd64&amp;#34;&lt;/span&gt;;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;        fixed&lt;span style=&#34;color:#f92672&#34;&gt;-&lt;/span&gt;address &lt;span style=&#34;color:#ae81ff&#34;&gt;192.168&lt;/span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;.&lt;/span&gt;&lt;span style=&#34;color:#ae81ff&#34;&gt;10.102&lt;/span&gt;;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;        option routers &lt;span style=&#34;color:#ae81ff&#34;&gt;192.168&lt;/span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;.&lt;/span&gt;&lt;span style=&#34;color:#ae81ff&#34;&gt;10.1&lt;/span&gt;;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;}
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;ul&gt;
&lt;li&gt;Make sure root-path is in /etc/exports.&lt;/li&gt;
&lt;li&gt;If you use MINIMAL-derived config add your NIC driver to /boot/loader.conf:&lt;/li&gt;
&lt;/ul&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-gdscript3&#34; data-lang=&#34;gdscript3&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;if_re_load&lt;span style=&#34;color:#f92672&#34;&gt;=&lt;/span&gt;&lt;span style=&#34;color:#e6db74&#34;&gt;&amp;#34;YES&amp;#34;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;That&amp;rsquo;s pretty much it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Untethering Jetson-TK1</title>
      <link>https://kernelnomicon.org/posts/untethering-jetson-tk1/</link>
      <pubDate>Sun, 25 Sep 2016 18:11:43 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/untethering-jetson-tk1/</guid>
      <description>&lt;p&gt;Normally I netboot all my ARM devices but in case of Jetson TK1 I thought it would be nice to go and try to make it &amp;ldquo;real computer&amp;rdquo; - running by itself, may be use it for some port builds. I added Samsung EVO to it but the plan was to use SSD for builds/source code, and to use either external SD card or eMMC as a root device. TK1 survived buildworld/buildkernel (I had to add swap though, clang is a memory monster) so it was time to populate root device and eMMC was picked as a target. There were some ms-basic-data partitions on eMMC but I didn&amp;rsquo;t think much of it and happily typed dd if=/dev/zero of=/dev/mmcsd0 bs=128m. Well&amp;hellip; Big mistake. Among those partitions was u-boot. And probably earlier stage boot loader as well. So I had to install ubuntu on one of unused machines and re-flash TK1. Luckily no permanent damage was done to the device. After this accident I added a little bit of planning into the process. Here is short summary:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Controlling AC power using GPIO</title>
      <link>https://kernelnomicon.org/posts/controlling-ac-power-using-gpio/</link>
      <pubDate>Thu, 24 Dec 2015 12:50:16 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/controlling-ac-power-using-gpio/</guid>
      <description>&lt;p&gt;Being able to power cycle ARM boards remotely (without spending a lot of $$$) was on my wish list for way to long, so I finally got around to put something together. The obvious way to do this is power relay controlled by GPIO + remotely accessible GPIO port. For the former I picked up &lt;a href=&#34;http://www.amazon.com/gp/product/B00WV7GMA2&#34;&gt;this relay by Digital Loggers&lt;/a&gt;. It was four ports, only two of them are connected at a time, you can switch selected pair by setting control port level. For a controller part I picked up RIoTBoard but actually any ARM board with  sshd running on it and user-accessible GPIO pin would do.&lt;/p&gt;</description>
    </item>
    <item>
      <title>i.MX6 IPU and HDMI drivers</title>
      <link>https://kernelnomicon.org/posts/i-mx6-ipu-and-hdmi-drivers/</link>
      <pubDate>Wed, 09 Dec 2015 15:10:39 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/i-mx6-ipu-and-hdmi-drivers/</guid>
      <description>&lt;p&gt;Back from vacation and back to work. Once I got RIoTboard up and running next natural step was to wrap up some i.MX6 project I had in &amp;ldquo;almost finished&amp;rdquo; state for months. So now they&amp;rsquo;re in &amp;ldquo;going through review&amp;rdquo; state: drivers for &lt;a href=&#34;https://reviews.freebsd.org/D4174&#34;&gt;HDMI framer&lt;/a&gt; and &lt;a href=&#34;https://reviews.freebsd.org/D4168&#34;&gt;IPU&lt;/a&gt;. They add basic 1024x768 console for iMX6 board. Video mode management requires more sophisticated timers framework, that is being work on as a part of Jetson TK1 port.&lt;/p&gt;</description>
    </item>
    <item>
      <title>RIoTboard support</title>
      <link>https://kernelnomicon.org/posts/riotboard-support/</link>
      <pubDate>Thu, 12 Nov 2015 20:28:13 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/riotboard-support/</guid>
      <description>&lt;p&gt;My career as &lt;a href=&#34;https://www.youtube.com/playlist?list=PLIlNZLQQ4dQvD_WThzImhmgI5477APYN4&#34;&gt;a trendy videoblogger&lt;/a&gt; starts to pay off. Nice people from &lt;a href=&#34;http://www.newark.com&#34;&gt;Newark element14&lt;/a&gt; offered to send me some hardware for experiments (no strings attached) I took them up on their offer and few days later received &lt;a href=&#34;http://www.element14.com/community/community/designcenter/single-board-computers/riotboard&#34;&gt;RIoTboard&lt;/a&gt;. It&amp;rsquo;s iMX6 Solo in developer-friendly package, not as compact as Beaglebone but nicely built and comes with more connectors.&lt;/p&gt;
&lt;p&gt;FreeBSD&amp;rsquo;s iMX6 support is very good, so it took two one-line fixes to FreeBSD kernel code to make it work on RIoTboard. The other chunk of work was U-Boot package. Took more time than it should have due to some operator errors. The bring up process is more or less the same as for any other iMX6 system, so it should be really easy to add this board to &lt;a href=&#34;https://github.com/freebsd/crochet&#34;&gt;crochet&lt;/a&gt;. Step by step it looks like this (some of the code came from crochet):&lt;/p&gt;</description>
    </item>
    <item>
      <title>FreeBSD on RPi 2 progress</title>
      <link>https://kernelnomicon.org/posts/freebsd-on-rpi-2-progress/</link>
      <pubDate>Mon, 09 Nov 2015 15:04:20 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/freebsd-on-rpi-2-progress/</guid>
      <description>&lt;p&gt;Quick update on progress in FreeBSD&amp;rsquo;s support of Raspberry Pi:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;VCHIQ driver was updated to the latest vendor code and bunch of FreeBSD-specific problems was fixed: locking, handling of non-cacheline aligned data&lt;/li&gt;
&lt;li&gt;Raspberry Pi userland code was updated to the latest vendor code&lt;/li&gt;
&lt;li&gt;Mikael Urankar created &lt;a href=&#34;https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204388&#34;&gt;misc/raspberrypi-userland&lt;/a&gt; for userland libraries/utilities&lt;/li&gt;
&lt;li&gt;Mikael also created &lt;a href=&#34;https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204392&#34;&gt;multimedia/omxplayer&lt;/a&gt; port for OMXPlayer, video player developed for RPi. It&amp;rsquo;s also used in Kodi player on Pi.&lt;/li&gt;
&lt;li&gt;I created &lt;a href=&#34;https://github.com/gonzoua/experimental-freebsd-ports/tree/master/games/ioquake3-pi&#34;&gt;misc/ioquake-pi&lt;/a&gt; port to make it easier for people to try it out&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I put together all this stuff on my brand new Pi 2 and recorded demo that showcases, OpenGL, Quake3, omxplayer, camera, and audio. I hope all these ports will be committed/updated before next round of armv6 packages build.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Official 7&#34; Raspberry Pi Touchscreen Display and FreeBSD</title>
      <link>https://kernelnomicon.org/posts/official-7-raspberry-pi-touchscreen/</link>
      <pubDate>Fri, 23 Oct 2015 12:28:47 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/official-7-raspberry-pi-touchscreen/</guid>
      <description>&lt;p&gt;Received yesterday and had to assembly it first thing today. Display part works like a charm without any system modifications. Haven&amp;rsquo;t researched touchscreen part though.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://kernelnomicon.org/uploads/2015/10/IMG_1330.jpg&#34;&gt;&lt;img alt=&#34;IMG_1330&#34; loading=&#34;lazy&#34; src=&#34;https://kernelnomicon.org/uploads/2015/10/IMG_1330-768x1024.jpg&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://kernelnomicon.org/uploads/2015/10/IMG_1331.jpg&#34;&gt;&lt;img alt=&#34;IMG_1331&#34; loading=&#34;lazy&#34; src=&#34;https://kernelnomicon.org/uploads/2015/10/IMG_1331-1024x768.jpg&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://kernelnomicon.org/uploads/2015/10/IMG_1333.jpg&#34;&gt;&lt;img alt=&#34;IMG_1333&#34; loading=&#34;lazy&#34; src=&#34;https://kernelnomicon.org/uploads/2015/10/IMG_1333-1024x768.jpg&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://kernelnomicon.org/uploads/2015/10/IMG_1334.jpg&#34;&gt;&lt;img alt=&#34;IMG_1334&#34; loading=&#34;lazy&#34; src=&#34;https://kernelnomicon.org/uploads/2015/10/IMG_1334-1024x768.jpg&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://kernelnomicon.org/uploads/2015/10/IMG_1335.jpg&#34;&gt;&lt;img alt=&#34;IMG_1335&#34; loading=&#34;lazy&#34; src=&#34;https://kernelnomicon.org/uploads/2015/10/IMG_1335-1024x768.jpg&#34;&gt;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>FreeBSD, BBB, and 4DCAPE-43T: touchscreen</title>
      <link>https://kernelnomicon.org/posts/freebsd-bbb-and-4dcape-43t-touchscreen/</link>
      <pubDate>Fri, 16 Oct 2015 19:42:08 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/freebsd-bbb-and-4dcape-43t-touchscreen/</guid>
      <description>&lt;p&gt;And yet another demo of 4DCAPE-43T, this time it&amp;rsquo;s touchscreen. On AM335x SoC touchscreen controller is coupled with analog-to-digital converter, for which there is a driver in FreeBSD HEAD: ti_adc. I had to implement touchscreen part and add driver  userland communication protocol. For proof of concept I used significantly dumbed-down version of &lt;a href=&#34;http://lxr.free-electrons.com/source/Documentation/input/input.txt#L262&#34;&gt;Linux input event protocol&lt;/a&gt;. tslib serves as a userland part of the demo. I believe it&amp;rsquo;s de-facto standard for touchscreen devices interface in Linux world. Only two things were changed comparing to stock one: I added bsd-raw  input plugin to communicate with kernel and rewrote framebuffer-related routines.&lt;/p&gt;</description>
    </item>
    <item>
      <title>More fun with Beaglebone Black and 4DCAPE-43T</title>
      <link>https://kernelnomicon.org/posts/more-fun-with-baglebone-black-and-4dcape-43t/</link>
      <pubDate>Fri, 09 Oct 2015 22:46:17 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/more-fun-with-baglebone-black-and-4dcape-43t/</guid>
      <description>&lt;p&gt;I like Qt. It runs on everything. More than 10 years ago you could run it on Linux/ARM on &lt;a href=&#34;https://en.wikipedia.org/wiki/Sharp_Zaurus&#34;&gt;Sharp Zaurus&lt;/a&gt; and now you can run it on &lt;a href=&#34;http://kernelnomicon.org/?p=461&#34;&gt;FreeBSD/Pi&lt;/a&gt;. I thought it would look neat on LCD screen on BBB and coded small demo player (&lt;a href=&#34;https://github.com/gonzoua/qt-demo-player&#34;&gt;qt-demo-player sources&lt;/a&gt;) just for the fun of it. Stock Qt does not have FreeBSD framebuffer support so I had to hack it up (&lt;a href=&#34;https://github.com/gonzoua/qt-platform-scfb&#34;&gt;qt-platform-scfb sources&lt;/a&gt;). Also it seems they still consider FreeBSD/clang second class citizen comparing to FreeBSD/gcc which causes some minor POSIX-related incompatibility fallout. But other than that it was smooth sailing, patch against vendor tree is really small. I&amp;rsquo;ll post it later along with build instructions. In addition to scfb platform support Qt console input plugins required: &lt;a href=&#34;https://github.com/gonzoua/qt5-bsd-input&#34;&gt;qt5-bsd-input&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>HDMI support for Beaglebone Black</title>
      <link>https://kernelnomicon.org/posts/hdmi-support-for-beaglebone-black/</link>
      <pubDate>Thu, 09 Jul 2015 15:28:53 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/hdmi-support-for-beaglebone-black/</guid>
      <description>&lt;p&gt;Just quick (and overdue) update: HDMI for BBB is in HEAD as of r284534.&lt;/p&gt;</description>
    </item>
    <item>
      <title>HDMI progress and 4DCAPE-43 support for Beaglebone Black</title>
      <link>https://kernelnomicon.org/posts/hdmi-progress-and-4dcape-43-support-for-beaglebone-black/</link>
      <pubDate>Sat, 28 Feb 2015 19:54:28 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/hdmi-progress-and-4dcape-43-support-for-beaglebone-black/</guid>
      <description>&lt;p&gt;HDMI support for Beaglebone Black is stable now and supports reading EDID, you can get the path &lt;a href=&#34;https://people.freebsd.org/~gonzo/arm/patches/bbb-hdmi-20150128.diff&#34;&gt;here&lt;/a&gt;. Before committing it I&amp;rsquo;d like to make interoperability between HDMI framer and FB/LCD drivers as generic as possible and for this I need at least one more system with working HDMI to find common patterns. For this purpose I picked up i.MX6-based &lt;a href=&#34;http://www.solid-run.com/products/hummingboard/&#34;&gt;Hummingboard&lt;/a&gt; and now try to get video output working on it. There is some minor progress but it seems before getting to HDMI/IPU I need to do some work on clock management part of the system. So it&amp;rsquo;s going to be some time before I see first pixels on my monitor.&lt;/p&gt;</description>
    </item>
    <item>
      <title>HDMI support for Beaglebone Black: first milestone</title>
      <link>https://kernelnomicon.org/posts/hdmi-support-for-beaglebone-black-first-milestone/</link>
      <pubDate>Sun, 18 Jan 2015 18:56:06 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/hdmi-support-for-beaglebone-black-first-milestone/</guid>
      <description>&lt;p&gt;Today for the first time I&amp;rsquo;ve got stable and correctly positioned output on HDMI monitor connected to BeagleBone Black. It involved fixing bug in AM335x LCDC controller, fixing bug in I2C controller, and a lot of experiments with register-pushing. Code requires major clean-up and is not ready for the tree yet. I&amp;rsquo;ll post patch when it&amp;rsquo;s in readable form.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://kernelnomicon.org/uploads/2015/01/IMG_0650.jpg&#34;&gt;&lt;img alt=&#34;IMG_0650&#34; loading=&#34;lazy&#34; src=&#34;https://kernelnomicon.org/uploads/2015/01/IMG_0650-1024x768.jpg&#34;&gt;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Update on ioquake/ARM for FreeBSD: controls support added</title>
      <link>https://kernelnomicon.org/posts/update-on-ioquakearm-for-freebsd-controls-support-added/</link>
      <pubDate>Tue, 13 Jan 2015 21:22:33 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/update-on-ioquakearm-for-freebsd-controls-support-added/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve update &lt;a href=&#34;http://people.freebsd.org/~gonzo/arm/ioquake3.arm.tar.gz&#34;&gt;ioquake binaries&lt;/a&gt; and pushed respective changes to github. New version has support for mouse and keyboard so you can actually play Quake3 on FreeBSD/Pi alas without sound. It should run out of the box on normal console. Make sure you have moused running or specify mouse device by setting Q_MOUSE_DEV environment variable, e.g.:&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-fallback&#34; data-lang=&#34;fallback&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;env Q_MOUSE_DEV=/dev/ums0 ioquake3.arm +set s_initsound 0
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;</description>
    </item>
    <item>
      <title>State of FreeBSD/MIPS emulation</title>
      <link>https://kernelnomicon.org/posts/state-of-freebsdmips-emulation/</link>
      <pubDate>Wed, 04 Sep 2013 15:22:24 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/state-of-freebsdmips-emulation/</guid>
      <description>&lt;p&gt;A week ago Adrian Chadd asked me to take a loot at FreeBSD/MIPS emulation. So last week I&amp;rsquo;ve been busy tidying up stuff in that department and looking up bits of information on various emulators. This morning I finally committed last changeset so now is the time to write up summary.&lt;/p&gt;
&lt;h2 id=&#34;emulators&#34;&gt;Emulators&lt;/h2&gt;
&lt;p&gt;There are two widely used MIPS emulatoes that FreeBSD supports: &lt;a href=&#34;http://www.qemu.org&#34;&gt;QEMU&lt;/a&gt; and &lt;a href=&#34;http://gxemul.sourceforge.net&#34;&gt;GXemul&lt;/a&gt;. Both of them support numerous MIPS devices but we&amp;rsquo;re interested in only two.&lt;/p&gt;</description>
    </item>
    <item>
      <title>USB driver for FreeBSD/Beaglebone</title>
      <link>https://kernelnomicon.org/posts/usb-driver-for-freebsdbeaglebone/</link>
      <pubDate>Thu, 27 Jun 2013 21:10:36 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/usb-driver-for-freebsdbeaglebone/</guid>
      <description>&lt;p&gt;It took me two months but I finally got back to hacking on musb driver for FreeBSD (the one that is used in TI AM335x-based devices like Beaglebone or Beaglebone Black). Previous revision turned out not to be ready for production. Here is the new one: &lt;a href=&#34;http://people.freebsd.org/~gonzo/arm/patches/beaglebone-usb-20130626.diff&#34;&gt;beaglebone-usb-20130626.diff&lt;/a&gt;. I adopted it to latest HEAD, fixed numerous bugs, added support for SPLIT transactions and USB suspend/resume signalling. There is some cleaning-up to do but unless something major comes up the plan is to commit it over next few days.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Framebuffer/syscons support for AM335x</title>
      <link>https://kernelnomicon.org/posts/framebuffersyscons-support-for-am335x/</link>
      <pubDate>Sun, 26 May 2013 17:48:44 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/framebuffersyscons-support-for-am335x/</guid>
      <description>&lt;p&gt;I finally got around to finishing the PWM and LCDC driver for AM335x. Everything was committed today. Here is demo on AM335x EVM (I apologize for quality):&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://kernelnomicon.org/uploads/2013/05/IMG_0049.jpg&#34;&gt;&lt;img alt=&#34;IMG_0049&#34; loading=&#34;lazy&#34; src=&#34;https://kernelnomicon.org/uploads/2013/05/IMG_0049-e1369615548914-300x224.jpg&#34;&gt;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Netbooting ARM/MIPS devices: ubldr</title>
      <link>https://kernelnomicon.org/posts/netbooting-armmips-devices-ubldr/</link>
      <pubDate>Fri, 19 Apr 2013 19:24:19 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/netbooting-armmips-devices-ubldr/</guid>
      <description>&lt;p&gt;As it was mentioned in &lt;a href=&#34;http://kernelnomicon.org/?p=327&#34;&gt;previous post&lt;/a&gt; U-Boot can boot FreeBSD kernel directly but this approach doesn&amp;rsquo;t allow a great deal of control over boot process: there is no way to set tunables&amp;rsquo; values or pre-load module. Controlling this stuff requires more knowledge of FreeBSD internal data structures and its boot process then U-Boot holds.&lt;/p&gt;
&lt;p&gt;On i386 and other Tier1 architectures this task is handled by the &lt;a href=&#34;http://www.freebsd.org/cgi/man.cgi?query=loader&amp;amp;sektion=8&#34;&gt;loader(8)&lt;/a&gt; program. It&amp;rsquo;s last stage boot loader (e.g. it&amp;rsquo;s supposed to pass control to FreeBSD kernel only), highly customizable and scriptable. &lt;a href=&#34;http://www.freebsd.org/cgi/man.cgi?query=loader&amp;amp;sektion=8&#34;&gt;loader(8)&lt;/a&gt; relies on one of the previous stages boot loader to access resources like disks, console, network. For i386 it&amp;rsquo;s BTX and BIOS.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Netbooting ARM/MIPS devices: server setup</title>
      <link>https://kernelnomicon.org/posts/netbooting-armmips-devices-server-setup/</link>
      <pubDate>Thu, 14 Feb 2013 18:50:42 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/netbooting-armmips-devices-server-setup/</guid>
      <description>&lt;p&gt;I was asked to share details about my root-over-NFS setup so here they are. I decided to split how-to in two posts: server/kernel part and u-boot part.&lt;/p&gt;
&lt;p&gt;Usual components in the setup are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;DHCP server&lt;/li&gt;
&lt;li&gt;TFTP server&lt;/li&gt;
&lt;li&gt;NFS server&lt;/li&gt;
&lt;li&gt;NAT (optional)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;dhcp-server&#34;&gt;DHCP server&lt;/h2&gt;
&lt;p&gt;I use &lt;strong&gt;net/isc-dhcp42-server&lt;/strong&gt; as a server. Sample dhcpd.conf:&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-fallback&#34; data-lang=&#34;fallback&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;option root-opts code 130 = string; # NFS / mount options
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;log-facility local7;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;subnet 192.168.10.0 netmask 255.255.255.0 {
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;        server-name &amp;#34;cinderella.bluezbox.com&amp;#34;;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;        server-identifier 192.168.10.1;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;        option subnet-mask 255.255.255.0;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;        option broadcast-address 192.168.10.255;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;        option domain-name-servers 8.8.8.8;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;        option domain-name &amp;#34;bluezbox.com&amp;#34;;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;        next-server 192.168.10.1;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;        option routers 192.168.10.1;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;}
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;group {
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;        host pandaboard {
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;                hardware ethernet 0E:60:33:B1:46:01;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;                fixed-address 192.168.10.90;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;                filename &amp;#34;kernel.PANDA.bin&amp;#34;;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;                option root-path &amp;#34;/src/FreeBSD/nfs/armv6&amp;#34;;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;                option root-opts &amp;#34;nolockd&amp;#34;;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;        }
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;        host rpi {
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;                hardware ethernet b8:27:eb:f6:08:83;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;                fixed-address 192.168.10.91;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;                filename &amp;#34;ubldr&amp;#34;;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;                option root-path &amp;#34;/src/FreeBSD/nfs/rpi&amp;#34;;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;                option root-opts &amp;#34;nolockd&amp;#34;;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;        }
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;}
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Config is pretty self-explanatory. I use google&amp;rsquo;s &lt;strong&gt;8.8.8.8&lt;/strong&gt; nameserver but you can change it to your very own DNS server. Difference between various &lt;strong&gt;filename &amp;ldquo;&amp;hellip;&amp;rdquo;&lt;/strong&gt; will be explained later.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Netbooting Hackberry A10 (Allwinner A10)</title>
      <link>https://kernelnomicon.org/posts/netbooting-hackberry-a10-allwinner-a10/</link>
      <pubDate>Sun, 10 Feb 2013 00:14:34 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/netbooting-hackberry-a10-allwinner-a10/</guid>
      <description>&lt;p&gt;Last few weeks I&amp;rsquo;ve been acting as a reviewer for Ganbold Tsagaankhuu&amp;rsquo;s port of FreeBSD for Cubieboard so in order to provide more valuable input and less naysaying I decided to get A10-based device to test his changes. So I ordered &lt;a href=&#34;https://www.miniand.com/products/Hackberry%20A10%20Developer%20Board&#34;&gt;Hackberry&lt;/a&gt; from miniand.com. I&amp;rsquo;m not great fan of pushing SD cards back and forth so first thing I do with my SoCs is get them netbooting. That&amp;rsquo;s where fun begins.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Accessing GPIO from Perl, Python, and Ruby</title>
      <link>https://kernelnomicon.org/posts/accessing-gpio-from-perl-python-and-ruby/</link>
      <pubDate>Thu, 07 Feb 2013 18:01:21 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/accessing-gpio-from-perl-python-and-ruby/</guid>
      <description>&lt;p&gt;I started this smallish project to overcome coder&amp;rsquo;s block and original idea was to implement it in only one scripting language. I chose Python as I believed it had most clear API but then I decided to throw in Perl and Ruby as well. It was more exercise in building C extensions then in actual system programming but it was fun nonetheless. All three sub-projects lack proper documentation but there are examples that should be enough to get started.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Building image for Raspberry Pi: up to date version</title>
      <link>https://kernelnomicon.org/posts/building-image-for-raspberry-pi-up-to-date-version/</link>
      <pubDate>Fri, 01 Feb 2013 15:00:02 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/building-image-for-raspberry-pi-up-to-date-version/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Update 1: Add -DDB_FROM_SRC to install targets&lt;/strong&gt;
&lt;strong&gt;Update 2: Add user &amp;ldquo;pi&amp;rdquo; with password &amp;ldquo;raspberry&amp;rdquo;&lt;/strong&gt;
&lt;strong&gt;Update 3: Added host system requirements suggested in comments&lt;/strong&gt;
&lt;strong&gt;Update 4: Rename bcm2835-rpi-b.dtb to rpi.dtb&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s been a while since I posted original &lt;a href=&#34;http://kernelnomicon.org/?p=164&#34;&gt;build instruction&lt;/a&gt; and a lot has change. Here is new version of it with some explanations:&lt;/p&gt;
&lt;p&gt;First make sure your host system is configured properly:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;WITHOUT_FORTH= must NOT be set in src.conf&lt;/li&gt;
&lt;li&gt;msdos support must be available in the kernel&lt;/li&gt;
&lt;li&gt;geom_md support must be available in the kernel&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;All code has been moved to HEAD. freebsd-pi repository on github serves only historical purpose and I guess will be removed at some point in future. So in order to build image you need sources for -head&lt;/p&gt;</description>
    </item>
    <item>
      <title>Packages(*) for Rasberry Pi(**)</title>
      <link>https://kernelnomicon.org/posts/packages-for-rasberry-pi/</link>
      <pubDate>Fri, 11 Jan 2013 20:05:44 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/packages-for-rasberry-pi/</guid>
      <description>&lt;p&gt;I finally got around to setting up experimental pkgng repo for ARM in order to share packages with other ARM developers and users who feel adventurous. And man, was it simple. I have pandaboard that is super-fast comparing to Raspberri Pi so I use it for building ports. There were several installed so I just had to generate packages for them using&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-fallback&#34; data-lang=&#34;fallback&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;pkg create -a
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;command. Then I uploaded all newly generated files to the server, grabbed packages &lt;a href=&#34;http://lists.freebsd.org/pipermail/freebsd-arm/2012-December/004493.html&#34;&gt;built and shared&lt;/a&gt; by Stephen Hurd, removed duplicates with older versions and generated repo.txz by issuing&lt;/p&gt;</description>
    </item>
    <item>
      <title>VCHI driver, part 2</title>
      <link>https://kernelnomicon.org/posts/vchi-driver-part-2/</link>
      <pubDate>Tue, 08 Jan 2013 15:33:02 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/vchi-driver-part-2/</guid>
      <description>&lt;p&gt;Some time ago I &lt;a href=&#34;http://kernelnomicon.org/?p=185&#34;&gt;announced&lt;/a&gt; port of VCHI driver to FreeBSD. Since then it was re-licensed as BSD/GPL and I had high hopes for bringing it into the tree as a part of sys/contrib. This weekend I finally got around to it but  turned out things had changed for worse. VCHI driver used to have this neat OS-abstraction wrapper, so overall porting process was quite simple: implement synch primitives, physical pages management, driver-specific initialization and you&amp;rsquo;re done. But&amp;hellip; The layer was lost with driver update in October. The reason for it - &lt;a href=&#34;https://github.com/raspberrypi/firmware/issues/130&#34;&gt;OS compatibility shims are banned from Linux mainline kernel&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Broadcom switches vchiq to dual license</title>
      <link>https://kernelnomicon.org/posts/broadcom-switched-vchiq-to-dual-license/</link>
      <pubDate>Mon, 17 Dec 2012 21:25:34 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/broadcom-switched-vchiq-to-dual-license/</guid>
      <description>&lt;p&gt;vchiq, kernel driver for interfacing ARM with VideoCore is now dual-licensed (BSD/GPL).&lt;/p&gt;
&lt;p&gt;References:
&lt;a href=&#34;https://github.com/raspberrypi/firmware/issues/40&#34;&gt;https://github.com/raspberrypi/firmware/issues/40&lt;/a&gt;
&lt;a href=&#34;https://github.com/raspberrypi/linux/commit/d21d26ebd773ab87888351220739b43a9733233a&#34;&gt;https://github.com/raspberrypi/linux/commit/d21d26ebd773ab87888351220739b43a9733233a&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>U-Boot env variables iterator</title>
      <link>https://kernelnomicon.org/posts/u-boot-env-variables-iterator/</link>
      <pubDate>Mon, 26 Nov 2012 15:26:49 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/u-boot-env-variables-iterator/</guid>
      <description>&lt;p&gt;Ran into it recently and decided to post here just in case someone will have this problem too. Do not define both CONFIG_LOADADDR and loadaddr in CONFIG_EXTRA_ENV_SETTINGS. Otherwise environment variables enumeration API(API_ENV_ENUM) will loop forever.&lt;/p&gt;</description>
    </item>
    <item>
      <title>FreeBSD/Pi update</title>
      <link>https://kernelnomicon.org/posts/freebsdpi-update/</link>
      <pubDate>Mon, 29 Oct 2012 19:34:32 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/freebsdpi-update/</guid>
      <description>&lt;p&gt;So, here is status update on the progress:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;freebsd-pi github repo has been merged to HEAD and should be considered only as a reference from now on.&lt;/li&gt;
&lt;li&gt;I repackaged &lt;a href=&#34;http://people.freebsd.org/~gonzo/arm/rpi/freebsd-pi-uboot-20120806-sd.tar.gz&#34;&gt;freebsd-pi-uboot-20120806-sd.tar.gz&lt;/a&gt; so tar should not complain about uid/guid stuff&lt;/li&gt;
&lt;li&gt;Hans Peter Selasky and Alexander Rybalko added host mode support for DWC OTG driver&lt;/li&gt;
&lt;li&gt;Problem with tty on serial port has been fixed. Use 3wire.115200 type for ttyu0 in /etc/ttys&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Still a lot of stuff to do though.
P.S.
I&amp;rsquo;ll post updated build script later.&lt;/p&gt;</description>
    </item>
    <item>
      <title>projects/armv6 branch is no more</title>
      <link>https://kernelnomicon.org/posts/projectsarmv6-branch-is-no-more/</link>
      <pubDate>Fri, 17 Aug 2012 19:18:43 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/projectsarmv6-branch-is-no-more/</guid>
      <description>&lt;p&gt;ARMv6/AMRv7 support is &lt;a href=&#34;http://lists.freebsd.org/pipermail/freebsd-hackers/2012-August/040263.html&#34;&gt;now in main FreeBSD codebase&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;New goodies:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;General ARMv6/ARMv7 kernel bits (pmap, cache,
assembler routines, etc&amp;hellip;)&lt;/li&gt;
&lt;li&gt;ARM SMP support&lt;/li&gt;
&lt;li&gt;VFP/Neon support&lt;/li&gt;
&lt;li&gt;ARM Generic Interrupt Controller driver&lt;/li&gt;
&lt;li&gt;Improved thread-local storage for cpus &amp;gt;=ARMv6&lt;/li&gt;
&lt;li&gt;Two new values for TARGET_ARCH: armv6 and armv6eb&lt;/li&gt;
&lt;li&gt;Driver for SMSC LAN95XX and LAN8710A ethernet controllers&lt;/li&gt;
&lt;li&gt;Marvell MV78x60 support (multiuser, ARMADA XP kernel config)&lt;/li&gt;
&lt;li&gt;TI OMAP4 and AM335x support (multiuser, no GPU or graphics
support, kernel configs for Pandaboard and Beaglebone)&lt;/li&gt;
&lt;li&gt;LPC32x0 support (multiuser, frame buffer works with SSD1289
LCD controller.Embedded Artists EA3250 kernel config)&lt;/li&gt;
&lt;li&gt;Barebone Nvidia Tegra2 support (timers, interrupts and UART.
No kernel config)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I&amp;rsquo;m going to re-create Raspberry Pi port off HEAD and start merging least intrusive bits back to the tree.&lt;/p&gt;</description>
    </item>
    <item>
      <title>FreeBSD/Pi setup HowTo</title>
      <link>https://kernelnomicon.org/posts/freebsdpi-setup-howto/</link>
      <pubDate>Sun, 05 Aug 2012 19:54:16 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/freebsdpi-setup-howto/</guid>
      <description>&lt;h3 id=&#34;this-instruction-is-no-longer-correct-new-version-is-here&#34;&gt;This instruction is no longer correct. New version is &lt;a href=&#34;http://kernelnomicon.org/?p=275&#34;&gt;here&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Took some time but it seems we&amp;rsquo;re there too :)&lt;/p&gt;
&lt;p&gt;Alexander Rybalko, who works on USB drivers for the platform got remote telnet shell to the device: &lt;a href=&#34;http://pastebin.com/6NqQLWD2&#34;&gt;http://pastebin.com/6NqQLWD2&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Having fixed serial console for userland applications (two lines change) and after some tweaking of SDHCI driver I got access to multiuser shell too: &lt;a href=&#34;http://people.freebsd.org/~gonzo/arm/rpi/multiuser.txt&#34;&gt;multiuser.txt&lt;/a&gt;
Still not usable for putting together distros but stable enough for those who are willing to get their hands dirty with kernel side.&lt;/p&gt;</description>
    </item>
    <item>
      <title>BSD Pi</title>
      <link>https://kernelnomicon.org/posts/bsd-pi/</link>
      <pubDate>Fri, 13 Jul 2012 21:34:06 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/bsd-pi/</guid>
      <description>&lt;p&gt;NetBSD &lt;a href=&#34;http://mail-index.netbsd.org/port-arm/2012/07/13/msg001367.html&#34;&gt;reached multiuser&lt;/a&gt; on Raspberry Pi! Congratulation to Nick Hudson and all involved.&lt;/p&gt;
&lt;p&gt;FreeBSD is not there yet, but we&amp;rsquo;re not slacking either:&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;http://imgur.com/8pgOk&#34;&gt;&lt;img loading=&#34;lazy&#34; src=&#34;http://i.imgur.com/8pgOks.jpg&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;.&lt;/p&gt;
&lt;p&gt;Well, may be just a little. It&amp;rsquo;s not even single user yet. SDHC support is work in progress. No USB yet, hence no keyboard and no network. Just console output to framebuffer or serial port.&lt;/p&gt;</description>
    </item>
    <item>
      <title>New U-Boot build</title>
      <link>https://kernelnomicon.org/posts/new-u-boot-build/</link>
      <pubDate>Sat, 07 Jul 2012 13:20:39 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/new-u-boot-build/</guid>
      <description>&lt;p&gt;New build for Raspberry Pi. ChangeLog:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;New firmware&lt;/li&gt;
&lt;li&gt;Improved SD card performance&lt;/li&gt;
&lt;li&gt;Added USB mass storage devices support&lt;/li&gt;
&lt;li&gt;Added ext2 filesystem support (painfully slow with SD card, tolerable with USB memory stick)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Tarball: &lt;a href=&#34;http://people.freebsd.org/~gonzo/arm/rpi/raspberry-pi-uboot-20120707.tar.gz&#34;&gt;raspberry-pi-uboot-20120707.tar.gz&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SD card image (32Mb): &lt;a href=&#34;http://people.freebsd.org/~gonzo/arm/rpi/raspberry-pi-uboot-20120707.img&#34;&gt;raspberry-pi-uboot-20120707.img&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>U-Boot for Raspberry Pi, the last step</title>
      <link>https://kernelnomicon.org/posts/u-boot-for-raspberry-pi-the-last-step/</link>
      <pubDate>Fri, 22 Jun 2012 00:28:35 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/u-boot-for-raspberry-pi-the-last-step/</guid>
      <description>&lt;p&gt;Yes, the last step. It doesn&amp;rsquo;t mean that I&amp;rsquo;m abandoning this project. Not at all. It just that it has reached the state I wanted it to reach from the very beginning: fairly stable, flexible  u-boot distribution suitable to be used as an environment for OS bring-up. So now it&amp;rsquo;s time to get back to the original idea: get FreeBSD running on Raspberry Pi.&lt;/p&gt;
&lt;p&gt;So, current state of affairs is &lt;a href=&#34;http://people.freebsd.org/~gonzo/arm/rpi/raspberry-pi-uboot-20120621.tar.gz&#34;&gt;raspberry-pi-uboot-20120621.tar.gz&lt;/a&gt;. It includes:&lt;/p&gt;</description>
    </item>
    <item>
      <title>U-Boot for Raspberry Pi, step 8: SDHC support</title>
      <link>https://kernelnomicon.org/posts/u-boot-for-raspberry-pi-step-8-sdhc-support/</link>
      <pubDate>Wed, 20 Jun 2012 12:59:32 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/u-boot-for-raspberry-pi-step-8-sdhc-support/</guid>
      <description>&lt;p&gt;Initial support for SD card has just been pushed to github repo.&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-gdscript3&#34; data-lang=&#34;gdscript3&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;U&lt;span style=&#34;color:#f92672&#34;&gt;-&lt;/span&gt;Boot &lt;span style=&#34;color:#ae81ff&#34;&gt;2012.04&lt;/span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;.&lt;/span&gt;&lt;span style=&#34;color:#ae81ff&#34;&gt;01&lt;/span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;-&lt;/span&gt;&lt;span style=&#34;color:#ae81ff&#34;&gt;00479&lt;/span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;-&lt;/span&gt;gb58d9ae&lt;span style=&#34;color:#f92672&#34;&gt;-&lt;/span&gt;dirty (Jun &lt;span style=&#34;color:#ae81ff&#34;&gt;20&lt;/span&gt; &lt;span style=&#34;color:#ae81ff&#34;&gt;2012&lt;/span&gt; &lt;span style=&#34;color:#f92672&#34;&gt;-&lt;/span&gt; &lt;span style=&#34;color:#ae81ff&#34;&gt;11&lt;/span&gt;:&lt;span style=&#34;color:#ae81ff&#34;&gt;47&lt;/span&gt;:&lt;span style=&#34;color:#ae81ff&#34;&gt;13&lt;/span&gt;)
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;DRAM:  &lt;span style=&#34;color:#ae81ff&#34;&gt;128&lt;/span&gt; MiB
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;WARNING: Caches &lt;span style=&#34;color:#f92672&#34;&gt;not&lt;/span&gt; enabled
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;MMC:   CAPS: &lt;span style=&#34;color:#ae81ff&#34;&gt;00000000&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;bcm2835_sdh: &lt;span style=&#34;color:#ae81ff&#34;&gt;0&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Using default environment
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;In:    serial
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Out:   serial
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Err:   serial
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Net:   Net Initialization Skipped
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;No ethernet found&lt;span style=&#34;color:#f92672&#34;&gt;.&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;U&lt;span style=&#34;color:#f92672&#34;&gt;-&lt;/span&gt;Boot&lt;span style=&#34;color:#f92672&#34;&gt;&amp;gt;&lt;/span&gt; mmcinfo
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Device: bcm2835_sdh
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Manufacturer ID: &lt;span style=&#34;color:#ae81ff&#34;&gt;1&lt;/span&gt;b
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;OEM: &lt;span style=&#34;color:#ae81ff&#34;&gt;534&lt;/span&gt;d
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Name: &lt;span style=&#34;color:#ae81ff&#34;&gt;00000&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Tran Speed: &lt;span style=&#34;color:#ae81ff&#34;&gt;25000000&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Rd Block Len: &lt;span style=&#34;color:#ae81ff&#34;&gt;512&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;SD version &lt;span style=&#34;color:#ae81ff&#34;&gt;2.0&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;High Capacity: No
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Capacity: &lt;span style=&#34;color:#ae81ff&#34;&gt;1.9&lt;/span&gt; GiB
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Bus Width: &lt;span style=&#34;color:#ae81ff&#34;&gt;4&lt;/span&gt;&lt;span style=&#34;color:#f92672&#34;&gt;-&lt;/span&gt;bit
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;U&lt;span style=&#34;color:#f92672&#34;&gt;-&lt;/span&gt;Boot&lt;span style=&#34;color:#f92672&#34;&gt;&amp;gt;&lt;/span&gt; fatls mmc &lt;span style=&#34;color:#ae81ff&#34;&gt;0&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;    &lt;span style=&#34;color:#ae81ff&#34;&gt;16528&lt;/span&gt;   bootcode&lt;span style=&#34;color:#f92672&#34;&gt;.&lt;/span&gt;bin
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;      &lt;span style=&#34;color:#ae81ff&#34;&gt;127&lt;/span&gt;   cmdline&lt;span style=&#34;color:#f92672&#34;&gt;.&lt;/span&gt;txt
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;   &lt;span style=&#34;color:#ae81ff&#34;&gt;314691&lt;/span&gt;   loader&lt;span style=&#34;color:#f92672&#34;&gt;.&lt;/span&gt;bin
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  &lt;span style=&#34;color:#ae81ff&#34;&gt;2047848&lt;/span&gt;   start&lt;span style=&#34;color:#f92672&#34;&gt;.&lt;/span&gt;elf
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;   &lt;span style=&#34;color:#ae81ff&#34;&gt;181196&lt;/span&gt;   kernel&lt;span style=&#34;color:#f92672&#34;&gt;.&lt;/span&gt;img
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#ae81ff&#34;&gt;5&lt;/span&gt; file(s), &lt;span style=&#34;color:#ae81ff&#34;&gt;0&lt;/span&gt; dir(s)
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;U&lt;span style=&#34;color:#f92672&#34;&gt;-&lt;/span&gt;Boot&lt;span style=&#34;color:#f92672&#34;&gt;&amp;gt;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;</description>
    </item>
    <item>
      <title>U-Boot for Raspberry Pi, step 7: cleanup</title>
      <link>https://kernelnomicon.org/posts/u-boot-for-raspberry-pi-step-7-cleanup/</link>
      <pubDate>Sun, 17 Jun 2012 19:32:26 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/u-boot-for-raspberry-pi-step-7-cleanup/</guid>
      <description>&lt;p&gt;More progress on the subject:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;I cleaned up sources and pushed new version to github.&lt;/li&gt;
&lt;li&gt;Stephen Warren submitted patches for R-Pi support to U-Boot mailing list &lt;a href=&#34;http://lists.denx.de/pipermail/u-boot/2012-June/125834.html&#34;&gt;here&lt;/a&gt; and &lt;a href=&#34;http://lists.denx.de/pipermail/u-boot/2012-June/125835.html&#34;&gt;here&lt;/a&gt;. His version is much cleaner so I spent some time combining his patches with ported USB driver. So now target is called rpi_b and you should use &amp;ldquo;make rpi_b_config&amp;rdquo; instead of &amp;ldquo;make raspberry_pi_config&amp;rdquo; step when building U-Boot from sources.&lt;/li&gt;
&lt;li&gt;Pre-built binaries are available for download &lt;a href=&#34;http://people.freebsd.org/~gonzo/arm/rpi/rpi-uboot.tar.gz&#34;&gt;here&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;</description>
    </item>
    <item>
      <title>U-Boot for Raspberry Pi, step 6: It lives!</title>
      <link>https://kernelnomicon.org/posts/u-boot-for-raspberry-pi-step-6-it-lives/</link>
      <pubDate>Fri, 15 Jun 2012 20:15:27 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/u-boot-for-raspberry-pi-step-6-it-lives/</guid>
      <description>&lt;p&gt;And finally it works!&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-fallback&#34; data-lang=&#34;fallback&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;U-Boot 2012.04.01-00306-gecc6e3d-dirty (Jun 15 2012 - 19:05:09)
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;DRAM:  128 MiB
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;WARNING: Caches not enabled
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Using default environment
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;In:    serial
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Out:   serial
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Err:   serial
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Net:   No ethernet found.
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Raspberry-Pi # usb start
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;(Re)start USB...
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;USB:   Core Release: 2.80a
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;scanning bus for devices... 3 USB Device(s) found
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;       scanning bus for ethernet devices... 1 Ethernet Device(s) found
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Raspberry-Pi # dhcp
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Waiting for Ethernet connection... done.
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;BOOTP broadcast 1
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;*** Unhandled DHCP Option in OFFER/ACK: 28
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;*** Unhandled DHCP Option in OFFER/ACK: 28
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;DHCP client bound to address 192.168.10.21
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Using sms0 device
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;TFTP from server 192.168.10.1; our IP address is 192.168.10.21
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Filename &amp;#39;kernel.RPI&amp;#39;.
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Load address: 0x700000
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Loading: #################################################################
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;         #################################################################
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;         #################################################################
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;         #################################################################
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;         ######################################################
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;done
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Bytes transferred = 4597674 (4627aa hex)
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Raspberry-Pi # ping 192.168.10.1
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Waiting for Ethernet connection... done.
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Using sms0 device
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;host 192.168.10.1 is alive
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Raspberry-Pi #
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;</description>
    </item>
    <item>
      <title>U-Boot on Raspberry Pi, step 5: More USB stuff</title>
      <link>https://kernelnomicon.org/posts/u-boot-on-raspberry-pi-step-5-more-usb-stuff/</link>
      <pubDate>Fri, 15 Jun 2012 00:54:09 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/u-boot-on-raspberry-pi-step-5-more-usb-stuff/</guid>
      <description>&lt;p&gt;OK. No visual progress, but short SitRep: I got control transfers working more stable and got bulk transfer somewhat working: U-Boot sends one packet and receives response, then all bulk transfers end up in STALL state. Investigating.&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-fallback&#34; data-lang=&#34;fallback&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;BOOTP broadcast 1
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;** smsc95xx_send(), len 342, buf 0x7e8db5e
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;BULK -&amp;gt; &amp;lt;3,2&amp;gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;dev = 3 pipe = 2 buf = 07e8db5e size = 350 dir_out = 1
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;max_hc_xfer_size = 65535, max_hc_pkt_count = 511
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;xfer_len = 350, num_packets = 6, max = 64, buffer = 07e8db5e(07e8f490)
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Tx: len = 350, actual = 350, err = 0
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;** smsc95xx_recv()
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;BULK -&amp;gt; &amp;lt;3,1&amp;gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;dev = 3 pipe = 1 buf = 07fec698 size = 2048 dir_out = 0
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;max_hc_xfer_size = 65535, max_hc_pkt_count = 511
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;xfer_len = 2048, num_packets = 32, max = 64, buffer = 07fec698(07e8f490)
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Rx: len = 2048, actual = 368, err = 0
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;packet received
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;packet received
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Receive from protocol 0x800
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Got IP
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;len=346, v=45
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;DHCPHandler: got packet: (src=67, dst=68, len=318) state: 3
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Filtering pkt = 0
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;DHCPHandler: got DHCP packet: (src=67, dst=68, len=318) state: 3
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;DHCP: state=SELECTING bp_file: &amp;#34;kernel.RPI&amp;#34;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;TRANSITIONING TO REQUESTING STATE
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;*** Unhandled DHCP Option in OFFER/ACK: 130
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;*** Unhandled DHCP Option in OFFER/ACK: 28
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;DhcpSendRequestPkt: Sending DHCPREQUEST
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Transmitting DHCPREQUEST packet: len = 342
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;** smsc95xx_send(), len 342, buf 0x7e8dace
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;BULK -&amp;gt; &amp;lt;3,2&amp;gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;dev = 3 pipe = 2 buf = 07e8dace size = 350 dir_out = 1
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;max_hc_xfer_size = 65535, max_hc_pkt_count = 511
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;xfer_len = 350, num_packets = 6, max = 64, buffer = 07e8dace(07e8f490)
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Channel halted
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Tx: len = 350, actual = 0, err = 0
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;BOOTP broadcast 2
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;** smsc95xx_send(), len 342, buf 0x7e8db5e
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;BULK -&amp;gt; &amp;lt;3,2&amp;gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;dev = 3 pipe = 2 buf = 07e8dace size = 350 dir_out = 1
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;max_hc_xfer_size = 65535, max_hc_pkt_count = 511
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;xfer_len = 350, num_packets = 6, max = 64, buffer = 07e8dace(07e8f490)
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Channel halted
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Tx: len = 350, actual = 0, err = 0
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;BOOTP broadcast 2
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;** smsc95xx_send(), len 342, buf 0x7e8db5e
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;BULK -&amp;gt; &amp;lt;3,2&amp;gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;dev = 3 pipe = 2 buf = 07e8db5e size = 350 dir_out = 1
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;max_hc_xfer_size = 65535, max_hc_pkt_count = 511
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;xfer_len = 350, num_packets = 6, max = 64, buffer = 07e8db5e(07e8f490)
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Channel halted
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Tx: len = 350, actual = 0, err = 0
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;** smsc95xx_recv()
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;BULK -&amp;gt; &amp;lt;3,1&amp;gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;dev = 3 pipe = 1 buf = 07fec698 size = 2048 dir_out = 0
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;max_hc_xfer_size = 65535, max_hc_pkt_count = 511
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;xfer_len = 2048, num_packets = 32, max = 64, buffer = 07fec698(07e8f490)
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;HANG at line 533: 00000423
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;</description>
    </item>
    <item>
      <title>U-Boot on Raspberry Pi, step 4: DWC OTG, Control transactions</title>
      <link>https://kernelnomicon.org/posts/u-boot-on-raspberry-pi-step-4-dwc-otg-control-transactions/</link>
      <pubDate>Tue, 12 Jun 2012 00:20:11 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/u-boot-on-raspberry-pi-step-4-dwc-otg-control-transactions/</guid>
      <description>&lt;p&gt;After rather busy weekend I finally got control transaction support for DWC OTG controller working on Raspberry Pi. U-Boot DWC OTG driver is cut-down version of Linux driver that works in polling mode. Stability is not very good at the moment though. And make sure to use latest firmware files. It does matter.&lt;/p&gt;
&lt;p&gt;Next step - bulk transactions.&lt;/p&gt;
&lt;p&gt;Repo: &lt;a href=&#34;https://github.com/gonzoua/u-boot-pi&#34;&gt;https://github.com/gonzoua/u-boot-pi&lt;/a&gt;&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-fallback&#34; data-lang=&#34;fallback&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;Raspberry-Pi # usb info
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;1: Hub,  USB Revision 1.10
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; - DWC OTG RootHub
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; - Class: Hub
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; - PacketSize: 8  Configurations: 1
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; - Vendor: 0x0000  Product 0x0000 Version 0.0
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;   Configuration: 1
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;   - Interfaces: 1 Self Powered 0mA
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;     Interface: 0
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;     - Alternate Setting 0, Endpoints: 1
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;     - Class Hub
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;     - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;2: Hub,  USB Revision 2.0
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; - Class: Hub
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; - PacketSize: 64  Configurations: 1
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; - Vendor: 0x0424  Product 0x9512 Version 2.0
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;   Configuration: 1
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;   - Interfaces: 1 Self Powered Remote Wakeup 2mA
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;     Interface: 0
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;     - Alternate Setting 0, Endpoints: 1
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;     - Class Hub
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;     - Endpoint 1 In Interrupt MaxPacket 1 Interval 255ms
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;3: Vendor specific,  USB Revision 2.0
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; - Class: Vendor specific
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; - PacketSize: 64  Configurations: 1
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; - Vendor: 0x0424  Product 0xec00 Version 2.0
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;   Configuration: 1
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;   - Interfaces: 1 Self Powered Remote Wakeup 2mA
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;     Interface: 0
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;     - Alternate Setting 0, Endpoints: 3
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;     - Class Vendor specific
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;     - Endpoint 1 In Bulk MaxPacket 64
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;     - Endpoint 2 Out Bulk MaxPacket 64
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;     - Endpoint 3 In Interrupt MaxPacket 16 Interval 1ms
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;</description>
    </item>
    <item>
      <title>R-Pi Boot process</title>
      <link>https://kernelnomicon.org/posts/r-pi-boot-process/</link>
      <pubDate>Mon, 04 Jun 2012 20:12:12 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/r-pi-boot-process/</guid>
      <description>&lt;p&gt;Just a note to myself to keep useful info.
Bakul Shah in freebsd-arm quotes R-Pi forum, but I failed to find original.&lt;/p&gt;
&lt;blockquote&gt;
&lt;ol&gt;
&lt;li&gt;Stage 1 boot is in the on-chip ROM. Loads stage2 in the L2 cache!&lt;/li&gt;
&lt;li&gt;Stage 2 is bootcode.bin. Enables SDRAM and loads stage3&lt;/li&gt;
&lt;li&gt;Stage 3 is loader.bin.  Knows about elf format and load start.elf&lt;/li&gt;
&lt;li&gt;start.elf loads kernel.img (+ it is the main gpu code).
It reads config.txt, cmdline.txt and bcm2835.dtb
If the dtb file exists, it is loaded at 0x100 &amp;amp; kernel @ 0x8000
Else if disable_commandline_tags is set load kernel @ 0x0
Else if load kernel @ 0x8000 and put ATAGS at 0x100
See Issue 16 in &lt;a href=&#34;https://github.com/raspberrypi/linux/issues&#34;&gt;https://github.com/raspberrypi/linux/issues&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;kernel.img, is the &lt;em&gt;first&lt;/em&gt; thing that runs on the ARM
processor.&lt;/li&gt;
&lt;/ol&gt;
&lt;/blockquote&gt;
&lt;p&gt;And more information on config.txt &lt;a href=&#34;http://elinux.org/RPi_config.txt&#34;&gt;here&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>U-Boot for Raspberry Pi, step 3</title>
      <link>https://kernelnomicon.org/posts/u-boot-for-raspberry-pi-step-3/</link>
      <pubDate>Sun, 03 Jun 2012 14:06:30 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/u-boot-for-raspberry-pi-step-3/</guid>
      <description>&lt;p&gt;Finally I received my female/male cables for inter-board connects (my soldering skill is close to zero) and got FTDI-based TTL/USB converter work. I had more luck with it then with my old trusty TTL/RS232 converter. No garbage in linux output, serial input works for u-boot.&lt;/p&gt;
&lt;p&gt;You can find content of boot partition of SD-card I use &lt;a href=&#34;http://people.freebsd.org/~gonzo/r-pi/u-boot-pi.tar.gz&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Fully functional serial port means that boot-over-serial should work and I do not need to move SD-card between R-Pi and card reader to get new version of u-boot running. So based on &lt;a href=&#34;http://blog.mezeske.com/?p=483&#34;&gt;this post&lt;/a&gt; I managed to automate compile/run/fix cycle to some extent. Not C-Kermit expert here, so the script is lame but it does its work:&lt;/p&gt;</description>
    </item>
    <item>
      <title>U-Boot for Raspberry Pi, step 2</title>
      <link>https://kernelnomicon.org/posts/u-boot-for-raspberry-pi-step-2/</link>
      <pubDate>Sat, 26 May 2012 00:36:52 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/u-boot-for-raspberry-pi-step-2/</guid>
      <description>&lt;p&gt;I had some issues with console output from U-Boot on my R-Pi but Alexander Rybalko submitted patch that seems to fix them. One more issue that needed to be resolved: mysterious hangs in relocate_code. Some digging revealed that system hangs once PC reaches address 0x100. Some more digging yielded that at this address is used by GPU part of loader to store arguments for kernel.&lt;/p&gt;
&lt;p&gt;So after tweaking .text offset for u-boot and generating proper image using &lt;a href=&#34;https://github.com/raspberrypi/tools/tree/master/mkimage&#34;&gt;this tool&lt;/a&gt; I finally got:&lt;/p&gt;</description>
    </item>
    <item>
      <title>FreeBSD on Raspberry Pi: baby steps</title>
      <link>https://kernelnomicon.org/posts/freebsd-on-raspberry-pi-baby-steps/</link>
      <pubDate>Mon, 21 May 2012 20:47:43 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/freebsd-on-raspberry-pi-baby-steps/</guid>
      <description>&lt;p&gt;Thanks to Robert Watson I got my hands on brand new raspberry pi device (model B) and now trying to get FreeBSD running on it. That turned out to be non-trivial task. For one - there is no way to netboot the board. At least I failed to find it. It seems that initial Linux bring-up was done on evaluation modules with proper bootloader, JTAG support and whatnot and for public use limited boot loader was released. So instead porting FreeBSD on it I face the task of porting U-Boot. Which is not something entirely impossible.&lt;/p&gt;</description>
    </item>
    <item>
      <title>FreeBSD on ARM devices</title>
      <link>https://kernelnomicon.org/posts/freebsd-on-arm-devices/</link>
      <pubDate>Thu, 19 Apr 2012 18:20:25 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/freebsd-on-arm-devices/</guid>
      <description>&lt;p&gt;Damjan Marion published &lt;a href=&#34;http://people.freebsd.org/~dmarion/beaglebone/creating_bootable_sd_card/&#34;&gt;nice how-to&lt;/a&gt; for getting FreeBSD running on BeagleBone. Using it I managed to get my PandaBoard ES running off SD card. The only modifications to this instructions are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Use PANDABOARD kernel config. Stock version is configured to use NFS so it should be modified to use SD card as root.&lt;/li&gt;
&lt;li&gt;MLO and u-boot.bin binaries are different. I used &lt;a href=&#34;http://people.freebsd.org/~gonzo/pandaboard/&#34;&gt;these&lt;/a&gt;. You&amp;rsquo;ll need boot.scr too.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Performance is still affected by using write-through caches by default, but this issue should be fixed soon.&lt;/p&gt;</description>
    </item>
    <item>
      <title>FreeBSD/MIPS &amp; clang/LLVM</title>
      <link>https://kernelnomicon.org/posts/freebsdmips-clangllvm/</link>
      <pubDate>Mon, 18 Jan 2010 21:49:00 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/freebsdmips-clangllvm/</guid>
      <description>&lt;p&gt;Now I know a little bit more about clang. I can&amp;rsquo;t say it&amp;rsquo;s quite useful for MIPS yet, but it&amp;rsquo;s nice to see some progress in this field.  My findings might be inaccurate and any corrections are welcome.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;No proper cross-compilation so far. Clang team plans to do it &amp;ldquo;right way&amp;rdquo; but so far it&amp;rsquo;s just an item on their ToDo list: &lt;a href=&#34;http://clang.llvm.org/UniversalDriver.html&#34;&gt;Universal driver&lt;/a&gt;. There are command-line options like -ccc-host-triple  to get target assembler code, but names for assembler/linker are hardcoded to as/ld, which puts some restriction on building target toolchain&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;UPD: -ccc-host-triple does the trick OK&lt;/p&gt;</description>
    </item>
    <item>
      <title>Is it self-hosted yet?</title>
      <link>https://kernelnomicon.org/posts/is-it-self-hosted-yet/</link>
      <pubDate>Wed, 08 Jul 2009 17:18:00 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/is-it-self-hosted-yet/</guid>
      <description>&lt;p&gt;Good news everyone! Last two days I&amp;rsquo;ve been testing FreeBSD/mips by running buildworld on netbooted &lt;a href=&#34;http://wiki.freebsd.org/FreeBSD/mips/UBNT-RouterStation&#34;&gt;RouterStation&lt;/a&gt; with root mounted over NFS. So far so good, it successfully completed twice.&lt;/p&gt;
&lt;p&gt;A couple of weeks ago arch-dependent part of libthr (both kernel and userland) was implemented and it seems to work. &amp;ldquo;Seems to work&amp;rdquo; means that it passes thr1 and thr2 tests from stress2 and python&amp;rsquo;s test_thread[ing].py. And yes, python and perl build fine on the same board from the ports do work. As bash et al :) Though perl should be built without Perl malloc but it&amp;rsquo;s on my ToDo list.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Scheduled for reading</title>
      <link>https://kernelnomicon.org/posts/scheduled-for-reading/</link>
      <pubDate>Tue, 24 Feb 2009 00:33:00 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/scheduled-for-reading/</guid>
      <description>&lt;p&gt;Has just received two books from Amazon.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;http://www.amazon.ca/Beautiful-Architecture-Diomidis-Spinellis/dp/059651798X/ref=sr_1_3?ie=UTF8&amp;amp;s=books&amp;amp;qid=1235435653&amp;amp;sr=8-3&#34;&gt;&lt;img loading=&#34;lazy&#34; src=&#34;http://ecx.images-amazon.com/images/I/311e-9x8UQL._SL500_AA180_.jpg&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The first one is Beautiful Architecture by fellow FreeBSD developer Diomidis Spinellis and Georgios Gousios. I bought it because software design is not my strongest skill and there is a lot of place for improvement. And learning from real life examples is always better then reading pure theory.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;http://www.amazon.ca/Productive-Programmer-David-Bock/dp/0596519788/ref=pd_bxgy_b_img_b?ie=UTF8&amp;amp;qid=1235435653&amp;amp;sr=8-3&#34;&gt;&lt;img loading=&#34;lazy&#34; src=&#34;http://ecx.images-amazon.com/images/I/61dx4Iu-fyL._SL500_AA240_.jpg&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The other one is The Productive Programmer by David Bock. Productivity is my sweet spot (well, it&amp;rsquo;s more about cool tips then real productivity boost). This had nice reviews so I decided to give it a try.&lt;/p&gt;</description>
    </item>
    <item>
      <title>FreeBSD/MIPS: something lost, something gained</title>
      <link>https://kernelnomicon.org/posts/freebsdmips-something-lost-something-gained/</link>
      <pubDate>Tue, 04 Nov 2008 04:01:00 +0000</pubDate>
      <guid>https://kernelnomicon.org/posts/freebsdmips-something-lost-something-gained/</guid>
      <description>&lt;p&gt;And again long pause in blogging. In this 4 months several things happened to me: I relocated to Vancouver, was interviewed and rejected by Microsoft (don&amp;rsquo;t know why they contacted me in the first place), met new people (philip@ and thompa@ among them), saw new places and even got some free time and learned to cook (it turned out to be fun!).&lt;/p&gt;
&lt;p&gt;Being close(geographically) to PMC-Sierra, major MIPS vendor, I tried to contact them and ask for a donation for FreeBSD/MIPS project. Got no reply, though. Predictable result, but it&amp;rsquo;s better to try and fail then have never try at all.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
