[uClinux-dev] 8.3 filenames on sd card

2009-03-05 Thread Tom Stalcup

Hello,

Does anyone know how to format an SD card so that uclinux can read/write 
filenames greater than 8 characters long?


I'm running uclinux on WildFire board from Steroid Micros, which has a 
MCF5282 processor.  No PC in my office is running linux, so I was hoping to 
find a Windows-based sd-card formatting program that will work.  But I can't 
seem to find one.


Thanks,

Tom

--
Tom Stalcup
Upward Innovations Inc.
www.UpwardInnovations.com
Phone: (877) 943-4328  ext. 701
Fax: (508) 495-0956 


___
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


Re: [uClinux-dev] parallel compiles

2009-03-05 Thread Mike Frysinger
On Thursday 07 February 2008 00:47:13 Mike Frysinger wrote:
 On Wednesday 06 February 2008, David McCullough wrote:
  If you have a patch,  send it in and I'll try it here and see how bad it
  is for our builds,  if it's relatively isolated I am happy to fix up
  some bits and include it,  anything that speeds builds is good,

 i'm pushing this for our next-next release (so current development tree).
 only noticed net-tools failing so far (but i posted a patch for that)
 ---
 Do not force -j1 in subdirs and use -j$(HOST_NCPU) for _only targets.

ping ...
-mike


signature.asc
Description: This is a digitally signed message part.
___
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

Re: [uClinux-dev] mcfcache patch

2009-03-05 Thread David Wu

On Wed, 04 Mar 2009 01:12:48 -0500, Greg Ungerer g...@snapgear.com wrote:


Hi David,

David Wu wrote:
On Tue, 03 Mar 2009 16:20:10 -0500, Gavin Lambert  
gav...@compacsort.com wrote:



Quoth David Wu:
CACHE_ENABLE is defined to nop if CONFIG_UCBOOTLOADER is defined.  
The cache setting is defined in the

bootloader in this case.
Also I would like to point out that at least the cache setting is not  
quite correct if RAM size is not

16M for CONFIG_M527x.


The settings made by the CACHE_ENABLE macro are overridden fairly  
quickly by the code in cacheflush.h anyway, so it might be moot :)

 Those are for invalidate cache, right?
for example bellow:
 #if defined(CONFIG_M527x) || defined(CONFIG_M528x)
__asm__ __volatile__ (
movel  #0x81000200, %%d0\n\t
movec  %%d0, %%CACR\n\t
nop\n\t
: : : d0 );
#endif /* CONFIG_M527x || CONFIG_M528x */
 #0x81000200 is for invalidate cache. Also ARC0 and ACR1 registers are  
not modified in cacheflush.h.


But it also re-writes all the other control bits in that register.
Which is fine if they correspond exactly with what you initially
set. But will break you if you use something different.
True. that's why I don't think it is correct in either file. So here comes  
the patch which inherites the setup in bootloader.
As for the cache flush routine in cacheflush.h it works for one setting in  
our bootloader. However we have to modify it if the cache setup in the  
bootloader is changed.



It doesn't make any sense in my mind to not set an initial value
for this (in the kernel proper), but then expect the flush code
to get it right.

Better would be to actually have proper configuration options for
enabling instruction and/or data cache. And to work out the proper
CACR value (using the calculated value as required for initial
setup, and when invalidating/flushing caches).
The setup (in mcfcache.h and cacheflush.h )should based on individal  
settings for each platform/board.
including cache enable(icache, dcache or both), flush_cache_all,  
__flush_dcache_all, __flush_icache_all, etc.



Regards
Greg



Greg Ungerer  --  Principal EngineerEMAIL: g...@snapgear.com
SnapGear, a McAfee Company  PHONE:   +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
___
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






--
David Wu
___
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


[uClinux-dev] [PATCH] put all the benchmarks in the same place and sort them

2009-03-05 Thread Mike Frysinger
Signed-off-by: Mike Frysinger vap...@gentoo.org
---
 user/Kconfig |   14 +++---
 1 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/user/Kconfig b/user/Kconfig
index 7b6947c..6698e6d 100644
--- a/user/Kconfig
+++ b/user/Kconfig
@@ -2922,11 +2922,6 @@ config USER_CAL_DATE
  Print the date
  Approx. binary size: 5k
 
-config USER_DHRYSTONE_DHRYSTONE
-   bool dhrystone
-   help
- The dhrystone CPU benchmark program.
-
 config USER_DE2TSCAL_DE2TSCAL
bool de2ts-cal
 
@@ -3484,12 +3479,17 @@ config USER_LRZSZ_LSZ
 
 comment Benchmarks
 
