Similar Posts
Simple pf for Raspberry Pi
One of the best things about the Pi is that it’s small, and portable. It’s very tempting to use it on wireless networks, unattended. Sadly, in the real world, any wireless network can be hacked, and any device on wireless should be considered vulnerable. So, pf is an easy way to harden your Pi. The…
The FreeBSD FDT, the Raspberry PI SPI
How the FDT works In specific, I’m looking at this file bcm2835.dtsi which contains the hardware definitions for the BCM2835, the SOC which powers a Raspberry Pi. Primarily, i’m interested in how to read it. To really make sense of this, you should have this pdf at hand; it’s the hardware manual for BCM2835. If…
Spelunking Apple DOS 3.3 DSK files
If you happen to have had an Apple][, you might be interested in retrieving your data from old DOS 3.3 floppies. Or maybe you’re just interested in retrocomputing and downloaded some floppies at Apple2Online. In my case, I had an ulterior motive. I’ve been learning about FreeBSD device drivers and was wondering how difficult it…
The skeleton of a FreeBSD driver
It’s been a goal of mine for a while to understand how FreeBSD device drivers work. So, firstly I wrote a simple module; it’s here. The next step is to write the skeleton of a device driver. That is, a device driver that does nothing. The resulting source code is here. The Makefile is very…
Time Machine backups using FreeBSD ZFS
In this blog article, I described a way to use Netatalk3 to do Time Machine backups on FreeBSD. This approach worked well, but it had some problems: The Time Machine backups are in every user’s home dir. That’s messy and there is the potential that they’ll accidentally delete the backup. If I put the backups…
Bare Metal coding on FreeBSD
I recently got interested in the technical details of how ARM OS’s work, so I decided to try my hand at writing a simple one. This blog post is not about the OS itself, but about setting up the development environment. In my case, I’m developing in a terminal session, on FreeBSD 10 on an…
2 Comments
Leave a Reply Cancel reply
This site uses Akismet to reduce spam. Learn how your comment data is processed.
Did you intentionally remove i2c support from r270855?
root@wandboard:/dev # ofwdump -a | grep i2c
Node 0x143c: i2c@021a0000
Node 0x14a8: i2c@021a4000
Node 0x1518: i2c@021ac000
root@wandboard:/dev # kldstat -v | grep iic
130 i2c/iicbus
58 iichb/ofw_iicbus
57 iicbb/ofw_iicbus
16 iichb/iicbus
15 iicbus/iic
root@wandboard:/dev # ls -l /dev/iic*
ls: No match.
Same board with r268304
root@wandboard:~ # ofwdump -a | grep i2c
Node 0x1538: i2c@021a0000
Node 0x15d0: i2c@021a4000
Node 0x1668: i2c@021a8000
root@wandboard:~ # kldstat -v | grep iic
131 i2c/iicbus
13 iichb/iicbus
12 iicbus/iic
55 iichb/ofw_iicbus
54 iicbb/ofw_iicbus
root@wandboard:~ # ls -l /dev/iic*
crw——- 1 root wheel 0x20 Jul 6 01:29 /dev/iic0
crw——- 1 root wheel 0x21 Jul 6 01:29 /dev/iic1
crw——- 1 root wheel 0x22 Jul 6 01:29 /dev/iic2
Just curious. I guess it’s time to try out crochet.
Nope, I didn’t.