Re: ELC access to hifive unleashed boards
On Thu, Mar 15, 2018 at 11:15 PM, Bdale Garbee <bdale@gag.com> wrote:
> "Manuel A. Fernandez Montecelo" <manuel.montezelo@gmail.com> writes:
>
>> In summary: when feasible, and with profiles that make sense, is a
>> good tradeoff to spend some time to add them to the archive, IMO.
>
> Thanks for the thoughts. Fair enough, just don't let yourself get so
> bogged down "doing things the better way" that progress grinds to a
> halt. Been there, done that, too. /o\
:)
it's a fairly unique situation, this one, where the ISA could be
changed last-minute (even now), forcing everyone to throw away all and
any manually-carried out work up until that point. so that is why,
having been bitten once already, they're doing it the sensible
(automated / scriptable) way, bdale.
previous recent efforts in the past 10 years - armhf and aarch64 -
the architecture / ISA was completely finalised so it was "fine" to do
the work manually: it would not be "wasted".
also bear in mind at some point in the future there will be a RV128
architecture, so any manual work would *again* need to be duplicated
there. likewise if an RV32 system becomes extremely prevalent
(mass-volume) it may be worthwhile considering creating an RV32 port
despite the 4GB limit... same thing again. the only difference being,
at that point it would be a fairly safe bet that the ISA would be
stable by then (whewwww).
l.
Reply to: