[meta-ti] Koen Kooi : u-boot 2011.09+git: update to latest version of Tom Rini's tree
Tom Rini
trini at ti.com
Thu Aug 2 15:37:52 PDT 2012
On Thu, Aug 02, 2012 at 06:06:22PM -0400, Denys Dmytriyenko wrote:
> On Wed, Aug 01, 2012 at 12:12:14PM -0700, Tom Rini wrote:
> > On Thu, Jul 26, 2012 at 01:57:27AM +0000, Kridner, Jason wrote:
> > >
> > > -----Original Message-----
> > > From: Arago Project git <git at arago-project.org>
> > > Date: Wednesday, July 25, 2012 9:32 PM
> > > To: "meta-ti at yoctoproject.org" <meta-ti at yoctoproject.org>
> > > Subject: [meta-ti] Koen Kooi : u-boot 2011.09+git: update to latest
> > > version of Tom Rini's tree
> > >
> > > >Module: meta-ti
> > > >Branch: master
> > > >Commit: e1b4ab72cfb3ea4599701d1600c44fe3c5f8ba66
> > > >URL:
> > > >http://arago-project.org/git/meta-ti.git?a=commit;h=e1b4ab72cfb3ea4599701d
> > > >1600c44fe3c5f8ba66
> > > >
> > > >Author: Koen Kooi <koen at dominion.thruhere.net>
> > > >Date: Wed Jul 11 11:53:27 2012 +0200
> > > >
> > > >u-boot 2011.09+git: update to latest version of Tom Rini's tree
> > >
> > > Aren't all of Tom's patches upstream now? Why not pull from the latest
> > > u-boot release? Are we carrying any patches that would be accepted
> > > upstream?
> >
> > Late to the party, I know. v2012.07 has extremely minimal support for
> > am335x platforms. With 3 series of patches (which I expect to queue up
> > and push along to u-boot-arm and then u-boot proper) mainline support
> > should be better, at least wrt bone, than the arago tree. NAND and SPI
> > and MMC1 won't be there, yet. i2c, ethernet, booting kernels will be
> > there. And easier than arago eeprom programming will be there too
> > (eeprom command in U-Boot for dumping memory to eeprom).
>
> Tom,
>
> Why are you comparing to "arago u-boot"? Isn't that your tree also? :)
I know you know but for the record..
It's a product tree that I am the responsible party for. I'm also the
custodian of the TI parts in mainline U-Boot. The goal is to one day be
able to make the tree on arago just be for historical reference and have
everyone using mainline (or mainline with distro / product / etc
specific patches). We're getting much nearer the point where I think
folks can switch to the mainline tree. Some peripherals that can be
exposed via capes wouldn't be supported today but the important ones on
a beaglebone would be.
The other side of things is that barring a product related need I don't
add new features (and then backport as much as possible from mainline)
to the arago hosted tree. So improved / easier eeprom writing isn't
likely to end up there :)
--
Tom
More information about the meta-ti
mailing list