linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Kegel <dkegel@ixiacom.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: When did ppc405 support stabilize?
Date: Mon, 20 May 2002 12:09:09 -0700	[thread overview]
Message-ID: <3CE949D5.AC5C5A9@ixiacom.com> (raw)


Hi,
I'm trying to track down a khttpd problem.
khttpd was solid in Hard Hat Linux 2.0 on ppc405,
it's stable on the x86 (at least after my recent patch),
and it's (mostly) stable on the imac running plain old 2.4.18.
However, it seems to have serious problems on ppc405
with 2.4.17 and on from linuxppc_2_4_devel.

I'd like to try older linuxppc_2_4_devel kernels
until I find where the problem started.
I guess I'll have to work my way backwards, since I don't know
when ppc405 support stabilized in that tree.

How far back should I expect to be able to go?

BTW, here's the cheesy script I'm using to fetch old kernel versions;
I'm relying on the v2.4.xx tags.

#!/bin/sh

if [ -z $1 ]; then
        echo "Usage: `basename $0` <tag> e.g v2.4.18"
        exit 1
fi

bk clone -r$1 bk://ppc.bkserver.net/linuxppc_2_4_devel
linuxppc_2_4_devel-$1
cd linuxppc_2_4_devel-$1
find -type d -exec bk get {} \;
find -name SCCS -exec rm -rf {} \;
rm -rf RESYNC/
rm -rf PENDING/
rm -rf BitKeeper/
rm ChangeSet
cd ..
mv linuxppc_2_4_devel-$1 linux
tar zcvf linux-$1-ppc_2_4_devel.tar.gz linux

Thanks,
Dan

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

             reply	other threads:[~2002-05-20 19:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-20 19:09 Dan Kegel [this message]
     [not found] <3CE94AE9.E18D2B1E@ixiacom.com>
2002-05-20 20:31 ` When did ppc405 support stabilize? andrew may
2002-05-20 20:42   ` Dan Kegel

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=3CE949D5.AC5C5A9@ixiacom.com \
    --to=dkegel@ixiacom.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).