-config USER_WHETSTONE_WHETSTONE
-   bool whetstone benchmark
+config USER_DHRYSTONE_DHRYSTONE
+   bool dhrystone
+   help
+ The dhrystone CPU benchmark program.
 
 config USER_NBENCH_NBENCH
bool nbench benchmark
 
+config USER_WHETSTONE_WHETSTONE
+   bool whetstone benchmark
+
 
 comment LIRC
 
-- 
1.6.1.3

___
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


Re: [uClinux-dev] Does anyone have m68knommu running with current uClibc and gcc 4.3?

2009-03-05 Thread Lennart Sorensen
On Wed, Mar 04, 2009 at 09:38:27AM -0500, Lennart Sorensen wrote:
 On Wed, Mar 04, 2009 at 04:45:28PM +1000, Greg Ungerer wrote:
  Given that the initial compile of put.o seems correct it is hard
  to see how this is an assembler of compiler issues.
  You are disassembly the final .gdb file, and that would pretty much
  rule out elf2flt - since its input is the ELF object.
 
 I don't think it does.  The .gdb file is created by elf2flt along with
 the flt file, and after all the .gdb file has to be an elf file that
 gdb can read that matches any layout changes done to the flt file for
 the target system.  The .gdb is not generated by the normal linker as
 far as I can tell, and even if it is, elf2flt has already done some work
 on the file before it gets to the linker.

I have attached the output of running with -elf2flt=-v for both gcc
4.1.1 and gcc 4.3.3 cases.  The putput is quote different, although I
don't yet know what it means.

-- 
Len Sorensen
TEXT - vma=0x0 len=0xfe0
DATA - vma=0xfe0 len=0x170
BSS  - vma=0x1150 len=0x230
SECTION: .text [0x80a923c]: flags=0x11f vma=0x0
 RELOCS: .text [0x80a923c]: flags=0x11f vma=0x0
  RELOC[0]: offset=0xc symbol=__uClibc_main+0xffee section=.text size=4 
fixup=0x17a (reloc=0xc)
  RELOC[0]: offset=0x22 symbol=__main+0x0 section=.text size=4 fixup=0xc4 
(reloc=0x22)
reloc[0] = 0x22
  RELOC[1]: offset=0x28 symbol=.data+0x20 section=.data size=4 fixup=0x1000 
(reloc=0x28)
reloc[1] = 0x28
  RELOC[2]: offset=0x2e symbol=puts+0x0 section=.text size=4 fixup=0x1a8 
(reloc=0x2e)
reloc[2] = 0x2e
  RELOC[3]: offset=0x50 symbol=.data+0x4c section=.data size=4 fixup=0x102c 
(reloc=0x50)
reloc[3] = 0x50
  RELOC[4]: offset=0x86 symbol=__CTOR_LIST__+0x0 section=.data size=4 
fixup=0x113c (reloc=0x86)
reloc[4] = 0x86
  RELOC[5]: offset=0xd4 symbol=.bss+0x0 section=.bss size=4 fixup=0x1150 
(reloc=0xd4)
reloc[5] = 0xd4
  RELOC[6]: offset=0x42 symbol=.data+0x4c section=.data size=4 fixup=0x102c 
(reloc=0x42)
reloc[6] = 0x42
  RELOC[7]: offset=0x5a symbol=.data+0x4c section=.data size=4 fixup=0x102c 
(reloc=0x5a)
reloc[7] = 0x5a
  RELOC[8]: offset=0x70 symbol=__CTOR_LIST__+0x0 section=.data size=4 
fixup=0x113c (reloc=0x70)
reloc[8] = 0x70
  RELOC[9]: offset=0x9c symbol=__CTOR_LIST__+0x4 section=.data size=4 
fixup=0x1140 (reloc=0x9c)
reloc[9] = 0x9c
  RELOC[10]: offset=0xb2 symbol=atexit+0x0 section=.text size=4 fixup=0x1a 
(reloc=0xb2)
reloc[10] = 0xb2
  RELOC[11]: offset=0xca symbol=.bss+0x0 section=.bss size=4 fixup=0x1150 
(reloc=0xca)
reloc[11] = 0xca
  RELOC[12]: offset=0xf0 symbol=.bss+0x14 section=.bss size=4 fixup=0x1164 
(reloc=0xf0)
reloc[12] = 0xf0
  RELOC[13]: offset=0xfa symbol=.bss+0x8 section=.bss size=4 fixup=0x1158 
(reloc=0xfa)
reloc[13] = 0xfa
  RELOC[14]: offset=0x13a symbol=.bss+0x4 section=.bss size=4 fixup=0x1154 
(reloc=0x13a)
reloc[14] = 0x13a
  RELOC[15]: offset=0x140 symbol=.bss+0xc section=.bss size=4 fixup=0x115c 
