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

next in thread | previous in thread | raw e-mail | index | archive | help
Hi=0A=0A----- Original Message -----=0A>From: Warner Losh <imp@bsdimp.com>=
=0A>To: Mori Hiroki <yamori813@yahoo.co.jp> =0A>Cc: "freebsd-arm@freebsd.or=
g" <freebsd-arm@freebsd.org>; "freebsd-arch@freebsd.org" <arch@freebsd.org>=
=0A>Date: 2018/6/14, Thu 07:57=0A>Subject: Re: Armeb removal before 12=0A> =
=0A>=0A>=0A>=0A>=0A>=0A>On Wed, Jun 13, 2018 at 4:25 PM, Mori Hiroki <yamor=
i813@yahoo.co.jp> wrote:=0A>=0A>Hi.=0A>>=0A>>=0A>>----- Original Message --=
---=0A>>> From: Warner Losh <imp@bsdimp.com>=0A>>> To: "freebsd-arm@freebsd=
.org" <freebsd-arm@freebsd.org>; "freebsd-arch@freebsd.org" <arch@freebsd.o=
rg>=0A>>> Cc: =0A>>> Date: 2018/6/14, Thu 01:55=0A>>> Subject: Armeb remova=
l before 12=0A>>> =0A>>> I'd like to remove armeb before 12.0.=0A>>> =0A>>>=
 It's poorly supported today.=0A>>> =0A>>> Nobody has tested the concurrenc=
y kit changes on it. And ck is now=0A>>> mandatory. We don't even know if i=
t works or not.=0A>>> =0A>>> Last time we asked, it took quite a while to f=
ind users.=0A>>> =0A>>> It maxes out at 256MB of RAM. This is barely large =
enough for FreeBSD to=0A>>> run in.=0A>>=0A>>sys/arm/ralink target is only =
16M of RAM. I use bridge on this target=0A>>work fine.=0A>>=0A>=0A>=0A>Even=
 with current? It seems to have grown a lot. Even FreeBSD 11 on my atmel bo=
ards, 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 d=
isabling a ton of stuff. And FreeBSD-current is even larger.=0A>=0A>=0A>Are=
 you using a custom rc.d in this setup?=0A=0A=0AOf course CURRENT.=0A=0Ahtt=
ps://gist.github.com/yamori813/88224f1c96c9c592fb611b12a15e4ab5=0A=0A=0AI u=
se custom rc.d by ZRouter build system.=0A=0AThanks=0A=0AHiroki Mori=0A=0A>=
=A0=0A>I have FWIXP422BB target(Planex BRC-14VG) with 32M of RAM. I never b=
uild=0A>>FreeBSD for this=A0target.=0A>>=0A>>I want build for=A0FWIXP422BB =
but clang cross build is very slow. It take=0A>>7 hour on my machine.=0A>=
=0A>=0A>I'm sorry to hear that. Even on my fast machines, it takes long tim=
e.=0A>=0A>=0A>Warner=0A>=0A>=0A>=A0=0A>=0A>>> =0A>>> The hardware was last =
made almost a decade ago.=0A>>> =0A>>> It uses non-standard non-mainstream =
boot loaders (boot technology has moved=0A>>> on from redboot).=0A>>> =0A>>=
> The cost of doing API sweeps, make universe runs, etc exceeds the benefit=
=0A>>> to the project.=0A>>> =0A>>> So, given all these factors, it sounds =
like a good candidate for retirement.=0A>>> =0A>>> Therefore, I'd like to r=
emove it on July 15th.=0A>>> =0A>>> Comments? (please keep=A0 them on topic=
 to this specific thing: there's other=0A>>> things that may also be past t=
heir freshness date, we'll discuss those in a=0A>>> separate thread).=0A>>>=
 =0A>>> Warner=0A>>=0A>>> ______________________________ _________________=
=0A>>> freebsd-arm@freebsd.org mailing list=0A>>> https://lists.freebsd.org=
/ mailman/listinfo/freebsd-arm=0A>>> To unsubscribe, send any mail to "free=
bsd-arm-unsubscribe@ freebsd.org"=0A>>> =0A>>=0A>=0A>=0A>



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