From: Dan Kegel <dkegel@ixiacom.com>
To: andrew may <acmay@acmay.homeip.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: When did ppc405 support stabilize?
Date: Mon, 20 May 2002 13:42:51 -0700 [thread overview]
Message-ID: <3CE95FCB.ADF38CE0@ixiacom.com> (raw)
In-Reply-To: 20020520133149.A17318@ecam.san.rr.com
andrew may wrote:
>
> Dan Kegel wrote:
> > 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. ...
> >
> > BTW, here's the cheesy script I'm using to fetch old kernel versions;
> > I'm relying on the v2.4.xx tags.
>
> look into 'bk export' instead of the script.
Hmm. I tried
$ bk export -rv2.4.14 bk://ppc.bkserver.net/linuxppc_2_4_devel mylinux
but it failed with
Cannot find package root.
Can some bk expert suggest the right command for grabbing a plaintext
version of the linuxppc_2_4_devel kernel corresponding roughly to
2.4.xx?
> I believe the tags are off the base Linux kernel and they have never
> worked for the 405gp.
Oh. Do you have any suggestions for how to retrieve 'ok' older
versions of the tree? I can grab as of a date, but I imagine
I'd have to be fairly picky about the date to get something good.
> The recent trees have been working for me but there have been a lot
> of changes to try to get a common OCP framework.
(OCP has to do with the built-in peripherals?) BTW,
I don't even need to get ethernet working; the bug I'm
after occurs even with loopback. All I need working
is the serial port and the core kernel.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-20 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2002-05-20 19:09 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=3CE95FCB.ADF38CE0@ixiacom.com \
--to=dkegel@ixiacom.com \
--cc=acmay@acmay.homeip.net \
--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 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.