(reloc=0x140)
reloc[15] = 0x140
  RELOC[16]: offset=0x14a symbol=.bss+0x10 section=.bss size=4 fixup=0x1160 
(reloc=0x14a)
reloc[16] = 0x14a
  RELOC[17]: offset=0xe6 symbol=.bss+0x14 section=.bss size=4 fixup=0x1164 
(reloc=0xe6)
reloc[17] = 0xe6
  RELOC[18]: offset=0x100 symbol=__pthread_initialize_minimal+0x0 section=*UND* 
size=4 fixup=0x0 (reloc=0x100)
reloc[18] = 0x100
  RELOC[19]: offset=0x10c symbol=_stdio_init+0x0 section=.text size=4 
fixup=0x214 (reloc=0x10c)
reloc[19] = 0x10c
  RELOC[20]: offset=0x132 symbol=.bss+0x4 section=.bss size=4 fixup=0x1154 
(reloc=0x132)
reloc[20] = 0x132
  RELOC[21]: offset=0x156 symbol=__errno_location+0x0 section=.text size=4 
fixup=0x8e0 (reloc=0x156)
reloc[21] = 0x156
  RELOC[22]: offset=0x166 symbol=__h_errno_location+0x0 section=*UND* size=4 
fixup=0x0 (reloc=0x166)
reloc[22] = 0x166
  RELOC[23]: offset=0x17e symbol=main+0x0 section=.text size=4 fixup=0x1c 
(reloc=0x17e)
reloc[23] = 0x17e
  RELOC[24]: offset=0x186 symbol=exit+0x0 section=.text size=4 fixup=0x800 
(reloc=0x186)
reloc[24] = 0x186
  RELOC[25]: offset=0x1b2 symbol=stdout+0x0 section=.data size=4 fixup=0x1034 
(reloc=0x1b2)
reloc[25] = 0x1b2
  RELOC[26]: offset=0x1c2 symbol=__pthread_mutex_lock+0x0 section=.text size=4 
fixup=0x8f0 (reloc=0x1c2)
reloc[26] = 0x1c2
  RELOC[27]: offset=0x1d0 symbol=__fputs_unlocked+0x0 section=.text size=4 
fixup=0x418 (reloc=0x1d0)
reloc[27] = 0x1d0
  RELOC[28]: offset=0x1e6 symbol=__fputc_unlocked+0x0 section=.text size=4 
fixup=0x354 (reloc=0x1e6)
reloc[28] = 0x1e6
  RELOC[29]: offset=0x202 symbol=__pthread_mutex_unlock+0x0 section=.text 
size=4 fixup=0x8f0 (reloc=0x202)
reloc[29] = 0x202
  RELOC[30]: offset=0x21e symbol=__errno_location+0x0 section=.text size=4 
fixup=0x8e0 (reloc=0x21e)
reloc[30] = 0x21e
  RELOC[31]: offset=0x228 symbol=.data+0x84 section=.data size=4 fixup=0x1064 
(reloc=0x228)
reloc[31] = 0x228
  RELOC[32]: offset=0x232 symbol=isatty+0x0 section=.text size=4 fixup=0x774 
(reloc=0x232)
reloc[32] = 0x232
  RELOC[33]: offset=0x246 symbol=.data+0xc4 section=.data size=4 fixup=0x10a4 

[uClinux-dev] [PATCH] allow the prop dir to not exist

2009-03-05 Thread Mike Frysinger
If the prop dir does not actually exist, then don't try to process it.

Signed-off-by: Mike Frysinger vap...@gentoo.org
---
 lib/Makefile |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/lib/Makefile b/lib/Makefile
index 07655b5..1379432 100644
--- a/lib/Makefile
+++ b/lib/Makefile
@@ -91,8 +91,8 @@ dir_5_$(CONFIG_LIB_LIBOPENH323)  += libopenh323
 #
 -include Makefile.local
 
-# And build libraries in the prop directory last
-dir_9_y += $(ROOTDIR)/prop
+# And build libraries in the prop directory last (if it exists)
+dir_9_y += $(wildcard $(ROOTDIR)/prop)
 
 DIRS_NUM = 1 2 3 4 5 6 7 8 9
 DIRS_y   = $(foreach n,$(DIRS_NUM),$(sort $(dir_$(n)_y)))
-- 
1.6.1.3

___
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


Re: [uClinux-dev] [PATCH] mkconfig: allow people to control default vendor

2009-03-05 Thread Mike Frysinger
On Saturday 29 November 2008 20:37:03 Mike Frysinger wrote:
 On Thursday 06 November 2008 20:38:45 Mike Frysinger wrote:
  Rather than forcing SECURECOMPUTING as the default vendor, allow people
  to tweak this locally with a config/vendor-default file.  If said file
  does not exist, then we still get SECURECOMPUTING as the default.

 ping ...

