HyperSPARC users unite! ;-)

"Ingo T. Storm" <[email protected]>
Newsgroups gmane.linux.aurora.devel
Message-ID <014a01c31ae3$1c6930a0$022ca8c0@OPTIMUS>
To all the folks trying to get 2.4 working on HyperSPARCS: There was a mail
on sparclinux that suggests someone else is working on 2.5/HyperSPARC.

Maybe you should join forces.

Cheers,
Ingo

-----

From: "Keith M Wesolowski" <[email protected]>
To: "Pete Zaitcev" <[email protected]>
Cc: <[email protected]>
Sent: Tuesday, May 13, 2003 1:51 AM
Subject: Re: Implement sun4m non-xcall IPIs


> On Mon, May 12, 2003 at 07:35:06PM -0400, Pete Zaitcev wrote:
>
> > Interesting, but I have no opinion. I'll just take it and
> > deal with the fallout later. I assume that you did not have
> > a chance to test it on SuperSPARC, or did you?
>
> Yes, I tested 2xSM71 and 4xHS90.
>
> > Also, why are you calling them "non-xcall"? Looks like a
> > cross-call to me, except that it does not pass a function
> > pointer, so you can argue semantics here...
>
> Right, it's the direct path rather than the generic
> smp4m_cross_call_irq path.  Semantics only.
>
> > What do you think about making SMP on 2.5 working, Keith?
> > I was just going to look at it, but if you want it, I don't mind.
>
> Fire away.  My time is somewhat limited, so I'll be focusing my energy
> on 2.5 hypersparc for a while.  If you can make SMP SuperSPARC work,
> that'll mean less work for me when I look at SMP hyper.
>
> I do have one more pending SMP patch, which I'll send shortly.
>
> --
> Keith M Wesolowski <[email protected]> http://foobazco.org/~wesolows
> ------(( Project Foobazco Coordinator and Network Administrator ))------
> "May Buddha bless all stubborn people!"
> -- Uliassutai Karakorum Blake
> -
> To unsubscribe from this list: send the line "unsubscribe sparclinux" in
> the body of a message to [email protected]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.