Steve Foster wrote:
> 
> Soren,
> 
> Forgive my ignorance on this matter, but what is actually required with the
> HPC init.? is it just a case of looking at specific memory address's or am i
> over simplifying matters here?

I'll allow myself to but in here, since my experience with the Indigo 4k
may be of relevance.
It depends on the HPC chip version in your Challenge S.
I believe there are 3 versions of this beast (HPC). Version 1 (in Indigo
3k), version 1.5 (Indigo R4000) and HPC 3 (Indy, Indigo 2).
If your Challenge has an HPC 1.5, then there are some not insubstantial
differences in memory addresses. The DMA data structure is also
_slightly_ different. Nothing to get worked up about, but not a simple
block displacement of memory addresses either.

Hope that helps

Gerald

> 
> Steve
> 
> PS Please note that my new email address is spindle@area404.co.uk
> 
> -----Original Message-----
> From: Soren S. Jorvang [mailto:soren@wheel.dk]
> Sent: 23 January 2002 04:43
> To: Steve Foster
> Cc: port-sgimips@netbsd.org
> Subject: Re: ThunderLan network Card
> 
> On Tue, Jan 22, 2002 at 09:59:46PM -0000, Steve Foster wrote:
> > Anyhow, has anyone done any work on getting the daughter board for the
> > Challenge S working? Or is it currently on hiatus?
> 
> The ethernet interface is the same Seeq 80c03 as is used on the
> motherboard and it should require no more than some basic HPC
> initialization to work.
> 
> The SCSI interfaces would be rather harder, as the 33c95 seems
> impossible to acquire actual documentation for, so unless someone
> goes to the trouble of reverse-engineering some existing driver
> for it, don't expect it to happen..
> 
> --
> Soren