linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Scott Shappe <mshappe@nxnetworks.com>
To: Dan Malek <dan@mvista.com>
Cc: Elan Feingold <elan@nxnetworks.com>,
	"Linuxppc-Embedded (E-mail)"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: kernel hangs at my_console_write
Date: Mon, 6 Aug 2001 13:26:00 -0500	[thread overview]
Message-ID: <20010806132600.A20948@nxnetworks.com> (raw)
In-Reply-To: <3B6EDD68.55E51A8A@mvista.com>; from dan@mvista.com on Mon, Aug 06, 2001 at 02:09:44PM -0400


> If you take everything from the same kernel baseline, all of this will
> match.  At one point late in the 2.3.xx development, the values
> were changed from MHz to Hz.  People weren't patching/merging
> correctly to get all of the right parts at the same time.

Dan --

I can accept this statement -- it certainly makes sense -- however, it doesn't
quite fit what we actually did. We took a stock linux 2.4.5, applied a patch
that was named 'linuxppc2.4_vs_v.2.4.5.patch' (because there wasn't a 2.4.6),
which we found by chasing links from <http://www.linuxppc.org/>, and went from
there (I'd give you the exact URL, but linuxppc.org isn't answering, right
now). On the surface, this seems like it should have been the Right Thing.

I'm willing to accept that it wasn't, however, especially if someone can tell
us what the Right Thing is :-D When I tried to build an entirely unmodified
v.2.4.6 kernel, for example, it didn't even build (symbols had changed names
and only about half the code had the names changed).

Mike Shappe
NxNetworks, Inc.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-08-06 18:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-06 16:18 kernel hangs at my_console_write Navin Boppuri
2001-08-06 16:36 ` Elan Feingold
2001-08-06 18:09   ` Dan Malek
2001-08-06 18:26     ` Michael Scott Shappe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-06 16:48 Navin Boppuri

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=20010806132600.A20948@nxnetworks.com \
    --to=mshappe@nxnetworks.com \
    --cc=dan@mvista.com \
    --cc=elan@nxnetworks.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).