RFC: Fedora mipsel secondary architecture plan

[Aron Xu]

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

-- 
Regards,
Aron Xu

[Fai Wong (lazyfai)]

Hi all,

I would like to join and see anything I can help, if there is any base
system built for F15/16.

But currently I am very busy on my day job so my Loongson 2f is idling
(running F13)

Cheers,
Fai

2011/7/3 Aron Xu <happyaron.xu(a)gmail.com&gt;:
>  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
>
>  --
>  Regards,
>  Aron Xu
>
>  _______________________________________________
>  mips mailing list
>  mips(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/mips
>
>

[Sérgio Basto]

On Sun, 2011-07-03 at 15:21 +0800, Aron Xu wrote:
>  
>   * 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. 
where I found "a working n32 ABI" ? 

Thanks, 
-- 
Sérgio M. B.

[Aron Xu]

On Mon, Jul 04, 2011 at 06:07:10PM +0100, Sérgio Basto wrote:
>  On Sun, 2011-07-03 at 15:21 +0800, Aron Xu wrote:
>  > 
>  >  * 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.
>  
>  where I found "a working n32 ABI" ? 
>   
Please have a look at this page:
http://fedoraproject.org/wiki/Arch:MIPS

-- 
Regards,
Aron Xu

[Gerard Braad]

Hi All,

On Tue, Jul 5, 2011 at 3:55 PM, Aron Xu <happyaron.xu(a)gmail.com&gt; wrote:
>  On Mon, Jul 04, 2011 at 06:07:10PM +0100, Sérgio Basto wrote:
> > On Sun, 2011-07-03 at 15:21 +0800, Aron Xu wrote:
> > >  * 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.
> > where I found "a working n32 ABI" ?
>  Please have a look at this page:
>  http://fedoraproject.org/wiki/Arch:MIPS 
currently just observing the list until I have some time this weekend.
Already got in touch with yujie of China Standard Software (CS2C, 中标软件)
Let's create a breakdown of what is needed.

Also would like to invite you to the FUDCon APAC if in Beijing else
the upcoming FAD.
I'll email you the details when more is known. I also expect Fai Wong
and Xin Zhen to attend this ;-)


Gerard

-- 
Gerard Braad — 吉拉德
   Project-lead Fedora-MIPS
   Regional Mentor for APAC/China, Member of FAmSCo
   http://fedoraproject.org/wiki/User:gbraad

[Zhen Xin]

+1

[liang liang wang]

抱歉能用中文吗，看起来有些费劲！

谢谢




2011/7/3 Aron Xu <happyaron.xu(a)gmail.com&gt;

>  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
>
>  --
>  Regards,
>  Aron Xu
>
>  _______________________________________________
>  mips mailing list
>  mips(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/mips
>
>

[Peter Robinson]

On Sun, Jul 3, 2011 at 8:21 AM, Aron Xu <happyaron.xu(a)gmail.com&gt; 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