> OK, I have made use of the MCP23008 and MCP23017, 8 bit and 16 bit GPIO
> expanders that are I2C connected on Raspberry Pis. The Raspberry Pi kernels
> include both an overlay (Device Tree Blob) and a driver module for the
> MCP23008 and MCP23017 chips. I would also like to make use of these chips on
> my beagle boards (a BeagleBoneBlack and a PocketBeagle).
> I just did some poking around on my BBB, and there are neither Device Tree
> Blobs nor driver modules for the MCP23008 and MCP23017 chips.
> So, my question is: What is involved in building the missing driver modules
> and Device Tree Blobs -- I have built driver modules and even rebuilt whole
> kernels on x86 Linux boxen, so I have passing knowledge of how that goes, what
> I am really wondering: is there a repo with .deb files containing the "extra"
> ko files? Or tarballs containing the additional sources? I realize the BBB
> and PB are rather slow, so maybe I should cross build this on one of my Pis?
> Or is there an alternitive kernel I can upgrade to that includes these
> Right now my two Beagles are running 4.14.71-ti-r80, Debian GNU/Linux 9,
> BeagleBoard.org Debian Image 2018-10-07. I did do a apt-get update/apt-get
> dist-upgrade about a month ago (May 14).
it's enabled, just after r80 came out.. Just run, and then reboot..
OK, I did the above and did a apt-get dist-upgrade.
The kernel module is there, but there isn't a Device Tree Blob for the *I2C*
mcp23* chips, just a Device Tree Blob
(/lib/firmware/BB-SPI0-MCP23S08-00A0.dtbo) for the SPI interface.
During the kernel update the package linux-firmware-image-4.14.108-ti-r106 was
suggested, but apt-get install is complaining when I try to install it:
snoopy% sudo apt-get install linux-firmware-image-4.14.108-ti-r106
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package linux-firmware-image-4.14.108-ti-r106 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or is only available from another source
E: Package 'linux-firmware-image-4.14.108-ti-r106' has no installation candidate
I do have device tree blobs on the RPi and can get a device tree blob source
file from the RPi device tree source repo. I guess it is *possible* to
compile a device tree blob for the beagles, but want to be sure and would
rather get a device tree blob properly built for the Beagles.