)
-Original Message-
From: uclinux-dev-boun...@uclinux.org
[mailto:uclinux-dev-boun...@uclinux.org] On Behalf Of Luis Alves
Sent: Tuesday, March 05, 2013 6:19 PM
To: uClinux development list
Subject: Re: [uClinux-dev] migration issue scheduling while atomic
Hi,
With preemption
Hi,
With preemption disabled, you shouldn't see that message.
In your current kernel config, under Kernel hacking what is the
state of the Sleep inside atomic section checking option?
Regards,
Luis
On Tue, Mar 5, 2013 at 5:00 PM, Christian Gieseler
christiangiese...@yahoo.de wrote:
Hi list,
Hi,
This patch fixes some broken #define's in the MC68328.h file.
Most of them are whitespaces and one is an incorrect define of TCN.
Regards,
Luis Alves
Signed-off-by: Luis Alves lja...@gmail.com
---
arch/m68k/include/asm/MC68328.h | 10 +-
1 file changed, 5 insertions(+), 5
(no packed attribute) --
10cbfe8c: 38bc 8000 movew #-32768,%a4@
10cbfe90: 38bc e000 movew #-8192,%a4@
Regards,
Luis
On Thu, Feb 21, 2013 at 1:53 PM, Greg Ungerer g...@uclinux.org wrote:
Hi Luis,
On 21/02/13 09:47, Luis Alves wrote:
This patch fixes the 68328 platform
Hi,
This patch fixes the 68328 platform init code.
I've been able to successefully build the kernel for the Xcopilot (Pilot3)
target.
A boot log can be found here: http://pastebin.com/9rT02vVi
Regards,
Luis
Signed-off-by: Luis Alves lja...@gmail.com
---
arch/m68k/include/asm/MC68328.h
Hi,
That's right. There are misplaced spaces in the defines.
I tried to find where this typos were introduced, but going back to
the old uClinux CSV achieve, in January 2001 these typos were already
there:
http://cvs.uclinux.org/cgi-bin/cvsweb.cgi/uClinux-2.4.x/include/asm-m68knommu/MC68328.h
This patch adds the correct CPU name.
Without this, it just displays UNKNOWN at boot time and at '/proc/cpuinfo'.
Regards,
Luis
Signed-off-by: Luis Alves lja...@gmail.com
---
arch/m68k/kernel/setup_no.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/m68k/kernel/setup_no.c b/arch
Hi Greg,
I'm sending the patch for the 68000 core code merge to add in the 'for-next'
branch.
Regards,
Luis Alves
Signed-off-by: Luis Alves lja...@gmail.com
---
arch/m68k/Makefile |6 +-
arch/m68k/platform/68000/Makefile | 18
).
Thanks,
Luis
On Tue, Oct 30, 2012 at 12:33 AM, Greg Ungerer g...@snapgear.com wrote:
Hi Luis,
On 30/10/12 05:38, Luis Alves wrote:
Thanks for the explanation Larry.
Meanwhile I've read some stuff about non-MMU memory alocation (I had
the wrong idea of how memory was allocated).
I guess my
Hi,
Just like the mail subject says, I'm getting a lot of these errors
when 'ls'ing' NFS mounts (but only NFS mounts).
Full error sample text:
# ls
ls: page allocation failure: order:8, mode:0xd0
Call Trace:
[008446e8] 0x8446e8
[0084683a] 0x84683a
[00851e34] 0x851e34
[008526c2]
and not 'ls' itself. Is
this correct?
Thanks
On Mon, Oct 29, 2012 at 5:49 PM, Larry Baker ba...@usgs.gov wrote:
Luis,
On 29 Oct 2012, at 8:32 AM, Luis Alves wrote:
DMA: 36*4kB 30*8kB 29*16kB 21*32kB 6*64kB 7*128kB 4*256kB 3*512kB
0*1024kB 0*2048kB 0*4096kB = 5360kB
The largest block of memory
Hi,
As pointed out by Geert, MC68000 target needs to be disabled when
MMU support is enabled.
Regards,
Luis
Signed-off-by: Luis Alves lja...@gmail.com
---
arch/m68k/Kconfig.cpu |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/m68k/Kconfig.cpu b/arch/m68k/Kconfig.cpu
index
Hi,
I think I've fixed all those minor issues.
Also, following the same scheme as in the coldfire directory, I've renamed
cpu specific files to match the cpu name.
Regards,
Luis
Signed-off-by: Luis Alves lja...@gmail.com
---
arch/m68k/Kconfig.cpu |2
Hi Greg,
Please ignore this patch also. I've detected some errors in the head.S
file (due to the linker script changes - _bss is now _bss_stop ).
I'll fix those and build a kernel to fully test these changes.
Sorry for the incovenience,
Luis
___
Hello again,
I've fixed the previous issue.
As a test I've built a kernel for the 68000 based on the git sources with this
patch and everything went smooth. (Tested it in real hardware)
Regards,
Luis
Signed-off-by: Luis Alves lja...@gmail.com
---
arch/m68k/Kconfig.cpu
and mc68000
related code.
Also I expect to merge all entry*.S into a single file.
Regards,
Luis
Signed-off-by: Luis Alves lja...@gmail.com
---
arch/m68k/Kconfig.cpu |2 +-
arch/m68k/Makefile |6 +-
arch/m68k/platform/68000/Makefile
).
To run uClinux how much minimum SRAM Required?
I've been able to run uClinux with kernel 2.0.x in a system with 512Kb
RAM, but you'll be limited in what you can do... (the kernel was
reduced to the minimum functionality).
Regards,
Luis Alves
___
uClinux
. In addition, the
EBI supports up to four regions (via chip selects), along with
programmed region-specific attributes.
[...]
If you're using the 416 BGA package you're good to go... (you can also
add more FLASH)
Regards
On Tue, Aug 28, 2012 at 2:29 PM, Luis Alves lja...@gmail.com wrote:
Hi
Hi Greg,
On Tue, Aug 7, 2012 at 7:38 AM, Greg Ungerer g...@snapgear.com wrote:
So it looks like LMA's are wrong now. What config switches do you
have enabled, and what are they set to for the kernel memory layout?
Important ones to look at are:
CONFIG_RAMBASE
0x1000
CONFIG_RAMSIZE
Hi,
I'm getting this error when trying to build python in the latest uClinux-dist:
[...]
ucfront-gcc m68k-uclinux-gcc -m68000 -Wl,-elf2flt
-Wl,-L/root/m68k/20120620/uClinux-dist/user/./../staging/lib
-Wl,-rpath-link
-Wl,/root/m68k/20120620/uClinux-dist/user/./../staging/lib -Xlinker
Thanks,
Luis Alves
___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
Hi,
Some time ago I was able to build my own non-working gcc toolchain for
the 68000 but in the end, after exchanging some mails I've found out
that support for the 68000 core was 'removed' since gcc = 4.3
(I think Greg might remember this discussion)
I've filled up a bug report
[...]
Which is what you were expecting (although it is using an OR instead
of a BSET in the first one).
Regards,
Luis
On Fri, Aug 3, 2012 at 12:07 PM, Michael Schnell mschn...@lumino.de wrote:
On 08/03/2012 11:48 AM, Luis Alves wrote:
At the moment I'm still using gcc 4.2.x
I would be thankful
On Fri, Aug 3, 2012 at 2:42 PM, Michael Schnell mschn...@lumino.de wrote:
On 08/03/2012 03:34 PM, Luis Alves wrote:
Since the volatile tells exactly that you want to use registers during
the manipulation of those variables, so I'm not surprised that it
doesn't change memory contents directly
On Fri, Aug 3, 2012 at 2:45 PM, Michael Schnell mschn...@lumino.de wrote:
On 08/03/2012 03:34 PM, Luis Alves wrote:
Since the volatile tells exactly that you want to use registers during
the manipulation of those variables, so I'm not surprised that it
doesn't change memory contents directly
that it is related to the ABI change in gcc = 4.3.x and
that I should use as target 'm68k-uclinuxoldabi' and
--with-cpu=m68000.
For now I've just changed the flags in the header file... maybe I'll
try building it with that weird target (m68k-uclinuxoldabi).
Regards,
Luis Alves
On Thu, May 17, 2012
have the time I'll try to build a toolchain (maybe using
gcc 4.7) and check the generated code.
Maybe I also could try the code sourcery one, but there is no
reference for the 'legacy 68k' family on their download page (only
coldfire).
Regards,
Luis Alves
On Tue, May 15, 2012 at 1:32 PM, Greg
reported it as a bug it in the
gcc bugzilla (Bug 53386).
Do you have any further suggestion?
Thanks and regards,
Luis Alves
On Wed, May 16, 2012 at 9:42 PM, Luis Alves lja...@gmail.com wrote:
Hi Greg,
What are the compiler options supplied to gcc?
(If you make the kernel with V=1 then you
this has been compiled in (and arch)?
Anyway, I guess I'll compile my own toolchain.
Regards,
Luis
On Tue, May 15, 2012 at 6:00 AM, Greg Ungerer g...@snapgear.com wrote:
Hi Luis,
On 15/05/12 01:07, Luis Alves wrote:
I'm currently using the 'experimental' pre-built gcc toolchain from
Hi,
I'm currently using the 'experimental' pre-built gcc toolchain from
http://www.uclinux.org/pub/uClinux/arm-elf-tools/tools-20080626/m68k-uclinux-tools-20080626.sh
to build my uClinux-dist.
I've never found any issue with that package, so I didn't even bother
to build my own toolchain.
But
the vfat fs.
I've traced the issue down to the 'unaligned.h' file. (I guess nobody has ever
used unaligned.h back in the 68328 'era'.
Regards,
Luis Alves
Signed-off-by: Luis Alves lja...@gmail.com
---
arch/m68k/include/asm/unaligned.h |2 +-
1 files changed, 1 insertions(+), 1 deletions
Hi Greg,
On Fri, May 4, 2012 at 7:53 AM, Greg Ungerer g...@snapgear.com wrote:
Hi Luis,
On 01/05/12 06:42, Luis Alves wrote:
Here is my second attempt for the 68000 code integration.
What I have done:
Merged all 68000 based cpu's in platform/68000 and deleted 68*328
subdirs.
Modified
Hi,
I've tried the 'rrdtool' included in the latest uClinux dist (20120401).
Creating the database, inserting and fetching values work fine, but
when I try to create a .png chart it do one of these two things:
1) Crash the kernel (I'm almost sure it writes in bad memory locations)
2) Give an
Thanks a lot Greg! Increased the stack size and it works now!
By default it is set to the 4k default.
Always learning!
Thanks and Regards,
Luis Alves
No dia 4 de Mai de 2012 14:41, Greg Ungerer g...@snapgear.co
Hi Luis,
On 05/04/2012 07:58 PM, Luis Alves wrote:
I've tried the 'rrdtool
Hi Greg,
I've done a similar thing for the 68000 cpu's. Ended up with a single
platform/68000 directory and removed the 68328, 68EZ328 and 68VZ328
directories.
When I have the time I'll prepare the patches and send them (probably
latter today).
I'm not sure if anyone is still building 3.x
description.
Just like I answered to Greg, I didn't have a clear view of the differences.
Please ignore this patch. I'll make the changes according to what was
discussed in here and submit a new one.
Thanks,
Luis Alves
___
uClinux-dev mailing list
uClinux-dev
/T5iDs3cw60I/AXg/8h_N9-31--o/s1029/IMG_20120425_233230.jpg
(hope the link works)
Regards,
Luis Alves
On Wed, Apr 25, 2012 at 1:36 PM, Greg Ungerer g...@snapgear.com wrote:
Hi Michael,
On 04/25/2012 02:57 AM, Michael Durrant wrote:
I have recently updated the front page
of
CONFIG_M68000/CONFIG_MCPU32
Regards,
Luis Alves
---
arch/m68k/Kconfig.cpu | 29 ++---
arch/m68k/Kconfig.machine |6 ++
arch/m68k/Makefile |9 ++---
arch/m68k/include/asm/bitops.h |2 +-
arch/m68k/include/asm/delay.h
38 matches
Mail list logo