double ping ...
-mike


signature.asc
Description: This is a digitally signed message part.
___
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

Re: [uClinux-dev] Threading and synchronization questions

2009-03-05 Thread Lennart Sorensen
On Wed, Mar 04, 2009 at 04:05:09PM +0100, Michael Schnell wrote:
 I did not know about this wording. With exec*() the process stays the  
 same (same pid), and it's still a child of the same parent. It just gets  
 new memory and some initialization is done (man execve=).

The new memory and initialization is what would make things allowed.

The reason you can do a lot of stuff before exec is that you are still
borrowing the parents memory space.

-- 
Len Sorensen
___
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


[uClinux-dev] [PATCH] allow people to declare a user/Makefile.local file

2009-03-05 Thread Mike Frysinger
Signed-off-by: Mike Frysinger vap...@gentoo.org
---
 user/Makefile |2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/user/Makefile b/user/Makefile
index 9a7acc4..d311dc6 100644
--- a/user/Makefile
+++ b/user/Makefile
@@ -438,6 +438,8 @@ dir_$(CONFIG_USER_ZEBRA_ZEBRA_ZEBRA)+= zebra
 
 dir_y += games
 
+-include Makefile.local
+
 all: config
$(MAKE) -j$(HOST_NCPU) $(sort $(dir_y) $(dir_v) $(dir_p)) || exit $$?
 
-- 
1.6.1.3

___
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


[uClinux-dev] uclibc, traget m68knommu

2009-03-05 Thread angelo

hi all,

i am trying to compile the uClinux-dist, target proc is cf 5307 
(m68knommu).


The kernel part compile fine, but compilation then fail compiling the libc.
make menuconfig shows 3 options:
1 uClibc
2 uC-libc
3 none

I am using:
ang...@miri:~/uClinux-dist$ m68k-uclinux-gcc --v
Using built-in specs.
Target: m68k-uclinux
Configured with: 
/home/gerg/src/gnu/m68k-elf/autobuild/gcc-4.1.1/configure 
--target=m68k-uclinux 
--with-headers=/home/gerg/src/gnu/m68k-elf/autobuild/linux-2.6.16/include 
--enable-multilib --disable-shared --enable-languages=c,c++

Thread model: single
gcc version 4.1.1


chosing the first option (uClibc) i get assembly error, seems that 
resolve.S syntax is for 68k and not


chmod +x ./extra/scripts/conf-header.sh
./extra/scripts/conf-header.sh .config  include/bits/uClibc_config.h
 CC ldso/ldso/ldso.oS
 AS ldso/ldso/m68k/resolve.o
ldso/ldso/m68k/resolve.S:11:4: error: invalid preprocessing directive #Save
ldso/ldso/m68k/resolve.S:14:4: error: invalid preprocessing directive #Call
ldso/ldso/m68k/resolve.S:16:4: error: invalid preprocessing directive 
#Restore

ldso/ldso/m68k/resolve.S:19:4: error: invalid preprocessing directive #Pop
ldso/ldso/m68k/resolve.S:21:4: error: invalid preprocessing directive #Call
ldso/ldso/m68k/resolve.S: Assembler messages:
ldso/ldso/m68k/resolve.S:22: Error: invalid operand mode for this 
architecture; needs 68020 or higher -- statement `jmp (%d0)' ignored

make[3]: *** [ldso/ldso/m68k/resolve.o] Error 1
make[3]: Leaving directory `/home/angelo/uClinux-dist/uClibc'
make[2]: *** [uClibc] Error 2
make[2]: Leaving directory `/home/angelo/uClinux-dist/lib'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/angelo/uClinux-dist/lib'
make: *** [subdirs] Error 1
ang...@miri:~/uClinux-dist$ nano ldso/ldso/m68k/resolve.S
ang...@miri:~/uClinux-dist$ nano linux-2.6.x/ldso/ldso/m68k/resolve.S
ang...@miri:~/uClinux-dist$ nano linux-2.6.x/ldso/ldso/m68k/resolve.S
ang...@miri:~/uClinux-dist$ nano linux-2.6.x/ldso/ldso/m68k/resolve.S



chosing the second option (uclibc)

make[3]: Leaving directory `/home/angelo/uClinux-dist/user/games'
[ ! -d gdbserver ] || ( touch gdbserver/.sgbuilt_user  make -j1 -C 
gdbserver ) || exit $?

make[3]: Entering directory `/home/angelo/uClinux-dist/user/gdbserver'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/home/angelo/uClinux-dist/user/gdbserver'
[ ! -d inetd ] || ( touch inetd/.sgbuilt_user  make -j1 -C inetd ) 
|| exit $?

make[3]: Entering directory `/home/angelo/uClinux-dist/user/inetd'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/home/angelo/uClinux-dist/user/inetd'
[ ! -d init ] || ( touch init/.sgbuilt_user  make -j1 -C init ) || 
exit $?

