So my idea is to wait until he test and merges that patch, then we can just upload the newer version (I can work on this).
Another issue is that this is incompatible with ES1, and this is the only board that we tested and have support (x-loader, u-boot and kernel). As we still don't have other packages, pushing a new ES2 compatible x-loader will probably get us to a state that neither boards will be working correctly, so I suggest we wait until we can have a proper kernel and tested boot-loader.
I asked prpplague if he could test and merge the 1gb patch from robclark (http:// gitorious. org/~robclark/ pandaboard/ robclarks- x-loader/ commit/ 1b391e2cb124038 109e7035a9ecebb 769784246b) so we could pack the right version from the first version, and he said he would probably do this today (friday).
So my idea is to wait until he test and merges that patch, then we can just upload the newer version (I can work on this).
Another issue is that this is incompatible with ES1, and this is the only board that we tested and have support (x-loader, u-boot and kernel). As we still don't have other packages, pushing a new ES2 compatible x-loader will probably get us to a state that neither boards will be working correctly, so I suggest we wait until we can have a proper kernel and tested boot-loader.
What do you think?
Until then you can just use my binaries at http:// people. canonical. com/~rsalveti/ maverick/ boot/es2/ (tested and it works fine).