From: Pete Popov <ppopov@pacbell.net>
To: Matthew Dharm <mdharm@momenco.com>
Cc: linux-mips <linux-mips@oss.sgi.com>,
Manoj Ekbote <Manoj_Ekbote@pmc-sierra.com>
Subject: Re: Help with OOPSes, anyone?
Date: 29 Jan 2002 08:47:04 -0800 [thread overview]
Message-ID: <1012322824.8522.232.camel@zeus> (raw)
In-Reply-To: <20020128221829.A24770@momenco.com>
On Mon, 2002-01-28 at 22:18, Matthew Dharm wrote:
> Do you know who, precisely, got the CD? I'm going to try to chase this
> down, but exact names would be helpful.
I believe Manoj has access to it and I added him to the CC without
asking ;-)
> Also, when you push that material out to the community, when did you do
> that? That is, if your work is 2.4.2-based, is it reasonable to assume
> that 2.4.2 or 2.4.3 in the CVS repository will work?
No, not necessarily. Sometimes I push out patches for new boards even
if the support is not fully baked yet. But typically I wait until I've
got something useful going. That means that the work might have been
done locally, on a 2.4.2 snapshot, and submitted once it was stable.
However, oss might have been up to 2.4.5 at that point; that, and
whatever delay is introduced because Ralf is too busy to immediately
apply the patches means that a MontaVista 2.4.2 based release does not
necessarily equal oss 2.4.2.
> Or do you take a more "fire and forget" sort of approach?
I'm not sure what you mean by that. Hopefully the above is clear
enough.
Pete
> Matthew Dharm
>
> On Mon, Jan 28, 2002 at 06:29:22PM -0800, Pete Popov wrote:
> >
> > > And 2.4.17 with the wait instruction turned off still crashes.
> >
> > > The Montavista kernel (which claims to be 2.4.0 #5 build by jsun)
> > > seems to work...
> >
> > Strange, that must have been some interim build Jun did.
> >
> > > I've done several recompiles on it, and lots of I/O
> > > traffic with no problems. Unfortunatly, I don't have the source code
> > > to this particular kernel... tho I believe that Montavista is required
> > > to release their source cod by the GPL.
> >
> > All of the open source work we do we push out to the community tree
> > immediately. That's a rule we live by and there's no exceptions. The Ocelot
> > code was pushed out back then. Since then I've seen lots of additions to that
> > directory and obviously something got broke.
> >
> > QED did receive an Alliance CD with the Ocelot LSP on it, so they should
> > be able to provide you with a copy of the cdimage, including the
> > source. But the kernel will be 2.4.2 based though -- I don't know where
> > the 2.4.0 came from.
> >
> > > Tho here's a question: What is the best compiler to build a kernel
> > > with? I've built all mine with egcs-2.91.66 which I downloaded from
> > > oss.sgi.com a while ago.
> >
> > MontaVista's, but I'm biased ;-) The toolchain will be on the CD as
> > well.
> >
> > Pete
> >
>
> --
> Matthew Dharm Work: mdharm@momenco.com
> Senior Software Designer, Momentum Computer
>
next prev parent reply other threads:[~2002-01-29 17:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-27 8:22 Help with OOPSes, anyone? Matthew Dharm
2002-01-27 10:53 ` Jason Gunthorpe
2002-01-27 22:26 ` Matthew Dharm
2002-01-28 2:39 ` Jason Gunthorpe
2002-01-28 23:31 ` Matthew Dharm
2002-01-28 23:31 ` Matthew Dharm
2002-01-28 23:50 ` Matthew Dharm
2002-01-28 23:50 ` Matthew Dharm
2002-01-28 23:54 ` Pete Popov
2002-01-29 0:09 ` Matthew Dharm
2002-01-29 0:22 ` Pete Popov
2002-01-29 2:03 ` Matthew Dharm
2002-01-29 2:29 ` Pete Popov
2002-01-29 6:18 ` Matthew Dharm
2002-01-29 16:47 ` Pete Popov [this message]
2002-01-27 17:33 ` Pete Popov
2002-01-27 22:24 ` Matthew Dharm
-- strict thread matches above, loose matches on Subject: below --
2002-01-29 18:27 Manoj Ekbote
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1012322824.8522.232.camel@zeus \
--to=ppopov@pacbell.net \
--cc=Manoj_Ekbote@pmc-sierra.com \
--cc=linux-mips@oss.sgi.com \
--cc=mdharm@momenco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.