make[3]: Entering directory `/home/angelo/uClinux-dist/user/init'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/home/angelo/uClinux-dist/user/init'
[ ! -d ipfwadm ] || ( touch ipfwadm/.sgbuilt_user  make -j1 -C 
ipfwadm ) || exit $?

make[3]: Entering directory `/home/angelo/uClinux-dist/user/ipfwadm'
ucfront-gcc m68k-uclinux-gcc -m5307 -DCONFIG_COLDFIRE -Os -g 
-fomit-frame-pointer -pipe -fno-common -fno-builtin -Wall   -DEMBED 
-msep-data -Dlinux -D__linux__ -Dunix -D__uClinux__   -c -o ipfwadm.o 
ipfwadm.c

In file included from ipfwadm.c:114:
/home/angelo/uClinux-dist/lib/libc/include/netinet/ip_fw.h:1:25: error: 
linux/ip_fw.h: No such file or directory


i checked, include/linux/ip_fw.h is missing.

any help is appreciated,.

angelo



___
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


RE: [uClinux-dev] Threading and synchronization questions

2009-03-05 Thread Gavin Lambert
Quoth Michael Schnell:
 I did not know about this wording. With exec*() the process stays the
 same (same pid), and it's still a child of the same parent. It just gets
 new memory and some initialization is done (man execve=).

Right, but it's the new memory that does the trick.  After calling exec* it no 
longer shares an address space with its
parent, so calling other functions won't corrupt its parent any more.

___
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


Re: [uClinux-dev] [PATCH] split config steps into %_defconfig

2009-03-05 Thread David McCullough

Jivin Mike Frysinger lays it down ...
 The _default target is pretty useful, but sometimes I want to start with
 the default config.  Splitting the default config steps out into a new
 _defconfig target allows for this code flow w/out breaking it manually
 with my own CTRL+C:
   $ make Some/Board_defconfig
   $ make config_menuconfig
   $ make

Applied,

Thanks,
Davidm

 ---
  Makefile |   10 ++
  1 files changed, 6 insertions(+), 4 deletions(-)
 
 diff --git a/Makefile b/Makefile
 index 9faa7b7..f331838 100644
 --- a/Makefile
 +++ b/Makefile
 @@ -352,17 +352,19 @@ bugreport:
   *)   $(MAKEARCH) -C $(@:_romfs=) romfs;; \
   esac
  
 -%_default: conf
 - @if [ ! -f vendors/$(@:_default=)/config.device ]; then \
 - echo vendors/$(@:_default=)/config.device must exist first; \
 +%_defconfig: conf
 + @if [ ! -f vendors/$(@:_defconfig=)/config.device ]; then \
 + echo vendors/$(@:_defconfig=)/config.device must exist first; 
 \
   exit 1; \
fi
   -$(MAKE) clean  /dev/null 21
 - cp vendors/$(@:_default=)/config.device .config
 + cp vendors/$(@:_defconfig=)/config.device .config
   chmod u+x config/setconfig
   yes  | config/setconfig defaults
   config/setconfig final
   $(MAKE) dep
 +%_default: conf
 + $(MAKE) $(@:_default=_defconfig)
   $(MAKE)
  
  config_error:
 -- 
 1.6.1.3
 
 ___
 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
 

-- 
David McCullough,  david_mccullo...@securecomputing.com,  Ph:+61 734352815
McAfee - SnapGear  http://www.snapgear.comhttp://www.uCdot.org
___
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


Re: [uClinux-dev] Does anyone have m68knommu running with current uClibc and gcc 4.3?

2009-03-05 Thread Greg Ungerer

Hi Lennart,

Lennart Sorensen wrote:

On Wed, Mar 04, 2009 at 04:45:28PM +1000, Greg Ungerer wrote:

Given that the initial compile of put.o seems correct it is hard
to see how this is an assembler of compiler issues.
You are disassembly the final .gdb file, and that would pretty much
rule out elf2flt - since its input is the ELF object.


I don't think it does.  The .gdb file is created by elf2flt along with
the flt file,


No, its not.
The .gdb file is created by the ld replacement script. elf2flt
only does the conversion from ELF to FLT, nothing more.
Have a look at the ld script, typically /usr/local/m68k-uclinux/bin/ld,
to see how it creates the .gdb fi;e, and calls to elf2flt.



and after all the .gdb file has to be an elf file that
gdb can read that matches any layout changes done to the flt file for
the target system.


No, not exactly. The .gdb file is simply a fully located version
of the relocatable original.



 The .gdb is not generated by the normal linker as
far as I can tell,


It is. See the ld script for how it does it.



