Commit graph

11 commits

Author SHA1 Message Date
David Guibert 5db26b465e update kernels
svn path=/nixpkgs/trunk/; revision=28437
2011-08-09 20:04:03 +00:00
Eelco Dolstra 5a08a41204 * Kernel updates.
svn path=/nixpkgs/trunk/; revision=22941
2010-08-04 10:40:25 +00:00
Eelco Dolstra 237c7808ce * Latest Linux kernels.
svn path=/nixpkgs/trunk/; revision=22488
2010-07-06 08:44:05 +00:00
Eelco Dolstra 8f99f22819 * Kernel updates.
svn path=/nixpkgs/trunk/; revision=22002
2010-05-27 12:16:05 +00:00
Eelco Dolstra a310fc9ed0 * Latest kernels.
svn path=/nixpkgs/trunk/; revision=21874
2010-05-19 12:28:54 +00:00
Eelco Dolstra 68d9e26bcb * Linux 2.6.32.12, 2.6.33.3.
svn path=/nixpkgs/trunk/; revision=21338
2010-04-27 09:52:36 +00:00
Eelco Dolstra 5330be5fbb * Latest Linux kernels.
svn path=/nixpkgs/trunk/; revision=20952
2010-04-06 10:33:49 +00:00
Eelco Dolstra f02cd9d59c * Linux updated to 2.6.32.10, 2.6.33.1.
svn path=/nixpkgs/trunk/; revision=20646
2010-03-16 11:44:28 +00:00
Lluís Batlle i Rossell 289d728337 Fixing the kernel expressions to allow normal and cross-building, depending
on the native and cross platforms.

I thought I already did that today in a previous commit, but I did all wrong.

svn path=/nixpkgs/trunk/; revision=20280
2010-02-27 21:48:48 +00:00
Lluís Batlle i Rossell 11aa65c28a Simplified much more the expressions for cross building and multiplatform.
I introduce the new nixpkgs parameter "platform", defaulting to "pc",
which was before defined as an attribute of nixpkgs.

I made the crossSystem nixpkgs attribute set parameter contain its own 'platform'.

This allows cross-building a kernel for a given crossSystem.platform in a non-PC
platform.

The actual native platform can be taken from stdenv.platform, and this way we also
avoid the constant passing of 'platform' to packages for platform-dependant builds
(kernel, initrd, ...).

I will update nixos accordingly to these changes, for non-PC platforms to work.

I think we are gaining on flexibility and clearness. I could cross build succesfully
an ultrasparc kernel and a mipsel kernel on PC. But since this change, I should be able
to do this also in non-PC.

Before this change, there was no possibility of distinguishing the "target platform" or
the "native build platform" when cross building, being the single "platform" attribute
always interpreted as target platform.

The platform is a quite relevant attribute set, as it determines the linuxHeaders used
(in the case, by now the only one supported, of linux targets).

The platform attributes are quite linux centric still. Let's hope for more generality to come.

svn path=/nixpkgs/trunk/; revision=20273
2010-02-27 17:35:47 +00:00
Eelco Dolstra e04c9a452a * Linux 2.6.33.
svn path=/nixpkgs/trunk/; revision=20246
2010-02-25 12:40:03 +00:00