From: Dan Malek <dan@netx4.com>
To: "Robin O'Leary" <robin@equiinet.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: linux-2.3.37
Date: Mon, 10 Jan 2000 14:54:03 -0500 [thread overview]
Message-ID: <387A38DB.8C51AB1D@netx4.com> (raw)
In-Reply-To: 20000107213528.A29581@mail.ro.nu
Robin O'Leary wrote:
>
> I just tried building the latest 2.3.37 from ftp.kernel.org for the 8xx.
Not a good idea. There have been many changes lately that I
haven't yet updated in the 8xx tree. I am also learning to
use the new bitkeeper tools, so I am a little cautious about
checking in changes at the moment.
> There is no inline find_pte() in include/asm-ppc/pgtable.h as there was
> before, yet arch/ppc/8xx_io/commproc.c (and enet.c and fec.c) still try
> to use this function. Where has it gone?
Probably moved to something new and better :-). It looks like
we need to go back to va_to_pte() like was done in the 2.2.xx kernels.
> What is the currently recommended kernel for 860-based development and
> where can I get it?
The 2.2.xx kernels are certainly the most stable and recommended
if you are building products. There is a 2.2.13 tar image on
ppc.kernel.org/embedded for 8xx processors. I don't know when
some of the recent changes happened, but the generic 2.3.18
kernel has all of the 8xx changes.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-10 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-07 21:35 linux-2.3.37 Robin O'Leary
2000-01-10 19:54 ` Dan Malek [this message]
2000-01-10 21:10 ` linux-2.3.37 / 2.3.18 / 2.2.13 Robin O'Leary
2000-01-10 22:40 ` Dan Malek
2000-01-10 23:32 ` Alan Mimms
2000-01-11 19:17 ` Marcus Sundberg
2000-01-12 0:17 ` Dan Malek
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=387A38DB.8C51AB1D@netx4.com \
--to=dan@netx4.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=robin@equiinet.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.