> Perhaps you are looking for this?
Thanks but unfortunately no. I am looking for the specific version and
patches that made up the new U-Boot and MLO binaries that have been
announced for download at the beginning of this thread.
So you are looking for Steve Sakoman's git tree? Google can help you there.
For the version before this one I did have the right sources and after
some tweaking I could compile them myself to understand and make
modifications for my project.
But now there is a new binary version made from unknown sources (I
just got the hint: "it is all in OE") - and therefore I can't apply my
own patches and use an unknown binary. Or I have to continue without
the latest changes. Or I have to reverse engineer OE. Neither option
looks attractive to me, doesn't it?
The announcement tells you exactly where the sources came from (Steve Sakoman's
tree). If you are making modifications to u-boot, then you probably ought to
just be tracking Steve's tree directly anyways. It will make life substantially
easier when it comes time to rebase (i.e. now).
> For this, you'll need to look at the recipe, which really isn't that
> tough to
> find. In the openembedded tree, you want the /recipes/u-boot (IIRC)
This requires to download the full OE tree just to find 2 files where
the information is located (I think there is a downloads list and a
patches list within each recipe). Maybe, someone who already has OE
installed can send me the (latest!) version of the recipies of U-Boot
and the new MLO.
Nope, gitweb (err, cgit) is your friend,
> I suspect, however, that the recipe simply configures u-boot with
> the correct
> machine type. Just a guess though.
Most probably it is so for the real build phase. But that is not my
issue - it is getting the correct source package.
In my view and experience the complexity nowadays lies in the
multitude of different source repositories and how easy it became to
make new and only slightly differing versions. Tracking down the
correct sources has become more complex by that.
It really isn't that difficult. You simply need to read. The announcement told
you exactly where to look.
OE tries to make life easy by having a central list of this information.
Which is a very good idea. But it adds one level of complexity to all those
who do not just want to or can not use the OE magics. Up to some years ago
the task I am trying to do was simple: each project did have a FTP server
where the sources were happily sorted by version number as a
And now it's even easier.
$ git clone <repo>
$ git checkout <branch/tag> (optional)
So to recap, it's not difficult, you simply need to know where to look. There
is absolutely nothing magical about OE, it's just a convenient way to compile
things. Granted, the few patches still held in OE should be upstreamed, but
there's probably good reason for waiting that I'm not aware of and none of them
appear to be all that crucial.