and even if it is, elf2flt has already done some work
on the file before it gets to the linker.


No, it hasn't.
elf2flt can only take an ELF file and convert - it doesn't modify
the original object(s).

Regards
Greg




Are you sure that the uClibc objects you compiled are the ones
that are actually being linked into your final .gdb file?


Yes.  I even disassembled the puts function from the m5200/libc.a file,
and it looks fine.


Run your app build with verbose gcc output. Check that it is actually
using the library objects that you think it is.


I will check again, but I am quite sure it has no other choice for what
to use.



--

Greg Ungerer  --  Principal EngineerEMAIL: g...@snapgear.com
SnapGear, a McAfee Company  PHONE:   +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
___
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


[uClinux-dev] [PATCH] m68knommu: m5206e build fix.

2009-03-05 Thread Steven King
Signed-off-by: Steven King sfk...@fdwdc.com

diff --git a/arch/m68knommu/platform/5206e/config.c 
b/arch/m68knommu/platform/5206e/config.c
index d01a5d2..db90254 100644
--- a/arch/m68knommu/platform/5206e/config.c
+++ b/arch/m68knommu/platform/5206e/config.c
@@ -17,6 +17,7 @@
 #include asm/coldfire.h
 #include asm/mcfsim.h
 #include asm/mcfdma.h
+#include asm/mcfuart.h
 
 /***/
 
___
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


[uClinux-dev] [PATCH] m68knommu: m528x build fix.

2009-03-05 Thread Steven King
There isn't any mcfqspi.h in the tree, and without it everything inside the 
#ifdef CONFIG_SPI is uncompilable.

Signed-off-by: Steven King sfk...@fdwdc.com

diff --git a/arch/m68knommu/platform/528x/config.c 
b/arch/m68knommu/platform/528x/config.c
index dfdb5c2..44baeb2 100644
--- a/arch/m68knommu/platform/528x/config.c
+++ b/arch/m68knommu/platform/528x/config.c
@@ -24,7 +24,6 @@
 #include asm/coldfire.h
 #include asm/mcfsim.h
 #include asm/mcfuart.h
-#include asm/mcfqspi.h
 
 #ifdef CONFIG_MTD_PARTITIONS
 #include linux/mtd/partitions.h
@@ -33,233 +32,6 @@
 /***/
 
 void coldfire_reset(void);
