Martin Langhoff mar...@laptop.org writes:
On Wed, Aug 22, 2012 at 2:27 AM, Sascha Silbe si...@activitycentral.com
wrote:
It's probably worth noting that you only have to jump through all these
hoops for NM = 0.8 / Sugar = 0.94. For NM 0.9 / Sugar 0.96+ all you
need to do is:
nmcli con up
On Thu, Aug 23, 2012 at 3:16 AM, Sascha Silbe si...@activitycentral.com wrote:
Have you connected to the AP at least once through Sugar?
Freshly installed systems on a new motherboard where X was not coming
up until a few days ago. We happen to be working on a motherboard to a
new model. :-)
Thanks everyone for the discussion. I know this issue is not the #1
priority right now so I've summarised it in a wiki page:
http://wiki.laptop.org/go/Device_tree_upgrade_considerations
(edits welcome)
We can revisit the topic at a point in the near future.
Daniel
Hi,
Here is the first pass at camera support from the device tree.
Firmware patch:
http://dev.laptop.org/~dsd/20120823/fw-camera.patch
Kernel patch:
http://dev.laptop.org/~dsd/20120823/kernel-camera.patch
My next step is to explore putting the camera node as a child of the
camera-i2c node
shep was just filing a ticket, and had no way of finding someone's
trac nick, based on their real name. that reminded me that we could
still use a page of some sort that lets one do that lookup.
of course i have no idea how difficult that would be. even a link to
a ticket whose description
