Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 13 Jun 2018 17:24:13 -0600
From:      Warner Losh <imp@bsdimp.com>
To:        Mori Hiroki <yamori813@yahoo.co.jp>
Cc:        "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>, "freebsd-arch@freebsd.org" <arch@freebsd.org>
Subject:   Re: Armeb removal before 12
Message-ID:  <CANCZdfpbNfajJs82tx1CgyNCN1QNAdZwd=nut0J_Gq8ZR2xz4w@mail.gmail.com>
In-Reply-To: <861063.32056.qm@web101713.mail.ssk.yahoo.co.jp>
References:  <CANCZdfoVYJbJEM-PhKL3Y_edp=X6Smb1uYHrEiYSm%2BZXsTmzdw@mail.gmail.com> <540973.43848.qm@web101701.mail.ssk.yahoo.co.jp> <CANCZdfr5yL7qbgGzJxRAQSq=CGC35L8rwR0knEQf6UpSNPUCOw@mail.gmail.com> <861063.32056.qm@web101713.mail.ssk.yahoo.co.jp>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 13, 2018 at 5:10 PM, Mori Hiroki <yamori813@yahoo.co.jp> wrote:

> Hi
>
> ----- Original Message -----
> >From: Warner Losh <imp@bsdimp.com>
> >To: Mori Hiroki <yamori813@yahoo.co.jp>
> >Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>; "
> freebsd-arch@freebsd.org" <arch@freebsd.org>
> >Date: 2018/6/14, Thu 07:57
> >Subject: Re: Armeb removal before 12
> >
> >
> >
> >
> >
> >
> >On Wed, Jun 13, 2018 at 4:25 PM, Mori Hiroki <yamori813@yahoo.co.jp>
> wrote:
> >
> >Hi.
> >>
> >>
> >>----- Original Message -----
> >>> From: Warner Losh <imp@bsdimp.com>
> >>> To: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>; "
> freebsd-arch@freebsd.org" <arch@freebsd.org>
> >>> Cc:
> >>> Date: 2018/6/14, Thu 01:55
> >>> Subject: Armeb removal before 12
> >>>
> >>> I'd like to remove armeb before 12.0.
> >>>
> >>> It's poorly supported today.
> >>>
> >>> Nobody has tested the concurrency kit changes on it. And ck is now
> >>> mandatory. We don't even know if it works or not.
> >>>
> >>> Last time we asked, it took quite a while to find users.
> >>>
> >>> It maxes out at 256MB of RAM. This is barely large enough for FreeBSD
> to
> >>> run in.
> >>
> >>sys/arm/ralink target is only 16M of RAM. I use bridge on this target
> >>work fine.
> >>
> >
> >
> >Even with current? It seems to have grown a lot. Even FreeBSD 11 on my
> atmel boards, the 32MB ones can't really do much of anything (though a
> custom /etc/rc.d might be usable). The 64MB ones I have troubles logging
> into without disabling a ton of stuff. And FreeBSD-current is even larger.
> >
> >
> >Are you using a custom rc.d in this setup?
>
>
> Of course CURRENT.
>
> https://gist.github.com/yamori813/88224f1c96c9c592fb611b12a15e4ab5
>
>
> I use custom rc.d by ZRouter build system.
>

Cool! You have 10MB available. what all runs in that little space? I didn't
see too much starting up

Warner


> Thanks
>
> Hiroki Mori
>
> >
> >I have FWIXP422BB target(Planex BRC-14VG) with 32M of RAM. I never build
> >>FreeBSD for this target.
> >>
> >>I want build for FWIXP422BB but clang cross build is very slow. It take
> >>7 hour on my machine.
> >
> >
> >I'm sorry to hear that. Even on my fast machines, it takes long time.
> >
> >
> >Warner
> >
> >
> >
> >
> >>>
> >>> The hardware was last made almost a decade ago.
> >>>
> >>> It uses non-standard non-mainstream boot loaders (boot technology has
> moved
> >>> on from redboot).
> >>>
> >>> The cost of doing API sweeps, make universe runs, etc exceeds the
> benefit
> >>> to the project.
> >>>
> >>> So, given all these factors, it sounds like a good candidate for
> retirement.
> >>>
> >>> Therefore, I'd like to remove it on July 15th.
> >>>
> >>> Comments? (please keep  them on topic to this specific thing: there's
> other
> >>> things that may also be past their freshness date, we'll discuss those
> in a
> >>> separate thread).
> >>>
> >>> Warner
> >>
> >>> ______________________________ _________________
> >>> freebsd-arm@freebsd.org mailing list
> >>> https://lists.freebsd.org/ mailman/listinfo/freebsd-arm
> >>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@ freebsd.org
> "
> >>>
> >>
> >
> >
> >
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpbNfajJs82tx1CgyNCN1QNAdZwd=nut0J_Gq8ZR2xz4w>