Hi all,
I am writing to ask for your comments about a secondary architecture plan, as now a company named Cs2c[1] would like to provide essential manpower and other resources (hardware, hosting, etc.) to support fedora-mips port to catch up with the primary architectures. First, let me introduce our situation:
* fedora-mips team's previous works are almost based on 64bit loongson2f hardware, which is little endian (and should be called "mips64el" instead of "mips" when accuracy does matter). The team have already built a working n32 ABI Fedora 13.
* Cs2c is an OS vender which builds its products based on Fedora. Now it is determined that the company will work on loongson based architectures in the foreseeable future, hence it would like to support fedora-mips in any way it can (manpower, hardware for porting and building, hosting for koji and mirror servers, etc).
We'd like to start our work based on F13, to build Koji builders (DONE), and build a usable base system by cherry-picking SRPMs from Rawhide, then bootstrap koji to do full archive rebuild.
When F16 is branched, we'll move our focus to it and continue the auto builds of Rawhide software, which will make our life easier when F17 development cycle is kicked off. During F16 development cycle, it is expected to meet problems and we may produce a number of patches, these patches will be submitted to corresponding package maintainers when it's tested to be working. And we wish during the F17 development cycle there won't be too much duplicate work to be done.
Any ideas and/or comments please?
[1]http://www.cs2c.com.cn/index.php?styleid=2
On Sun, Jul 3, 2011 at 8:21 AM, Aron Xu happyaron.xu@gmail.com wrote:
Hi all,
I am writing to ask for your comments about a secondary architecture plan, as now a company named Cs2c[1] would like to provide essential manpower and other resources (hardware, hosting, etc.) to support fedora-mips port to catch up with the primary architectures. First, let me introduce our situation:
- fedora-mips team's previous works are almost based on 64bit loongson2f
hardware, which is little endian (and should be called "mips64el" instead of "mips" when accuracy does matter). The team have already built a working n32 ABI Fedora 13.
- Cs2c is an OS vender which builds its products based on Fedora. Now
it is determined that the company will work on loongson based architectures in the foreseeable future, hence it would like to support fedora-mips in any way it can (manpower, hardware for porting and building, hosting for koji and mirror servers, etc).
We'd like to start our work based on F13, to build Koji builders (DONE), and build a usable base system by cherry-picking SRPMs from Rawhide, then bootstrap koji to do full archive rebuild.
When F16 is branched, we'll move our focus to it and continue the auto builds of Rawhide software, which will make our life easier when F17 development cycle is kicked off. During F16 development cycle, it is expected to meet problems and we may produce a number of patches, these patches will be submitted to corresponding package maintainers when it's tested to be working. And we wish during the F17 development cycle there won't be too much duplicate work to be done.
Any ideas and/or comments please?
Please submit all patches needed to spec files and any other bugs to bugzilla and link against a MIPS tracking bug. All issues that need patches to source code should be submitted directly upstream to the appropriate project.
Regards, Peter
secondary@lists.fedoraproject.org
-
Aron Xu -
Peter Robinson