[07:36] <flexiondotorg> ogra_, I was at a Rasspberry Jam yesterday.
[07:36] <flexiondotorg> I have a preview or Ubuntu MATE 15.10 and we also played with Ubuntu Snappy.
[07:37] <flexiondotorg> ogra_, The feedback about Ubuntu Snappy is that without firmware and VideoCore drivers/utilities it is limited.
[07:37] <flexiondotorg> ogra_, I have this issue with Ubuntu MATE 15.10 right now too.
[07:38] <flexiondotorg> Because the 15.10 kernel is 4.2 and Rpi2 firmware is only available for kernel 4.1 and 3.18.
[07:39] <ogra_> flexiondotorg, well, there are plans to make the KMS/DRM driver work
[07:39] <flexiondotorg> I'd like to work on getting the Pi2 better supported on Ubuntu.
[07:39] <ogra_> but that wont get you the same features the closed driver will
[07:39] <flexiondotorg> flexiondotorg, Are you referring to the accelerate DDX?
[07:40] <ogra_> no, i'm referring to the opensource one
[07:40] <flexiondotorg> ogra_, Just want to clarify what you mean.
[07:40] <flexiondotorg> Do you mean fbturbo?
[07:41] <ogra_> i dont know how it is called, afaik there is an opensource KMS capable driver, but that only does 2D accel
[07:41] <flexiondotorg> Or this - https://github.com/Factoid/xf86-video-rpi
[07:41] <ogra_> it should work with the KMS xorg driver
[07:41] <flexiondotorg> ogra_, So the issue is this.
[07:42] <flexiondotorg> The pi2 without firmware, much of the hardware is simply not enabled.
[07:42] <flexiondotorg> Some missing i2c, sound and accessible to video acceleration.
[07:42] <ogra_> do you use the right DTB overlays in your install ?
[07:42] <flexiondotorg> ogra_, Well, this is an interesting question.
[07:42] <ogra_> i2c is definitely enabled by default in our snappy install
[07:43] <flexiondotorg> ogra_, My understanding is that the Rpi2 firmware is required to enable those devices though.
[07:43] <flexiondotorg> Which DTB are you using and how have you enabled it?
[07:45] <ogra_> we use the default DTB only but allow enablin the overlays ... the default one includes SPI, I2C and I2S support that cou can switch on or off with a dt parameter in config.txt
[07:46] <ogra_> and we ship a set of overlays you can use to en/disable the other devices http://paste.ubuntu.com/12761947/
[07:47] <flexiondotorg> ogra_, OK. So what "installs" those overlays for Snappy?
[07:47] <flexiondotorg> Are you are using uboot in Snappy?
[07:47] <ogra_> the kernel package
[07:47] <ogra_> we chainload uboot from the binary bootloader
[07:47] <flexiondotorg> Ah, right.
[07:48] <ogra_> the DT config has to happen in the binary bootloader config.txt though
[07:48] <flexiondotorg> Yes.
[07:48] <ogra_> uboot can only read it from ram, it cant apply it to the kernel during boot (sadly a limitation of the rpi port)
[07:49] <ogra_> the dtbs come with your kernel packae under /lib/firmware
[07:49] <ogra_> copy them to the overlays directory in your bootloader setup and config.txt can see them
[07:50] <flexiondotorg> ogra_, OK, that is interesting.
[07:50] <flexiondotorg> I'll take a look at the linux-rpi2 source packages to better understand the above.
[07:51] <ogra_> you dont need the "firmware" (whatever people mean when saying that) to bring up devices ...
[07:51] <flexiondotorg> I was thinking of making a PPA with some packages to provide the firmware but that maynot be required.
[07:51] <flexiondotorg> Hah ^^^ :-)
[07:52] <flexiondotorg> But I do need the VideoCore device to be available, which currently it is not.
[07:52] <ogra_> the onlly "firmware" is the binary blob (start.elf, fixup.dat) ... everything past this is kernel
[07:53] <ogra_> and shits firmware is the binary blob for the graphics driver, with some bootloader code added
[07:53] <ogra_> s/hits/this/ ... tsk
[07:53] <ogra_> (freudian slip :P )
[07:53] <flexiondotorg> OK, so I need to figure out why the VideoCore device is not acceeible then.
[07:54] <flexiondotorg> OK, thanks for the pointers.
[07:54] <flexiondotorg> I'll see what I can figure out.
[07:55] <flexiondotorg> ogra_, Which source package is providing the firmware for the rpi2?
[07:56] <ogra_> the pi2.snap from the store
[07:57] <flexiondotorg> ogra_, Ah.
[07:57] <flexiondotorg> That firmware is not in the Debian packages/
[07:57] <flexiondotorg> ?
[07:57] <ogra_> http://people.canonical.com/~platform/snappy/raspberrypi2/ has a copy ... (you can unpack snaps with "dpkg-deb -x  /path/to/snap ./unpack")
[07:57] <ogra_> no, the oem snaps usually dont have a deb equivalent
[07:58] <ogra_> (and many normal snaps dont have either ... snappy can use debs but doesnt need to, in fact the expectation is that people build upstream trees directly for it )
[08:00] <flexiondotorg> ogra_, Understood.
[08:00] <flexiondotorg> We were talking a cross purposes. My mistake.
[08:00] <flexiondotorg> Ubuntu MATE 15.10 is not snap based.
[08:00] <ogra_> i know
[08:00] <flexiondotorg> I'm using the linux-raspi2 package.
[08:00] <flexiondotorg> In a traditional Debian setup.
[08:01] <ogra_> right
[08:01] <ogra_> so you need to find a bootloader setup that works
[08:01] <ogra_> and integrates properly with the kernel bits ... i.e. your installer shoudl copy the overlay bits into the right place
[08:02] <flexiondotorg> So, I have a bootable image.
[08:02] <flexiondotorg> With X and Ubuntu MATE working.
[08:02] <flexiondotorg> Just missing something for some devices.
[08:03] <flexiondotorg> I'm pulling down that snap and having a look.
[08:03] <ogra_> well, you are most likely using the dtb from the bootloaer that you got "somewhere" ...
[08:03] <ogra_> which means nearly no devices will work at all because the dtb is kernel specific
[08:04] <flexiondotorg> This is where I run out of rope.
[08:04] <ogra_> (RaspberryPi2)ubuntu@localhost:~$ ls /lib/firmware/4.2.0-1008-raspi2/device-tree/
[08:04] <ogra_> bcm2709-rpi-2-b.dtb  overlays
[08:04] <flexiondotorg> I'm not sure if the issue I am facing is because of the mismatch between Linux 4.2 (in 15.10) and the DTBs provided by Raspberry pi foundation that are for Linux 4.1.
[08:05] <ogra_> you want to have the content of this sitting in the dir of your bootloader (likely some vfat partition on your SD)
[08:05] <flexiondotorg> Perfect!
[08:05] <flexiondotorg> I'll give that a shot.
[08:05] <ogra_> just replace the stuff
[08:07] <flexiondotorg> Is the content of /lib/firmware/4.2.0-1008-raspi2/device-tree/ to same as I am seeing in pi2_0.16_all.snap boot-assets?
[08:07] <flexiondotorg> *the same as?
[08:07] <flexiondotorg> Because if so, I'll integrate that snap into my build.
[08:08] <flexiondotorg> I'd like to align with the snappy stuff as much as possible.
[08:23] <flexiondotorg> ogra_, This short thread is why I thought (and am still not sure) that the Raspi firmware and kernel version mismatch affect VideoCore enablement - https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=120977
[08:29] <flexiondotorg> ogra_, And this ;-)
[08:29] <flexiondotorg> https://bugs.launchpad.net/snappy/+bug/1500755
[08:32] <ogra_> flexiondotorg, well, thats most likely a question of enabling it in the kernel config (it seems all you need is the right module)
[08:34] <flexiondotorg> Which is closed source :-(
[11:47] <Guest47548> hello everyone, could anyone please give me some help, i don't know if i broke my microsd or not, i was trying to dd write a .raw file to a microsd card then it didn't work, something went wrong and it says my 16gb card only has 8mb (unllocated)
[21:03] <regum> hello everyone
[21:03] <regum> I was wondering if anyone has had any success in installing ROS on Ubuntu 15 (arm)
[22:26] <mijk> Is it possible to stream Steam to an ARM machine?