snappy on raspberry pi 2: DHCP, I2C

[Paolo Pisati]

for i2c, as a stop gap:

sudo modprobe i2c-chardev

should fix it, i'll release a kernel with that builtin.

On Thu, Jun 11, 2015 at 9:55 AM, roger peppe <roger.peppe at canonical.com>
wrote:

> Hi,
>
> I'm a total snappy and rpi newbie, just acquired an
> orange matchbox to play with and very much feeling my way,
> so my apologies if the answers to these questions are obvious.
>
> The snappy image that I'm using is (I think) the
> latest image from here
> http://people.canonical.com/~lool/pi2-device-and-oem/
>
> Two initial questions:
>
> 1) How can I get snappy to DHCP automatically after booting?
> I was expecting the network to come up right away, but
> I need to manually run "dhclient eth0" to get the network
> working.
>
> 2) What's the status of I2C devices/drivers? Various software
> (e.g. github.com/schoentoon/piglow, which I'm particularly
> interested in because I'd like to drive the piglow device from
> Go) assumes the existence of /dev/i2c-*, which isn't
> there. Do we need to do this in userspace?
>
>   cheers,
>     rog.
>
> --
> snappy-devel mailing list
> snappy-devel at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/snappy-devel
>



-- 
bye,
p.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snappy-devel/attachments/20150611/53e804fa/attachment.html>