Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 7 Nov 2019 18:50:54 +0900 (JST)
From:      Mori Hiroki <yamori813@yahoo.co.jp>
To:        Warner Losh <imp@bsdimp.com>
Cc:        "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>,  "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
Subject:   Re: firm date: armv5 support removal scheduled for 2019-12-31
Message-ID:  <184281310.1917624.1573120254286.JavaMail.yahoo@mail.yahoo.co.jp>
In-Reply-To: <CANCZdfquD0Fsbz5GkWOj1WMx=m8W6ZA_iskhev_pueGo9iN-GA@mail.gmail.com>
References:  <CANCZdfoYJ342=Ej_Ha39JMHwZhaeyPn2YfW9mzYR%2BGss58N6nA@mail.gmail.com> <1818196815.3441463.1570703722086.JavaMail.yahoo@jws700103.mail.ssk.yahoo.co.jp> <CANCZdfquD0Fsbz5GkWOj1WMx=m8W6ZA_iskhev_pueGo9iN-GA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi

My old hardware try have two reason.

One is my first BSD is LUNA68K that is 68030 with 8M memory at 1988.=C2=A0
Current my target have more memory.

Second is I think more=C2=A0material world make atomic=C2=A0accident at 3.1=
1.
I want less=C2=A0material world.

Also I try to support 1136J-S r1p5. I get single user on this. But still pr=
oblem.

I seem many commit is good. But a few commit make problem.

Finaly UNIX started on 32 bit architecture. I hope we remain 32 bit support=
.

Regards

Hiroki Mori


----- Original Message -----
>From: Warner Losh <imp@bsdimp.com>
>To: Mori Hiroki <yamori813@yahoo.co.jp>=20
>Cc: "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>; "freebsd-arm@fr=
eebsd.org" <freebsd-arm@freebsd.org>
>Date: 2019/10/23, Wed 00:07
>Subject: Re: firm date: armv5 support removal scheduled for 2019-12-31
>=20
>
>
>
>
>On Thu, Oct 10, 2019 at 4:35 AM Mori Hiroki <yamori813@yahoo.co.jp> wrote:
>
>Hi
>>
>>I have very angry. Because of this.
>>
>>One is Maverl soc is not right performance on FreeBSD now.
>>
>>Maverl FreeBSD is 10-30 times slow from Linux.
>>
>>I think armv5t support is not complete on FreeBSD.
>>
>>You say armv5t pmap have bug. But my RT1310(armv5t) work well half of yea=
r.
>>
>>I try ldd on armv5t one month ago. That is support for armv4 because of
>>
>>that don't know armv4t instruction by default.
>>
>
>
>Hi Mori-san,
>
>
>I get your love of the old hardware. However, we can't support the full ra=
nge of old hardware at this time. We don't have enough people actively work=
ing on it. We have dozens of people complaining that they can't install on =
old hardware that we used to support because things have decayed. I think i=
t's really awesome you've gotten the RT1310 working well. I've never been a=
ble to get mine going, despite spending several days on it over the last ye=
ar or two.=C2=A0 I've been unable to get my *Plug boards working well. They=
 may work fine to boot, but will often panic if I have to fsck because that=
 device doesn't support unaligned I/O.
>
>
>We have trouble enough with the more modern stuff... Trying to also suppor=
t this really old stuff just drains resources from the project.
>
>
>Warner
>=C2=A0
>Hiroki Mori
>>
>>
>>----- Original Message -----
>>> From: Warner Losh <imp@bsdimp.com>
>>> To: "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>; "freebsd-arm=
@freebsd.org" <freebsd-arm@freebsd.org>
>>> Cc:=20
>>> Date: 2019/10/10, Thu 06:40
>>> Subject: firm date: armv5 support removal scheduled for 2019-12-31
>>>=20
>>>G reetings,
>>>=20
>>> There's been much talk of removing armv5 support from FreeBSD in FreeBS=
D
>>> 13. This talk has been ongoing since before 12 was branched among the k=
ey
>>> arm developers. The compromise for the FreeBSD 12 was to have one final
>>> FreeBSD armv5 release for a few straggling users that needed (or think =
they
>>> needed) this release and it would be removed before FreeBSD 13.
>>>=20
>>> The reason to remove this is due to the increased burden armv5 has
>>> presented on the system. We have a separate pmap for v5 which has known=
 or
>>> suspected bugs relating to unaligned I/O. No developers have the armv5
>>> boards in service anymore. They have ceased being relevant to FreeBSD's
>>> success with the plethera of armv7 boards that are on the market. No ne=
w
>>> armv5 boards have been made in a long time. The FreeBSD project hasn't
>>> produce armv5 binaries for 12.x at all (the binaries produced earlier c=
ould
>>> not have possibly booted, though the userland binaries worked if you co=
uld
>>> otherwise install the system). Finally, llvm's lld doesn't support=20
>>> armv5.
>>> It would ease integration if we didn't have to worry about a fallback f=
or
>>> armv5. It would be one fewer dependency on the old binutils toolchain i=
n
>>> the tree.
>>>=20
>>> So, taking all these things together, the time has come to schedule rem=
oval
>>> of armv5 support from FreeBSD. The end of the year seems like a good da=
te
>>> to select for planning this removal, getting whatever notices should be=
 put
>>> into place and warning people about the next release in the most formal=
 way
>>> possible (more informal warnings have been going on for over a year,
>>> starting with armv4 support removal in 12).
>>>=20
>>> I'm posting this now to gather feedback and, if necessary, create a
>>> checklist of things to do before removal.
>>>=20
>>> 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"
>>>=20
>>
>>
>
>




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