Re: Indigo R3000, Indigo R4000 and Indy R5000

[Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>]

Hi,

> On 09/01/2018 05:18 PM, Izumi Tsutsui wrote:
> > Today I had a meeting with Etomi-san and reviewed his patches in PRs.
> > At least all kernel changes (PR 53378, 53518, 53519, 53520, 53521, 53522)
> > are okay for me so I'll commit them in a few days.

I've committed fixes for the following PRs:

PR/53378: Unable to Load RAMDISK kernel newer than NetBSD 6.1.5 on Sgi Indy.
 http://mail-index.netbsd.org/source-changes/2018/09/02/msg098775.html

PR/53518: netbsd-INSTALL32_IP2x.ecoff is broken since NetBSD-4.0.1.
 http://mail-index.netbsd.org/source-changes/2018/09/02/msg098784.html

PR/53519: aoutboot is broken since old NetBSD release.
 http://mail-index.netbsd.org/source-changes/2018/09/02/msg098778.html

PR/53521: Failed to build disable DDB kernel on sgimips.
 http://mail-index.netbsd.org/source-changes/2018/09/02/msg098776.html

PR/53522: wdsc WD33C93 SCSI chip driver is not configured on SGI HPC1.5
          (Indigo R3000 Indigo R4000) machine
 http://mail-index.netbsd.org/source-changes/2018/09/02/msg098783.html

I'll check further for bootloader changes (PR/53539) and
PR/53520 (for delay(9)).

Notes for PR/53520:
 NetBSD/sgimips uses the ci_divisor_delay value for the 4.4BSD derived
 dumb delay loop. However ci_devisor_delay is designed for mips3_delay()
 in sys/arch/mips/mips/mips3_clock.c that uses MIPS3's internal CPU counter,
 i.e. "a number of CPU clock count per microsecond."
 (note ci_cycles_per_hz is also for common mips3_clockintr() in
  sys/arch/mips/mips/mips3_clockintr.c)

 For sgimips delay implementation (traditional 4.4BSD derived delay loop),
 the "cpuspeed" value (that represents "instructions per microsecond")
 should be used instead, as pmax and newsmips do.

 Anyway the cpuspeed value is not so precise as noted in
 sys/arch/mips/mips/mips_mcclock.c
  https://nxr.netbsd.org/xref/src/sys/arch/mips/mips/mips_mcclock.c?r=1.19#198
 so current ci_divisor_delay value is still acceptable, I think.

> @Izumi:
> Cool, that you were around. I'm sadly too far away for a solder job. :-)

I'm happy I can help development for the rare machines :-)

> @Naruaki, Izumi:
> BTW, I hope I use your first names and not your family names when 
> addressing both of you or let's say I hope I use the preferred way you'd 
> like to be addressed. Please correct me if not.

No problem, Naruaki and Izumi are first (given) names.

Thanks,

---
Izumi Tsutsui