If you are working on an XO from serial port or the commandline, and
you want to drive NetworkManager to connect to your WLAN without using
X, here's what you can do.
In my case, I have an open AP, ESSID olpc
- Create /etc/NetworkManager/system-connections/olpc, containing:
[connection]
id=olpc
Hi,
We want to follow the upstream direction of dynamically driving
hardware detection by the firmware-provided device tree, rather than
hardcoding a board file into the kernel.
We have in-development kernel and firmware versions that make this
move, but we need to do this in a way that doesn't
daniel wrote:
Hi,
We want to follow the upstream direction of dynamically driving
hardware detection by the firmware-provided device tree, rather than
hardcoding a board file into the kernel.
We have in-development kernel and firmware versions that make this
move, but we need to
I do not have an XO-1.75. But with other XO models, I update firmware
INDEPENDENTLY of updating the distribution, and update the kernel
INDEPENDENTLY of updating the firmware or the distribution. Surely I am
not alone in the world in doing so.
If stable (old) kernels will not boot with
On Tue, 2012-08-21 at 12:04 -0600, Daniel Drake wrote:
Hi,
We want to follow the upstream direction of dynamically driving
hardware detection by the firmware-provided device tree, rather than
hardcoding a board file into the kernel.
We have in-development kernel and firmware versions that
On Tue, Aug 21, 2012 at 12:04:04PM -0600, Daniel Drake wrote:
2. Append the XO-1.75 device tree to the kernel image.
We also hope to boot this same kernel on other hardware, so it might
be necessary to include multiple device trees in this kernel.
This is my favourite option - while we would
On Tue, Aug 21, 2012 at 7:24 PM, James Cameron qu...@laptop.org wrote:
On Tue, Aug 21, 2012 at 12:04:04PM -0600, Daniel Drake wrote:
2. Append the XO-1.75 device tree to the kernel image.
We also hope to boot this same kernel on other hardware, so it might
be necessary to include multiple
