linux-2.3.37

linux-2.3.37

[Robin O'Leary]

I just tried building the latest 2.3.37 from ftp.kernel.org for the 8xx.
It failed with the error:
    arch/ppc/8xx_io/8xx_io.a: In function `m8xx_cpm_reset':
    arch/ppc/8xx_io/8xx_io.a(.text+0x54): undefined reference to `find_pte'

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?

What is the currently recommended kernel for 860-based development and
where can I get it?

Robin O'Leary.
-- 
email: robin@equiinet.com  Equiinet Ltd., Innovation Centre, Singleton Park,
Tel.:  +44 1792 540008     Swansea  SA2 8PP, Wales, U.K.  51.6101N 3.9831W

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

Re: linux-2.3.37

[Dan Malek]

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/

Re: linux-2.3.37 / 2.3.18 / 2.2.13

[Robin O'Leary]

On Mon, Jan 10, 2000 at 02:54:03PM -0500, Dan Malek wrote:
> 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.

Most recently (apart from trying the doomed 2.3.37) I have been using
2.3.18 (from ftp://linuxppc.cs.nmt.edu/pub/linuxppc/embedded) on
custom 860T hardware.  As you may have gathered from my earlier post
on 1999-11-29, all has not been going smoothly.  Although I have now
coaxed 2.3.18 as far as trying to load the initrd, it has been an uphill
struggle all the way and I still haven't got the compressed bootloader
going properly.  Could it be that my problems stem from using 2.3.18?

Robin O'Leary.
-- 
email: robin@equiinet.com  Equiinet Ltd., Innovation Centre, Singleton Park,
Tel.:  +44 1792 540008     Swansea  SA2 8PP, Wales, U.K.  51.6101N 3.9831W

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

Re: linux-2.3.37 / 2.3.18 / 2.2.13

[Dan Malek]

Robin O'Leary wrote:


> ....  Although I have now
> coaxed 2.3.18 as far as trying to load the initrd, it has been an uphill
> struggle all the way and I still haven't got the compressed bootloader
> going properly.  Could it be that my problems stem from using 2.3.18?


As I recall, the ram disk didn't work in 2.3.18.  There are some
general things that don't work in 2.3.18, so I bailed out and
updated 2.2.xx to get something stable.  Since 2.3.xx is now
in it's mid-30's (still younger than I :-), perhaps it is mature
enough that I should visit again and make sure the 8xx configuration
continues to work.


	-- Dan

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

Re: linux-2.3.37 / 2.3.18 / 2.2.13

[Alan Mimms]

Dan, the lack of RAMDISK support is still on Alan/Linus's "must do" list
before 2.3.x can become 2.4.x.  That would seem to imply that the necessary
work has not been done.

a

On Mon, 10 Jan 2000, Dan Malek wrote: > Robin O'Leary
wrote: >  > 
> > ....  Although I have now
> > coaxed 2.3.18 as far as trying to load the initrd, it has been an uphill
> > struggle all the way and I still haven't got the compressed bootloader
> > going properly.  Could it be that my problems stem from using 2.3.18?
> 
> 
> As I recall, the ram disk didn't work in 2.3.18.  There are some
> general things that don't work in 2.3.18, so I bailed out and
> updated 2.2.xx to get something stable.  Since 2.3.xx is now
> in it's mid-30's (still younger than I :-), perhaps it is mature
> enough that I should visit again and make sure the 8xx configuration
> continues to work.
> 
> 
> 	-- Dan
-- 
Alan Mimms     Packet Engines, Inc.     Spokane, Washington [99214-0497]
  USA, Earth, Sol, Milky Way, The Local Group, Virgo Supercluster, U0
Despite the cost of living, have you noticed how popular it remains?
  -- Steven Wright?

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

Re: linux-2.3.37 / 2.3.18 / 2.2.13

[Marcus Sundberg]

Dan Malek <dan@netx4.com> writes:

> Robin O'Leary wrote:
> 
> 
> > ....  Although I have now
> > coaxed 2.3.18 as far as trying to load the initrd, it has been an uphill
> > struggle all the way and I still haven't got the compressed bootloader
> > going properly.  Could it be that my problems stem from using 2.3.18?
> 
> 
> As I recall, the ram disk didn't work in 2.3.18.  There are some
> general things that don't work in 2.3.18, so I bailed out and
> updated 2.2.xx to get something stable.  Since 2.3.xx is now
> in it's mid-30's (still younger than I :-), perhaps it is mature
> enough that I should visit again and make sure the 8xx configuration
> continues to work.

Speaking of updating and 2.2, 8xx support were broken in 2.2.14 because
of changes in kernel/head.S. Could someone take care so that the
following patch makes it into 2.2.15:

--- linux-2.2.14.orig/arch/ppc/mbxboot/head.S	Wed Dec 22 17:52:37 1999
+++ linux-2.2.14/arch/ppc/mbxboot/head.S	Tue Jan 11 16:38:54 2000
@@ -222,12 +222,10 @@
 	lwz	r5,0(r2)
 	
 	/* tell kernel we're prep */
-	/* 
-	 * get start address of kernel code which is stored as a coff
-	 * entry.  see boot/head.S -- Cort 
+	/*
+	 * now all PPC kernels start execution at address 0
 	 */
 	li	r9,0x0
-	lwz	r9,0(r9)
 	mtlr	r9
 
 	/* Invalidate the instruction cache because we just copied a

Also, is there any reason why not at least the 8xx-only code in 2.2.15
could be updated to working versions?

//Marcus
-- 
Signature under construction, please come back later.

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

Re: linux-2.3.37 / 2.3.18 / 2.2.13

[Dan Malek]

Marcus Sundberg wrote:

> Speaking of updating and 2.2, 8xx support were broken in 2.2.14 because
> of changes in kernel/head.S.


The 8xx support in the 2.2.xx tree is very, very old, and I would
be surprised if it ran on anything.  Once I get 2.3.xx up to date,
I will attempt to update 2.2.xx.

The only 2.2.xx software for the 8xx is the tarball on ppc.kernel.org.


> Also, is there any reason why not at least the 8xx-only code in 2.2.15
> could be updated to working versions?


My time to make it happen, and to be able to do make substantial
changes to the code......In the past my timing was such that the
tree was in the process of syncing with Linus, so the updates were
put "on hold".


	-- Dan

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