| === cachio is now known as cachio_lunch | ||
| === cachio_lunch is now known as cachio_afk | ||
| === cachio_afk is now known as cachio | ||
| === lifeless_ is now known as lifeless | ||
| kees | ogasawara, apw: what's the state of the raspi2 port in ubuntu? | 21:01 |
|---|---|---|
| kees | (or raspi3) | 21:03 |
| kees | I note some config things aren't synced (like missing SW_DOMAIN_PAN on raspi2) | 21:03 |
| ogasawara | kees: heya, it's getting active security support and maintenance, so if something is missing or broken we should get that fixed | 21:08 |
| kees | ogasawara: ah, okay. I saw it in universe, so I wasn't sure. | 21:09 |
| kees | ogasawara: are there plans for an arm64 kernel for the raspi3? (and is there a hwe-edge for it, or is it just tracking the current LTS kernel?) | 21:09 |
| ogasawara | kees: ah, so I think arm64 landed in yakkety and zesty, but not in xenial | 21:11 |
| ogasawara | kees: and there isn't an hwe-edge for it unfortunately | 21:11 |
| ogasawara | kees: the linux-raspi2 package name is misleading too, since it does have support for raspi3 | 21:12 |
| ogasawara | kees: was there any other configs of concern you had noticed? | 21:15 |
| * ogasawara will file a tracking bug for SW_DOMAIN_PAN | 21:15 | |
| kees | nothing that jumped out yet (it's a 4.4 kernel, so most of the stuff I'm looking for is in later kernels) :) | 21:16 |
| ogasawara | ack | 21:17 |
| kees | ah-ha, i see the arm64 build now. cool. | 21:18 |
| kees | is there an install path for an arm64 image? all I can find is the 32-bit stuff... | 21:18 |
| ogasawara | kees: that one I'd have to check...but maybe slangasek knows off the top of his head? | 21:20 |
| ogasawara | slangasek: ^^ | 21:20 |
| slangasek | "install path"? | 21:20 |
| kees | like... where do I find the raspi arm64 server sdcard image for zesty? | 21:21 |
| slangasek | oh, are you asking whether we have an rpi3 image w/ 64-bit userspace? | 21:21 |
| kees | yes | 21:21 |
| slangasek | no | 21:21 |
| kees | ah-ha, okay :) | 21:21 |
| slangasek | :) | 21:21 |
| kees | is there a blocker for that? i.e. should it work in theory? | 21:22 |
| slangasek | it's not one of the reference images we're committed to providing | 21:22 |
| slangasek | rpi2/rpi3 are armhf reference; dragonboard is arm64 reference | 21:22 |
| kees | okay, understood. I've been mentally classifying arm as a dead arch like i386. :) | 21:23 |
| slangasek | now, should it work? you might be able to put together an ubuntu-core model assertion that takes the 64-bit userspace and combines it with the rpi3 ref kernel | 21:24 |
| slangasek | + gadget | 21:24 |
| slangasek | but we're not going to produce that image because we don't have the capacity to QA it | 21:25 |
| kees | gotcha | 21:25 |
| kees | oh, but just to be clear: there _is_ an arm64 userspace and there _is_ an arm64 kernel. :P so I should be able to make it work... | 21:58 |
| slangasek | kees: yeah, we have both of those pieces :) | 22:37 |
| kees | now I just have to figure out why apt doesn't talk on the network in a qemu-static-user chroot... :P | 22:38 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!