• Debian/MIPSeb: proposal to drop mipseb port?

    From YunQiang Su@21:1/5 to All on Sat Jul 7 17:00:01 2018
    Paul Wise <pabs@debian.org> 于2018年7月7日周六 下午10:41写道:

    On Sat, Jul 7, 2018 at 10:31 PM, YunQiang Su wrote:

    In fact I don't know anybody is using Debian's mips32eb port.

    I used jessie mips on my router in a chroot and was considering going

    you are right, use eb in a chroot env of openwrt etc env is a use case.

    further, but stretch bumped the ISA requirements so I cannot use it

    What CPU is your router? mips r2 is a quite old ISA standard,
    they are published in 2002, why your router didn't support it?

    any longer. Likewise someone on #debian-mips with a Loongson 2f Lemote
    laptop recently complained about stretch removing Longsoon support. So
    maybe a better approach would be to lower the ISA requirements back to
    what was in jessie so folks can use it again in buster?

    yes, Loongson 2f is only support MIPS II/III.
    I have no idea if it is valuable to downgrade mipsel to MIPS II,
    at the same time, Loongson 2f has some other bugs, which will ask for
    gcc/glibc patch, which will slow down the binary on other CPUs.


    --
    bye,
    pabs

    https://wiki.debian.org/PaulWise



    --
    YunQiang Su

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul Wise@21:1/5 to YunQiang Su on Sat Jul 7 16:50:01 2018
    On Sat, Jul 7, 2018 at 10:31 PM, YunQiang Su wrote:

    In fact I don't know anybody is using Debian's mips32eb port.

    I used jessie mips on my router in a chroot and was considering going
    further, but stretch bumped the ISA requirements so I cannot use it
    any longer. Likewise someone on #debian-mips with a Loongson 2f Lemote
    laptop recently complained about stretch removing Longsoon support. So
    maybe a better approach would be to lower the ISA requirements back to
    what was in jessie so folks can use it again in buster?

    --
    bye,
    pabs

    https://wiki.debian.org/PaulWise

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From YunQiang Su@21:1/5 to All on Sat Jul 7 17:30:01 2018
    Paul Wise <pabs@debian.org> 于2018年7月7日周六 下午11:20写道:

    On Sat, 2018-07-07 at 22:54 +0800, YunQiang Su wrote:

    use eb in a chroot env of openwrt etc env is a use case.

    In my case it was the default firmware with help of this:

    https://github.com/mattimustang/optus-sagemcom-fast-3864-hacks

    What CPU is your router? mips r2 is a quite old ISA standard,
    they are published in 2002, why your router didn't support it?

    The router is a (GPL violating) SAGEMCOM F@ST3864V2 with Broadcom SoC BCM963268 and CPU BMIPS4350 V8.0. This is the default router shipped by
    my ISP, I now have two of them and the latest one I recieved new this
    year. There are some other devices out there with the same SoC/CPU too:

    https://wikidevi.com/w/index.php?search=BMIPS4350&title=Special%3ASearch&fulltext=Search
    https://wikidevi.com/w/index.php?search=BCM963268&title=Special%3ASearch&profile=default&fulltext=1

    Since they are quite new, I except they support mips r2.
    Maybe the problem is due to lack of FPU?


    yes, Loongson 2f is only support MIPS II/III.
    I have no idea if it is valuable to downgrade mipsel to MIPS II,
    at the same time, Loongson 2f has some other bugs, which will ask for gcc/glibc patch, which will slow down the binary on other CPUs.

    I guess that is not a good idea then.

    --
    bye,
    pabs

    https://wiki.debian.org/PaulWise



    --
    YunQiang Su

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul Wise@21:1/5 to YunQiang Su on Sat Jul 7 17:30:01 2018
    On Sat, 2018-07-07 at 22:54 +0800, YunQiang Su wrote:

    use eb in a chroot env of openwrt etc env is a use case.

    In my case it was the default firmware with help of this:

    https://github.com/mattimustang/optus-sagemcom-fast-3864-hacks

    What CPU is your router? mips r2 is a quite old ISA standard,
    they are published in 2002, why your router didn't support it?

    The router is a (GPL violating) SAGEMCOM F@ST3864V2 with Broadcom SoC
    BCM963268 and CPU BMIPS4350 V8.0. This is the default router shipped by
    my ISP, I now have two of them and the latest one I recieved new this
    year. There are some other devices out there with the same SoC/CPU too:

    https://wikidevi.com/w/index.php?search=BMIPS4350&title=Special%3ASearch&fulltext=Search
    https://wikidevi.com/w/index.php?search=BCM963268&title=Special%3ASearch&profile=default&fulltext=1

    yes, Loongson 2f is only support MIPS II/III.
    I have no idea if it is valuable to downgrade mipsel to MIPS II,
    at the same time, Loongson 2f has some other bugs, which will ask for gcc/glibc patch, which will slow down the binary on other CPUs.

    I guess that is not a good idea then.

    --
    bye,
    pabs

    https://wiki.debian.org/PaulWise

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAltA2jQACgkQMRa6Xp/6 aaO5VxAAmmUSlA0iLWTL6PyzJMbsYUq/F6fMfl6YkzM6gLzC2kuTqEEV9mRWDWWF saYoDlaJ0M8yir3tCeeEQETbPW1ro32EY4dfCl1bd3qlbdf0tDAXZcDUjMjnGmTE b8esNd+4W3YW5U7xp9LLQf3+c2EOKCJ1nKhWskqw9SNwp6HbdEKMVS8L9Oa0TnRx tEKYE2pPsmCCG/qaYK8dp+BdJKFK6OLs5VjWQoRrEzSftbsVkUb1ty27N/k8bKFI EV/H7gHCjOlflaX46RBubqcFm7m43CKGUufR2koHH2+Ok4iO7OFezjCKuKi7RLJd UPuZ6hF13uSDdvGfC/48jWrkHB4SUhfbWgPOZCyYidkpIV8h275FYPeOUmxsTVTu rKy+JgxTf/zhY/IgH48m3zdxJIeAQ1m6kxr+47H6WUM0zfTm5aITz+HQg5GSPofT vM0MJ2PqIyfaYerVXxITbo9EL8kv1zMP9UO+C+N9OmkbIb/MJT94A7exnlzlBRXL DRJgG4CltDixoi7d2fQBOeA8nG5U5pZa6K2GlsLQ/mjTi20/ZUF5U2PHj+/jsYMG 9Pxa8JHpMguTgtlEnkPCWpLisPjMB2BQDhWxTSTzj2S9tZn/WeYVztDB2ctECTY7 0RHNOM6QhOdLIliwdMW5dlq6sp6XrB0moXe0Il3rCy9aGkLT3/8=
    =e2fP
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From YunQiang Su@21:1/5 to All on Sat Jul 7 18:00:01 2018
    Paul Wise <pabs@debian.org> 于2018年7月7日周六 下午11:42写道:

    On Sat, 2018-07-07 at 23:29 +0800, YunQiang Su wrote:

    Since they are quite new, I expect they support mips r2.

    I was not able to find any info about that.

    Maybe the problem is due to lack of FPU?

    Possibly, did Debian jessie have FPU disabled and stretch has FPU enabled?

    Here is /proc/cpuinfo from the device:

    system type : F@ST3864V2
    processor : 0
    cpu model : Broadcom BMIPS4350 V8.0
    BogoMIPS : 397.31
    wait instruction : yes
    microsecond timers : yes
    tlb_entries : 32
    extra interrupt vector : no
    hardware watchpoint : no
    ASEs implemented :
    shadow register sets : 1
    kscratch registers : 0
    core : 0
    VCED exceptions : not available
    VCEI exceptions : not available

    processor : 1
    cpu model : Broadcom BMIPS4350 V8.0
    BogoMIPS : 403.45
    wait instruction : yes
    microsecond timers : yes
    tlb_entries : 32
    extra interrupt vector : no
    hardware watchpoint : no
    ASEs implemented :
    shadow register sets : 1
    kscratch registers : 0
    core : 0
    VCED exceptions : not available
    VCEI exceptions : not available


    Ohh, it doesn't support r2 really. OMG.

    --
    bye,
    pabs

    https://wiki.debian.org/PaulWise



    --
    YunQiang Su

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul Wise@21:1/5 to YunQiang Su on Sat Jul 7 17:50:01 2018
    On Sat, 2018-07-07 at 23:29 +0800, YunQiang Su wrote:

    Since they are quite new, I expect they support mips r2.

    I was not able to find any info about that.

    Maybe the problem is due to lack of FPU?

    Possibly, did Debian jessie have FPU disabled and stretch has FPU enabled?

    Here is /proc/cpuinfo from the device:

    system type : F@ST3864V2
    processor : 0
    cpu model : Broadcom BMIPS4350 V8.0
    BogoMIPS : 397.31
    wait instruction : yes
    microsecond timers : yes
    tlb_entries : 32
    extra interrupt vector : no
    hardware watchpoint : no
    ASEs implemented :
    shadow register sets : 1
    kscratch registers : 0
    core : 0
    VCED exceptions : not available
    VCEI exceptions : not available

    processor : 1
    cpu model : Broadcom BMIPS4350 V8.0
    BogoMIPS : 403.45
    wait instruction : yes
    microsecond timers : yes
    tlb_entries : 32
    extra interrupt vector : no
    hardware watchpoint : no
    ASEs implemented :
    shadow register sets : 1
    kscratch registers : 0
    core : 0
    VCED exceptions : not available
    VCEI exceptions : not available

    --
    bye,
    pabs

    https://wiki.debian.org/PaulWise

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAltA32YACgkQMRa6Xp/6 aaNk6w//ZZTawVBPe7KGMcMxjg2P7dlynmfwUS9VOjrH8Vync27OAlv0KmxJpkAj qa28kppi0XRGQCOU9e9OCM+Hwqu3KuTFqeF9SRpmWPDr1CilY7qqL1f8QC71k606 sz8q4rnV2VlTI3XMizM9lZQvM6d4IU7qghI9pJvFKplHeD/YDrnCACBdeAloWl06 S16+lw5ryzfeT2jvVPdwDvOPHQm8GjAJCKT9GmkH55JUaulnBwt8AGkhCNSAfsuN RcyGn0gt0K1miGXAsu/HJjgfxmy3Arhk/8xZ7zw8T/no4mdDFBqA4ZpzJ+UVZclo 7DiY4piuobML0reBRBkTi888KPrPr1Ik2eHprLAINnge7t9YAt9bBrIX7DR/4P4Q R/x6BPWTbgqhIH6TUR5Zzb9bDl2c0qcfWXT0ZgfvR9c3V7DMCno8A6X5mF3UIEjS BJlLoQ529URWrbMESPcypNdhOlyH++/FBmYiz0YdtGMOO/lTixqxnurxoZI0sUxQ 4q0lU5Ej2z34zum6TD1nsAIrqmTgETEZnwteLSAAKBnZFy8LOoaNH9vPvj+QY0gL D/d9v+R3glVV83rX4mReCaK9bNSjwSNYgjj2DvaiZL+6cZJE8sHbpKHz0tatzgil ruM5xziwAYLoVijMJyDj0McmIv8KRLcbyT1MjTHOKoRdlXXqzfU=
    =RqRw
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Aron Xu@21:1/5 to pabs@debian.org on Sat Jul 7 18:00:01 2018
    On Sat, Jul 7, 2018 at 11:42 PM Paul Wise <pabs@debian.org> wrote:

    On Sat, 2018-07-07 at 23:29 +0800, YunQiang Su wrote:

    Since they are quite new, I expect they support mips r2.

    I was not able to find any info about that.

    Maybe the problem is due to lack of FPU?

    Possibly, did Debian jessie have FPU disabled and stretch has FPU enabled?

    Here is /proc/cpuinfo from the device:

    system type : F@ST3864V2
    processor : 0
    cpu model : Broadcom BMIPS4350 V8.0
    BogoMIPS : 397.31
    wait instruction : yes
    microsecond timers : yes
    [...]

    It's BCM63168 SoC for xDSL modems, which is standard MIPS32
    architecture and does not have MIPS32r2 support.

    Regards,
    Aron

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adi Kriegisch@21:1/5 to All on Mon Jul 9 10:40:01 2018
    Hi!

    due to lack of enough man power and build machines for 3 mips* port at
    the same time, I think that now it is time for us to have a talk about dropping mips32eb support now.
    [...]
    In fact I don't know anybody is using Debian's mips32eb port.
    If you are using it, please tell us.
    I am using mips32eb a lot on wifi routers (self-compiled kernel with
    rootfs on a usb stick). There are some people here at a community
    wireless network that do use such setups on their rooftops as well.

    Please let me know if there is anything I could do to help avoiding the
    drop.

    best regards,
    Adi Kriegisch

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mathieu Malaterre@21:1/5 to wzssyqa@gmail.com on Mon Jul 9 12:40:01 2018
    On Mon, Jul 9, 2018 at 12:12 PM YunQiang Su <wzssyqa@gmail.com> wrote:

    Adi Kriegisch <adi@cg.tuwien.ac.at> 于2018年7月9日周一 下午4:34写道:

    Hi!

    due to lack of enough man power and build machines for 3 mips* port at the same time, I think that now it is time for us to have a talk about dropping mips32eb support now.
    [...]
    In fact I don't know anybody is using Debian's mips32eb port.
    If you are using it, please tell us.
    I am using mips32eb a lot on wifi routers (self-compiled kernel with
    rootfs on a usb stick). There are some people here at a community
    wireless network that do use such setups on their rooftops as well.


    What is the advantage of eb than el? better performance?
    I guess most of CPUs support both eb and el.

    Please let me know if there is anything I could do to help avoiding the drop.


    We need some more build machines, current we use some ER8s,
    which use NFS as rootfs and they have no FPU.
    So the performance and stability are bad.

    Just for reference why is mips (mips32eb) not build from an mips64el
    machine (with FPU) ? All i386 (AFAIK) packages are build from amd64
    these days (same is true for ppc32 on ppc64).

    We also need some more manpower to fix the FTBFS in future.

    Is this the correct page to look at the FTBFS+mips(32eb):

    https://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=mips&user=debian-mips%40lists.debian.org



    best regards,
    Adi Kriegisch



    --
    YunQiang Su


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From YunQiang Su@21:1/5 to All on Mon Jul 9 12:20:01 2018
    Adi Kriegisch <adi@cg.tuwien.ac.at> 于2018年7月9日周一 下午4:34写道:

    Hi!

    due to lack of enough man power and build machines for 3 mips* port at
    the same time, I think that now it is time for us to have a talk about dropping mips32eb support now.
    [...]
    In fact I don't know anybody is using Debian's mips32eb port.
    If you are using it, please tell us.
    I am using mips32eb a lot on wifi routers (self-compiled kernel with
    rootfs on a usb stick). There are some people here at a community
    wireless network that do use such setups on their rooftops as well.


    What is the advantage of eb than el? better performance?
    I guess most of CPUs support both eb and el.

    Please let me know if there is anything I could do to help avoiding the
    drop.


    We need some more build machines, current we use some ER8s,
    which use NFS as rootfs and they have no FPU.
    So the performance and stability are bad.

    We also need some more manpower to fix the FTBFS in future.

    best regards,
    Adi Kriegisch



    --
    YunQiang Su

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From YunQiang Su@21:1/5 to All on Mon Jul 9 12:50:02 2018
    Mathieu Malaterre <malat@debian.org> 于2018年7月9日周一 下午6:31写道:

    On Mon, Jul 9, 2018 at 12:12 PM YunQiang Su <wzssyqa@gmail.com> wrote:

    Adi Kriegisch <adi@cg.tuwien.ac.at> 于2018年7月9日周一 下午4:34写道:

    Hi!

    due to lack of enough man power and build machines for 3 mips* port at the same time, I think that now it is time for us to have a talk about dropping mips32eb support now.
    [...]
    In fact I don't know anybody is using Debian's mips32eb port.
    If you are using it, please tell us.
    I am using mips32eb a lot on wifi routers (self-compiled kernel with rootfs on a usb stick). There are some people here at a community wireless network that do use such setups on their rooftops as well.


    What is the advantage of eb than el? better performance?
    I guess most of CPUs support both eb and el.

    Please let me know if there is anything I could do to help avoiding the drop.


    We need some more build machines, current we use some ER8s,
    which use NFS as rootfs and they have no FPU.
    So the performance and stability are bad.

    Just for reference why is mips (mips32eb) not build from an mips64el
    machine (with FPU) ? All i386 (AFAIK) packages are build from amd64
    these days (same is true for ppc32 on ppc64).

    mipsel packages do build on mips64el machines,
    while mips aka mips32eb cannot.


    We also need some more manpower to fix the FTBFS in future.

    Is this the correct page to look at the FTBFS+mips(32eb):

    https://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=mips&user=debian-mips%40lists.debian.org


    Yes. It is.



    best regards,
    Adi Kriegisch



    --
    YunQiang Su




    --
    YunQiang Su

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adi Kriegisch@21:1/5 to All on Mon Jul 9 13:50:01 2018
    Hi!

    In fact I don't know anybody is using Debian's mips32eb port.
    If you are using it, please tell us.
    I am using mips32eb a lot on wifi routers (self-compiled kernel with
    rootfs on a usb stick). There are some people here at a community
    wireless network that do use such setups on their rooftops as well.

    What is the advantage of eb than el? better performance?
    I guess most of CPUs support both eb and el.
    Actually, up to now I thought, endianess is determined by the CPU and
    cannot be changed easily. I chose my kernel and architecture settings
    based on those of OpenWRT and the CPUs I use are mainly:
    * Ubiquiti RouterStation Pro (Atheros AR7161r2/MIPS 24Kc V7.4)
    * TP-Link WDR4300 (Atheros AR9344r2/MIPS 74Kc V4.12)
    * TP-Link Archer C5 (Atheros QCA9558v1/MIPS 74Kc V5.0)

    Please let me know if there is anything I could do to help avoiding the drop.

    We need some more build machines, current we use some ER8s,
    which use NFS as rootfs and they have no FPU.
    So the performance and stability are bad.
    I could only offer a spare RouterStation Pro which I use for testing and compiling/backporting some software like swconfig or hostapd. At least
    this device seems stable although it is even older/weaker than those ER8s...

    We also need some more manpower to fix the FTBFS in future.
    The issues tagged 'mips' are way out of what I can handle, I am afraid.
    Though, I'll keep watching them and hope that there might appear issues
    I can deal with!

    all the best,
    Adi Kriegisch

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Aron Xu@21:1/5 to brockwittrock@gmail.com on Tue Jul 10 07:40:01 2018
    On Tue, Jul 10, 2018 at 1:21 AM Brock Wittrock <brockwittrock@gmail.com> wrote:

    I'm still actively using it for a couple of different devices.


    Let's avoid cross posting and keep this thread in
    debian-mips@lists.d.o. We'll move to other forum when suitable.

    Regards,
    Aron

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mathieu Malaterre@21:1/5 to wzssyqa@gmail.com on Tue Jul 10 08:30:01 2018
    On Mon, Jul 9, 2018 at 12:47 PM YunQiang Su <wzssyqa@gmail.com> wrote:

    Mathieu Malaterre <malat@debian.org> 于2018年7月9日周一 下午6:31写道:

    On Mon, Jul 9, 2018 at 12:12 PM YunQiang Su <wzssyqa@gmail.com> wrote:

    Adi Kriegisch <adi@cg.tuwien.ac.at> 于2018年7月9日周一 下午4:34写道:

    Hi!

    due to lack of enough man power and build machines for 3 mips* port at
    the same time, I think that now it is time for us to have a talk about
    dropping mips32eb support now.
    [...]
    In fact I don't know anybody is using Debian's mips32eb port.
    If you are using it, please tell us.
    I am using mips32eb a lot on wifi routers (self-compiled kernel with rootfs on a usb stick). There are some people here at a community wireless network that do use such setups on their rooftops as well.


    What is the advantage of eb than el? better performance?
    I guess most of CPUs support both eb and el.

    Please let me know if there is anything I could do to help avoiding the drop.


    We need some more build machines, current we use some ER8s,
    which use NFS as rootfs and they have no FPU.
    So the performance and stability are bad.

    Just for reference why is mips (mips32eb) not build from an mips64el machine (with FPU) ? All i386 (AFAIK) packages are build from amd64
    these days (same is true for ppc32 on ppc64).

    mipsel packages do build on mips64el machines,
    while mips aka mips32eb cannot.

    Sorry to insist, but I thought mips & mipsel in Debian were both
    MIPS32r2. So what makes mips32eb so special for MIPS64r6 ?


    We also need some more manpower to fix the FTBFS in future.

    Is this the correct page to look at the FTBFS+mips(32eb):

    https://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=mips&user=debian-mips%40lists.debian.org


    Yes. It is.



    best regards,
    Adi Kriegisch



    --
    YunQiang Su




    --
    YunQiang Su

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Aron Xu@21:1/5 to malat@debian.org on Tue Jul 10 09:40:01 2018
    On Tue, Jul 10, 2018 at 2:28 PM Mathieu Malaterre <malat@debian.org> wrote:

    On Mon, Jul 9, 2018 at 12:47 PM YunQiang Su <wzssyqa@gmail.com> wrote:

    Mathieu Malaterre <malat@debian.org> 于2018年7月9日周一 下午6:31写道:

    On Mon, Jul 9, 2018 at 12:12 PM YunQiang Su <wzssyqa@gmail.com> wrote:

    Adi Kriegisch <adi@cg.tuwien.ac.at> 于2018年7月9日周一 下午4:34写道:

    Hi!

    due to lack of enough man power and build machines for 3 mips* port at
    the same time, I think that now it is time for us to have a talk about
    dropping mips32eb support now.
    [...]
    In fact I don't know anybody is using Debian's mips32eb port.
    If you are using it, please tell us.
    I am using mips32eb a lot on wifi routers (self-compiled kernel with rootfs on a usb stick). There are some people here at a community wireless network that do use such setups on their rooftops as well.


    What is the advantage of eb than el? better performance?
    I guess most of CPUs support both eb and el.

    Please let me know if there is anything I could do to help avoiding the
    drop.


    We need some more build machines, current we use some ER8s,
    which use NFS as rootfs and they have no FPU.
    So the performance and stability are bad.

    Just for reference why is mips (mips32eb) not build from an mips64el machine (with FPU) ? All i386 (AFAIK) packages are build from amd64
    these days (same is true for ppc32 on ppc64).

    mipsel packages do build on mips64el machines,
    while mips aka mips32eb cannot.

    Sorry to insist, but I thought mips & mipsel in Debian were both
    MIPS32r2. So what makes mips32eb so special for MIPS64r6 ?


    Because mips32eb is big endian, while MIPS hardware does not support
    switching endianess at runtime, if I understand correctly mips64el
    hardware can do native build for mipsel binaries but cannot do the
    same for mips(32eb).

    Regards,
    Aron

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From YunQiang Su@21:1/5 to All on Wed Jul 11 02:10:01 2018
    Mathieu Malaterre <malat@debian.org> 于2018年7月10日周二 下午2:27写道:

    On Mon, Jul 9, 2018 at 12:47 PM YunQiang Su <wzssyqa@gmail.com> wrote:

    Mathieu Malaterre <malat@debian.org> 于2018年7月9日周一 下午6:31写道:

    On Mon, Jul 9, 2018 at 12:12 PM YunQiang Su <wzssyqa@gmail.com> wrote:

    Adi Kriegisch <adi@cg.tuwien.ac.at> 于2018年7月9日周一 下午4:34写道:

    Hi!

    due to lack of enough man power and build machines for 3 mips* port at
    the same time, I think that now it is time for us to have a talk about
    dropping mips32eb support now.
    [...]
    In fact I don't know anybody is using Debian's mips32eb port.
    If you are using it, please tell us.
    I am using mips32eb a lot on wifi routers (self-compiled kernel with rootfs on a usb stick). There are some people here at a community wireless network that do use such setups on their rooftops as well.


    What is the advantage of eb than el? better performance?
    I guess most of CPUs support both eb and el.

    Please let me know if there is anything I could do to help avoiding the
    drop.


    We need some more build machines, current we use some ER8s,
    which use NFS as rootfs and they have no FPU.
    So the performance and stability are bad.

    Just for reference why is mips (mips32eb) not build from an mips64el machine (with FPU) ? All i386 (AFAIK) packages are build from amd64
    these days (same is true for ppc32 on ppc64).

    mipsel packages do build on mips64el machines,
    while mips aka mips32eb cannot.

    Sorry to insist, but I thought mips & mipsel in Debian were both
    MIPS32r2. So what makes mips32eb so special for MIPS64r6 ?

    this is about big endian and little endian, not about r2 vs r6.



    We also need some more manpower to fix the FTBFS in future.

    Is this the correct page to look at the FTBFS+mips(32eb):

    https://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=mips&user=debian-mips%40lists.debian.org


    Yes. It is.



    best regards,
    Adi Kriegisch



    --
    YunQiang Su




    --
    YunQiang Su



    --
    YunQiang Su

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From J.P.Malhado@21:1/5 to YunQiang Su on Sat Jul 21 21:20:01 2018
    On Mon, 9 Jul 2018 18:13:43 +0800, YunQiang Su wrote:
    We need some more build machines, current we use some ER8s,
    which use NFS as rootfs and they have no FPU.
    So the performance and stability are bad.

    I'm commenting here from a position of ignorance:
    Would SGI hardware make good build machines for the architecture? I'm asking because I have a 3 SGI Octanes I could give away.
    Last I checked, stretch kernels did not work on these machines, but I would like
    to be wrong.
    Is the problem with the linux port, or is it related with Debian's compilation options?
    According to this information from Gentoo https://wiki.gentoo.org/wiki/MIPS/Hardware_Requirements#IP30:_Octane
    it should be semi-functional, but that information might be out of date.

    Best regards,
    João

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Matt Turner@21:1/5 to malhado@imperial.ac.uk on Sun Aug 12 07:50:01 2018
    On Sat, Jul 21, 2018 at 12:18 PM J.P.Malhado <malhado@imperial.ac.uk> wrote:

    On Mon, 9 Jul 2018 18:13:43 +0800, YunQiang Su wrote:
    We need some more build machines, current we use some ER8s,
    which use NFS as rootfs and they have no FPU.
    So the performance and stability are bad.

    I'm commenting here from a position of ignorance:
    Would SGI hardware make good build machines for the architecture? I'm asking because I have a 3 SGI Octanes I could give away.

    Doubtful. Octanes use hundreds of watts and aren't very fast compared
    with modern systems. They are indeed big endian, however.

    Debian used to have some Broadcom SWARM (BCM91250A) systems. They're
    bootable as big or little endian (controllable with a jumper on the motherboard). I have some that I attempt to use for Gentoo, but
    they're unstable and their kernel support seems to be totally
    unmaintained.

    Aurelien, do you know what happened to those systems? I don't see them
    listed here: https://wiki.debian.org/MIPSPort#Build_daemons_.26_porter_boxes

    (Gentoo would love your hand-me-downs if you're no longer using them :)

    Last I checked, stretch kernels did not work on these machines, but I would like
    to be wrong.
    Is the problem with the linux port, or is it related with Debian's compilation
    options?

    Lack of upstream kernel support.

    According to this information from Gentoo https://wiki.gentoo.org/wiki/MIPS/Hardware_Requirements#IP30:_Octane
    it should be semi-functional, but that information might be out of date.

    The maintainer of T2 Linux (René, Cc'd) has a YouTube channel in which
    he demonstrated an Octane running a modern (4.8?) kernel he had
    patched. I have not seen evidence of those patches going upstream
    though. As far as I know his work is in a significantly better state
    than that of Joshua's (from Gentoo).

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?iso-8859-1?Q?Ren=E9_Rebe?=@21:1/5 to Matt Turner on Tue Aug 14 12:10:02 2018
    Hello everyone,

    On 12 Aug 2018, at 07:46, Matt Turner <mattst88@gmail.com> wrote:

    On Sat, Jul 21, 2018 at 12:18 PM J.P.Malhado <malhado@imperial.ac.uk> wrote:

    On Mon, 9 Jul 2018 18:13:43 +0800, YunQiang Su wrote:
    We need some more build machines, current we use some ER8s,
    which use NFS as rootfs and they have no FPU.
    So the performance and stability are bad.

    I'm commenting here from a position of ignorance:
    Would SGI hardware make good build machines for the architecture? I'm asking >> because I have a 3 SGI Octanes I could give away.

    Doubtful. Octanes use hundreds of watts and aren't very fast compared
    with modern systems. They are indeed big endian, however.

    I would be interested in one faster than 2x250MHz ;-)

    According to this information from Gentoo
    https://wiki.gentoo.org/wiki/MIPS/Hardware_Requirements#IP30:_Octane
    it should be semi-functional, but that information might be out of date.

    The maintainer of T2 Linux (Ren, Cc'd) has a YouTube channel in which
    he demonstrated an Octane running a modern (4.8?) kernel he had
    patched. I have not seen evidence of those patches going upstream
    though. As far as I know his work is in a significantly better state
    than that of Joshua's (from Gentoo).

    I started to contact Ralf, and intend to try in autumn over the winter, to finally
    get the ageing Sgi Octane port bits upstream.

    https://www.linux-mips.org/wiki/IP30
    https://t2sde.org/architectures/mips64/

    Greetings,
    Ren

    --
    ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin
    DE Legal: Amtsgericht Berlin (Charlottenburg) HRB 105123B, Tax-ID#: DE251602478
    Managing Director: Ren Rebe
    http://exactcode.com | http://exactscan.com | http://ocrkit.com | http://t2-project.org | http://rene.rebe.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Aurelien Jarno@21:1/5 to Matt Turner on Wed Aug 15 00:00:01 2018
    Hi Matt,

    On 2018-08-11 22:46, Matt Turner wrote:
    On Sat, Jul 21, 2018 at 12:18 PM J.P.Malhado <malhado@imperial.ac.uk> wrote:

    On Mon, 9 Jul 2018 18:13:43 +0800, YunQiang Su wrote:
    We need some more build machines, current we use some ER8s,
    which use NFS as rootfs and they have no FPU.
    So the performance and stability are bad.

    I'm commenting here from a position of ignorance:
    Would SGI hardware make good build machines for the architecture? I'm asking
    because I have a 3 SGI Octanes I could give away.

    Doubtful. Octanes use hundreds of watts and aren't very fast compared
    with modern systems. They are indeed big endian, however.

    Debian used to have some Broadcom SWARM (BCM91250A) systems. They're
    bootable as big or little endian (controllable with a jumper on the motherboard). I have some that I attempt to use for Gentoo, but
    they're unstable and their kernel support seems to be totally
    unmaintained.

    Aurelien, do you know what happened to those systems? I don't see them
    listed here: https://wiki.debian.org/MIPSPort#Build_daemons_.26_porter_boxes

    (Gentoo would love your hand-me-downs if you're no longer using them :)

    Debian indeed used to have some of those as build daemons, but they all
    died one by one. I don't remember the exact details for all of them, but
    I remember I spent time during Debconf in Portland to fix one, which
    started to crash before the end of the CFE boot.

    I remember the original CPU fan was of quite bad quality and that they
    were also quite picky about memory modules and IDE disks.

    Aurelien

    --
    Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://www.aurel32.net

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)