Am 21.08.2014 13:26, schrieb Guillaume Gardet: > Le 21/08/2014 09:40, Matwey V. Kornilov a écrit : >> 2014-08-21 11:31 GMT+04:00 Guillaume Gardet<[email protected]>: >>> Is it mainlined now or not? I think some times ago Dirk said to drop >>> sunxi >>> patches from Base:System and handle them at a project level. Dirk, >>> could you >>> confirm, please? >> Mele_A1000 and Hyundai_A7HD are missed from upstream u-boot. >> > > I think it would be best to handle non upstream u-boot boards separately > and only keep upstream boards in u-boot from Base:System. What do you > think about that?
+1 We already have a Contrib:sunxi, where we could place it. In v2014.07 however, only Cubietruck was present, not Cubieboard and Cubieboard2, for which - unlike Mele and Hyundai - we have JeOS images somewhere. > I reworked our EXT2 support for MLO (SPL for OMAP) to ease upstreaming. > I based my work on Matwey update (2014.10-rc1). > See: > https://build.opensuse.org/project/monitor/home:Guillaume_G:branches:Base:System About v2014.10-rc1 I'm more doubtful. To build JeOS images, we need to submit u-boot to Factory, so Base:System and Factory(:ARM) will be pretty much the same all the time. So I'm thinking it may make sense to update Base:System to the latest stable only, which still is v2014.07, and do the v2014.10-rc1 in, e.g., devel:ARM:Factory. If we put the resulting u-boot on an SD card it is less of a problem if something in the -rc breaks; but for flashing U-Boot, bricking the device is a risk. So I see this similar to keeping Kernel:HEAD separate from Factory. Last time I checked, there was no real OpenOCD package in OBS (only some old one in a home:), and it requires JTAG hardware, connectors on the board and config files matching the board. Opinions? Regards, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
