Re: [uClinux-dev] m68k-uclinux-20061214 toolchain problem with mcf5407 and 2.6.x which tooldchain to move to?

2009-06-11 Thread Oleksii Kuchuk
Hello Roger, I have settled down on the Sourcery G++ light toolchain (2007 release, gcc version 4.3, i don't remeber the link, but I think it is not hard to google it). But I have encountered some problems with compiling uClibc. If it will write that it could not find limits.h, you may try really

Re: [uClinux-dev] m68k-uclinux-20061214 toolchain problem with mcf5407 and 2.6.x which tooldchain to move to?

2009-06-10 Thread Greg Ungerer
Hi Roger, Roger Thornblad wrote: I've been trying to get a 20080808 dist with the latest patches running on my 5407C3 eval board. toolchain is m68k-uclinux-20061214 2.4.x kernel runs OK 2.6.x doesn't. After some chasing around I found a problem in kmem_cache_create() thinking it was

Re: [uClinux-dev] m68k-uclinux-20061214 toolchain problem with mcf5407 and 2.6.x which tooldchain to move to?

2009-06-10 Thread Oleksii Kuchuk
Hello Roger, I think you are talking about me ). That toolchain does compilation mistakes for 5407C3 board (I do not know why, but it does, I have found at least two). Newer toolchain will help. Still that distribution does not work correctly with serial port i/o on that board. To solve

RE: [uClinux-dev] m68k-uclinux-20061214 toolchain problem with mcf5407 and 2.6.x which tooldchain to move to?

2009-06-10 Thread Roger Thornblad
-Original Message- From: uclinux-dev-boun...@uclinux.org [mailto:uclinux-dev-boun...@uclinux.org] On Behalf Of Oleksii Kuchuk Sent: Wednesday, June 10, 2009 3:20 AM To: uClinux development list Subject: Re: [uClinux-dev] m68k-uclinux-20061214 toolchain problem with mcf5407 and 2.6.x which

[uClinux-dev] m68k-uclinux-20061214 toolchain problem with mcf5407 and 2.6.x which tooldchain to move to?

2009-05-29 Thread Roger Thornblad
To All, I've been trying to get a 20080808 dist with the latest patches running on my 5407C3 eval board. toolchain is m68k-uclinux-20061214 2.4.x kernel runs OK 2.6.x doesn't. After some chasing around I found a problem in kmem_cache_create() thinking it was called while in an interrupt.