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
On Tue, Aug 21, 2012 at 4:06 PM, Jerry Vonau jvo...@shaw.ca wrote:
While working with Australia, we have found the need to have the AC
plugged-in for a firmware update while not requiring AC for a image
upgrade to be problematic in the field. You can start an OS upgrade then
run out of battery
On Wed, 2012-08-22 at 09:53 -0600, Daniel Drake wrote:
On Tue, Aug 21, 2012 at 4:06 PM, Jerry Vonau jvo...@shaw.ca wrote:
While working with Australia, we have found the need to have the AC
plugged-in for a firmware update while not requiring AC for a image
upgrade to be problematic in the
On 23 August 2012 09:00, Jerry Vonau jvo...@shaw.ca wrote:
On Wed, 2012-08-22 at 09:53 -0600, Daniel Drake wrote:
Either way, I don't quite understand the situation involving the
firmware here. (Maybe until now) there has been no driving need to
upgrade firmware when upgrading OS releases - it
On Wed, Aug 22, 2012 at 06:00:21PM -0500, Jerry Vonau wrote:
Yes it did at one point, way back when sparse support was first
added to the .zd files in order to gain the speed advantage offered
the required firmware must be installed first.
That's not how I remember it. Sparse support worked
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
11 matches
Mail list logo
