| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
And add API to make this contract stronger.
Some chrooted kspost scripts are now interested in knowing the laptop
model number.
|
|
|
|
| |
This is no longer a dependency of the kernel package.
|
|
|
|
|
| |
olpc-firmware is being renamed to olpc-firmware-qX for different
machine types.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As recently discussed on the devel list, we switch to a new naming
scheme for builds, encompassing more details than before.
See http://wiki.laptop.org/go/Release_Process#Version_numbering
for more info.
The name is now built from:
1. Fourth digit of the four-digit year corresponding to the Major Release
2. The release number within the current year
3. Three-digit zero-padded build number
4. An alphabetic 'deployment identifier', max 2 characters
5. A numeric code identifying the target laptop model.
|
| |
|
|
|
|
| |
Now moved to device-tree
|
|
|
|
| |
Includes package list updates, port to systemd, etc.
|
| |
|
|
|
|
|
|
| |
/ofw promfs is not used on XO-1.75, and is only temporarily used on
XO-1/XO-1.5 while they have not yet moved to kernels that have
auto-mounted /proc/device-tree
|
|
|
|
|
| |
We have the mesh network there for the under a tree
scenario.
|
|
|
|
| |
This doesn't apply to ubifs.
|
|
|
|
| |
Needed for ubifs support.
|
|
|
|
| |
We've obtained the information that we were looking for in #9100.
|
|
|
|
|
|
|
|
| |
We're seeing some reports of boot hangs which aren't entirely unexpected
(e.g. see http://dev.laptop.org/ticket/9100 )
Disable pretty boot so that we can get a better grasp on where the
problem lies.
|
|
|
|
|
| |
Recent firmware releases enable SMBIOS by default.
And olpc-configure can cope when it's not enabled.
|
| |
|
| |
|
|
|