linux-origin
[Top] [All Lists]

Re: IP35 support

To: kanoj@xxxxxxxxxxxxxxxxxxx (Kanoj Sarcar)
Subject: Re: IP35 support
From: sprasad@xxxxxxxxxxxxxxxxxxxx (Srinivasa Prasad Thirumalachar)
Date: Thu, 27 Apr 2000 09:10:11 -0700 (PDT)
Cc: linux-origin@xxxxxxxxxxx
In-reply-to: <200004271217.FAA24706@xxxxxxxxxxxxxxxxxxx> from "Kanoj Sarcar" at Apr 27, 2000 05:17:17 AM
Sender: owner-linux-origin@xxxxxxxxxxx
According to Kanoj Sarcar ...
> 
> What is the story on the SN1/IP35 support in the  oss tree? I saw some
> checkins go in for that, then a set of reverse checkins to pull that out.

There were some legal issues to be resolved before the bedrock (IP35)
features were made public. Like the SN1 MIPS product should be released
first etc.

At this point, if it is possible it should be removed from oss.

> 
> Anyway, there is still a lot of IP35 hooks lying around in source files
> (and makefiles).
> 
> > gid CONFIG_SGI_IP35
> include/asm-mips64/sn/addrs.h:24:#elif defined(CONFIG_SGI_IP35)
> include/asm-mips64/sn/agent.h:21:#elif defined(CONFIG_SGI_IP35)
> include/asm-mips64/sn/agent.h:23:#endif /* !CONFIG_SGI_IP27 && 
> !CONFIG_SGI_IP35 */
> include/asm-mips64/sn/klconfig.h:54:#elif defined(CONFIG_SGI_IP35)
> include/asm-mips64/sn/klconfig.h:65:#endif  /* !CONFIG_SGI_IP27 && 
> !CONFIG_SGI_IP35 */
> include/asm-mips64/sn/kldir.h:239:#elif defined(CONFIG_SGI_IP35)
> 
> If we are not planning to do the IP35 work right now, maybe we should
> just pull all these out too?

Work can proceed internally in a ptools tree, but they should not
go out on OSS.


Thanks
srinivasa

> 
> Kanoj
> 


<Prev in Thread] Current Thread [Next in Thread>