-static void coldfire_qspi_cs_control(u8 cs, u8 command);
-
-/***/
-
-#if defined(CONFIG_SPI)
-
-#if defined(CONFIG_WILDFIRE)
-#define SPI_NUM_CHIPSELECTS0x02
-#define SPI_PAR_VAL0x07  /* Enable DIN, DOUT, CLK */
-#define SPI_CS_MASK0x18
-
-#define FLASH_BLOCKSIZE(1024*64)
-#define FLASH_NUMBLOCKS16
-#define FLASH_TYPE m25p80
-
-#define M25P80_CS  0
-#define MMC_CS 1
-
-#ifdef CONFIG_MTD_PARTITIONS
-static struct mtd_partition stm25p_partitions[] = {
-   /* sflash */
-   [0] = {
-   .name = stm25p80,
-   .offset = 0x,
-   .size = FLASH_BLOCKSIZE * FLASH_NUMBLOCKS,
-   .mask_flags = 0
-   }
-};
-
-#endif
-
-#elif defined(CONFIG_WILDFIREMOD)
-
-#define SPI_NUM_CHIPSELECTS0x08
-#define SPI_PAR_VAL0x07  /* Enable DIN, DOUT, CLK */
-#define SPI_CS_MASK0x78
-
-#define FLASH_BLOCKSIZE(1024*64)
-#define FLASH_NUMBLOCKS64
-#define FLASH_TYPE m25p32
-/* Reserve 1M for the kernel parition */
-#define FLASH_KERNEL_SIZE   (1024 * 1024)
-
-#define M25P80_CS  5
-#define MMC_CS 6
-
-#ifdef CONFIG_MTD_PARTITIONS
-static struct mtd_partition stm25p_partitions[] = {
-   /* sflash */
-   [0] = {
-   .name = kernel,
-   .offset = FLASH_BLOCKSIZE * FLASH_NUMBLOCKS - FLASH_KERNEL_SIZE,
-   .size = FLASH_KERNEL_SIZE,
-   .mask_flags = 0
-   },
-   [1] = {
-   .name = image,
-   .offset = 0x,
-   .size = FLASH_BLOCKSIZE * FLASH_NUMBLOCKS - FLASH_KERNEL_SIZE,
-   .mask_flags = 0
-   },
-   [2] = {
-   .name = all,
-   .offset = 0x,
-   .size = FLASH_BLOCKSIZE * FLASH_NUMBLOCKS,
-   .mask_flags = 0
-   }
-};
-#endif
-
-#else
-#define SPI_NUM_CHIPSELECTS0x04
-#define SPI_PAR_VAL0x7F  /* Enable DIN, DOUT, CLK, CS0 - CS4 */
-#endif
-
-#ifdef MMC_CS
-static struct coldfire_spi_chip flash_chip_info = {
-   .mode = SPI_MODE_0,
-   .bits_per_word = 16,
-   .del_cs_to_clk = 17,
-   .del_after_trans = 1,
-   .void_write_data = 0
-};
-
-static struct coldfire_spi_chip mmc_chip_info = {
-   .mode = SPI_MODE_0,
-   .bits_per_word = 16,
-   .del_cs_to_clk = 17,
-   .del_after_trans = 1,
-   .void_write_data = 0x
-};
-#endif
-
-#ifdef M25P80_CS
-static struct flash_platform_data stm25p80_platform_data = {
-   .name = ST M25P80 SPI Flash chip,
-#ifdef CONFIG_MTD_PARTITIONS
-   .parts = stm25p_partitions,
-   .nr_parts = sizeof(stm25p_partitions) / sizeof(*stm25p_partitions),
-#endif
-   .type = FLASH_TYPE
-};
-#endif
-
-static struct spi_board_info spi_board_info[] __initdata = {
-#ifdef M25P80_CS
-   {
-   .modalias = m25p80,
-   .max_speed_hz = 1600,
-   .bus_num = 1,
-   .chip_select = M25P80_CS,
-   .platform_data = stm25p80_platform_data,
-   .controller_data = flash_chip_info
-   },
-#endif
-#ifdef MMC_CS
-   {
-   .modalias = mmc_spi,
-   .max_speed_hz = 1600,
-   .bus_num = 1,
-   .chip_select = MMC_CS,
-   .controller_data = mmc_chip_info
-   }
-#endif
-};
-
-static struct coldfire_spi_master coldfire_master_info = {
-   .bus_num = 1,
-   .num_chipselect = SPI_NUM_CHIPSELECTS,
-   .irq_source = MCF5282_QSPI_IRQ_SOURCE,
-   .irq_vector = MCF5282_QSPI_IRQ_VECTOR,
-   .irq_mask = ((0x01  MCF5282_QSPI_IRQ_SOURCE) | 0x01),
-   .irq_lp = 0x2B,  /* Level 5 and Priority 3 */
-   .par_val = SPI_PAR_VAL,
-   .cs_control = coldfire_qspi_cs_control,
-};
-
-static struct resource coldfire_spi_resources[] = {
-   [0] = {
-   .name = qspi-par,
-   .start = MCF5282_QSPI_PAR,
-   .end = MCF5282_QSPI_PAR,
-   .flags = IORESOURCE_MEM
-   },
-
-   [1] = {
-   .name = qspi-module,
-   .start = MCF5282_QSPI_QMR,
-   .end = 

Re: [uClinux-dev] Does anyone have m68knommu running with current uClibc and gcc 4.3?

2009-03-05 Thread Lennart Sorensen
On Thu, Mar 05, 2009 at 12:13:00PM +1000, Greg Ungerer wrote:
 No, its not.
 The .gdb file is created by the ld replacement script. elf2flt
 only does the conversion from ELF to FLT, nothing more.
 Have a look at the ld script, typically /usr/local/m68k-uclinux/bin/ld,
 to see how it creates the .gdb fi;e, and calls to elf2flt.

Yeah I finally figured out that part.  That's when I discovered that
gcc 4.3.3 was turning my -m5200 into -m5206 which didn't match what my
uclibc directories were using, and that it also causes the -p flag to
be passed to elf2flt since gcc 4.3.3 has a GOT while gcc 4.1.1 does not.

Turns out it was pulling in the m68k default libc code rather than the
m5200 code since it tried lib/m5206/ and found nothing and hence used
lib instead.  That caused no end of confusion.  My disasembled code no
longer shows illegal instructions from gcc 4.3.3, but it still doesn't
work. Perhaps 5206 isn't compatible with what 5200 did on gcc 4.1.1 and
doesn't work with the 5271 CPU I have.  I am going to try 5307 which
seems to be what is working for the kernel code with gcc 4.3.3.

-- 
Len Sorensen
___
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


[uClinux-dev] [PATCH] m68knommu: m532x build fix.

2009-03-05 Thread Steven King

Signed-off-by: Steven King sfk...@fdwdc.com

diff --git a/arch/m68k/include/asm/m532xsim.h 
b/arch/m68k/include/asm/m532xsim.h
index 1835fd2..e13903a 100644
--- a/arch/m68k/include/asm/m532xsim.h
+++ b/arch/m68k/include/asm/m532xsim.h
@@ -16,6 +16,7 @@
 #define MCFINT_VECBASE  64
 #define MCFINT_UART026  /* Interrupt number for UART0 */
 #define MCFINT_UART127  /* Interrupt number for UART1 */
+#define MCFINT_UART228  /* Interrupt number for UART2 */
 
 #define MCF_WTM_WCRMCF_REG16(0xFC098000)
 
___
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


Re: [uClinux-dev] Does anyone have m68knommu running with current uClibc and gcc 4.3?

2009-03-05 Thread Lennart Sorensen
On Thu, Mar 05, 2009 at 01:17:26PM -0500, Lennart Sorensen wrote:
 Yeah I finally figured out that part.  That's when I discovered that
 gcc 4.3.3 was turning my -m5200 into -m5206 which didn't match what my
 uclibc directories were using, and that it also causes the -p flag to
 be passed to elf2flt since gcc 4.3.3 has a GOT while gcc 4.1.1 does not.
 
 Turns out it was pulling in the m68k default libc code rather than the
 m5200 code since it tried lib/m5206/ and found nothing and hence used
 lib instead.  That caused no end of confusion.  My disasembled code no
 longer shows illegal instructions from gcc 4.3.3, but it still doesn't
 work. Perhaps 5206 isn't compatible with what 5200 did on gcc 4.1.1 and
 doesn't work with the 5271 CPU I have.  I am going to try 5307 which
 seems to be what is working for the kernel code with gcc 4.3.3.

So using gcc 4.3.3, uclibc 0.9.30.1, elf2flt from 20090304 checkout
(not that it seems to matter), binutils 2.19.1, and configuring for
-m5307 -msep-data, it actually generates working binaries.

For some reason gcc 4.1.1 works without -msep-data, but with tcc 4.3.3
using GOT it needs -msep-data.

But I got Hello World! as output.  Yay!

-- 
Len Sorensen
___
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


Re: [uClinux-dev] [PATCH] dosfstools: version bump to 3.0.2

2009-03-05 Thread Mike Frysinger
On Wednesday 04 March 2009 18:39:03 Mike Frysinger wrote:
 This updates dosfstools from the ancient 2.10 version to 3.0.2 which has
 a bunch of fixes.  It also includes a Blackfin fix for unaligned issues
 (you can see the patch in the patches/ subdir).  Otherwise, the 3.0.2 src
 tree is left untouched compared to the upstream tarball.

 Signed-off-by: Mike Frysinger vap...@gentoo.org
 ---

 i dont know what the limit / preference is here on file size, but since the
 patch in question is ~500kb uncompressed, ive bzipped it ...

this does have one typo which is fixed by this patch ...
-mike

--- user/dosfstools/Makefile(revision 7849)
+++ user/dosfstools/Makefile(revision 7850)
@@ -14,11 +14,11 @@ clean:
rm -f $(VER)/*.gdb
 
 romfs:
-   $(ROMFSINST) -e CONFIG_USER_DOSFSTOOLS_MKDOSFS $(VER)/mkdosfs/mkdosfs 
/sbin/mkdosfs
+   $(ROMFSINST) -e CONFIG_USER_DOSFSTOOLS_MKDOSFS $(VER)/mkdosfs 
/sbin/mkdosfs
$(ROMFSINST) -e CONFIG_USER_DOSFSTOOLS_MKDOSFS -s mkdosfs 
/sbin/mkfs.msdos
$(ROMFSINST) -e CONFIG_USER_DOSFSTOOLS_MKDOSFS -s mkdosfs 
/sbin/mkfs.vfat
 
-   $(ROMFSINST) -e CONFIG_USER_DOSFSTOOLS_DOSFSCK $(VER)/dosfsck/dosfsck 
/sbin/dosfsck
+   $(ROMFSINST) -e CONFIG_USER_DOSFSTOOLS_DOSFSCK $(VER)/dosfsck 
/sbin/dosfsck
$(ROMFSINST) -e CONFIG_USER_DOSFSTOOLS_DOSFSCK -s dosfsck 
/sbin/fsck.msdos
$(ROMFSINST) -e CONFIG_USER_DOSFSTOOLS_DOSFSCK -s dosfsck 
/sbin/fsck.vfat
 


signature.asc
Description: This is a digitally signed message part.
___
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

Re: [uClinux-dev] 8.3 filenames on sd card

2009-03-05 Thread Mike Frysinger
On Thursday 05 March 2009 11:52:59 Tom Stalcup wrote:
 Does anyone know how to format an SD card so that uclinux can read/write
 filenames greater than 8 characters long?

you're using the wrong filesystem when you mounted.  use vfat, not msdos.
-mike


signature.asc
Description: This is a digitally signed message part.
___
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