[EMAIL PROTECTED] wrote:
> Lo,
> This question belongs more to the ML
> you can subscribe and see archives at
> https://mail.gna.org/listinfo/eagleusb-dev/
>
> I've not tested cross-compilation... your router has usb to connect the
> fast 800 ? do you have the result of eaglediag -msc (if bash is
> implemented...) ? otherwise can you give lsusb ; lsmod ; lspci ; cat
> /proc/version and some other useful infos you can think of.
* the device doesn't run bash yet
* lsusb & lsmod aren't available
* lsmod
usb-storage 62144 0 (unused)
sd_mod 13268 0 (unused)
scsi_mod 70176 1 [usb-storage sd_mod]
videodev 8304 0
audio 50120 0 (unused)
soundcore 5280 0 [audio]
printer 12620 0 (unused)
ehci-hcd 23292 0 (unused)
usb-uhci 28380 0 (unused)
usbcore 77256 1 [usb-storage audio printer ehci-hcd
usb-uhci]
ipt_NETMAP 992 0 (unused)
ip_nat_starcraft 2224 0 (unused)
wl 418352 0 (unused)
robo 42104 -12
et 22680 0 (unused)
It does support usb printers & disk however the modem is probably not
recognized
* cat /proc/bus/usb/drivers
usbdevfs
hub
0- 15: usblp
audio
usb-storage
* this comes from dmesg
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 16:58:08 Feb 2 2005
usb-uhci.c: High bandwidth mode enabled
PCI: Enabling device 01:02.0 (0000 -> 0001)
usb-uhci.c: USB UHCI at I/O 0x100, IRQ 2
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Enabling device 01:02.1 (0000 -> 0001)
usb-uhci.c: USB UHCI at I/O 0x120, IRQ 2
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
PCI: Enabling device 01:02.2 (0000 -> 0002)
ehci_hcd 01:02.2: PCI device 1106:3104
ehci_hcd 01:02.2: irq 2, pci mem c00af000
usb.c: new USB bus registered, assigned bus number 3
PCI: 01:02.2 PCI cache line size set incorrectly (0 bytes) by BIOS/FW,
correcting to 32
ehci_hcd 01:02.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
hub.c: USB hub found
hub.c: 4 ports detected
usb.c: registered new driver usblp
printer.c: v0.13: USB Printer Device Class driver
hub.c: connect-debounce failed, port 2 disabled
hub.c: new USB device 01:02.0-2, assigned address 2
usb.c: USB device 2 (vend/prod 0x1110/0x9022) is not claimed by any
active driver.
usb.c: registered new driver audio
* and the kernel version is (/proc/version)
Linux version 2.4.20 (gcc version 3.2.3 with Broadcom modifications)
I do have problems described below. This is not a solitary
eagle-usb-only problem, many packages I've met did the same "nasty
thing" - while cross-compiling, they still tried to compile simple
pieces of code which, logically, failed to run on the machine where
the've been built.
I've looked through the configure script (very lightly) but wasn't able
to find out where these tests are located yet.
I thought about nasty hack with compilation & remote execution, but it
will be "the last thing" to do.
I would rather like to find out if there is some "clean" way
cross-compiling eagle-usb.
Another problem is that the target kernel version differs from that
running on build machine and it is compiled with different compiler (who
would have guessed :)) - configure script seems to check this.
If I try standard compilation with --build=i686-linux-gnu and
--host=mipsel-linux, script seems to ignore the proposed compiler (which
should be linux-mipsel-gcc) and uses gcc instead.
If I force the compiler with CC=mipsel-linux-gcc i get those errors
described above (with files being complied but not executable)
I would greatly appreciate any help with this problem.
ja.ro
>
> @++
> Ben'. aka baud123
> On Mar 7 juin 2005 9:52, Jan Rous a écrit :
>
>>Hi,
>>I'm trying to use Sagem [EMAIL PROTECTED] ADSL modem with wl500gx router from
>>asus.
>>The latter device runs some sort of lightweight linux on mipsel
>>architecture. It sadly doesn't support the modem "out-of-the-box", and
>>when I searched for a solution I noticed your eagle-usb kernel module.
>>
>>I tried to cross-compile it, but wasn't yet successful. I'd like to ask
>>you wheter you or anyone around you has managed to cross-compie
>>eagle-usb and could provide some how-to, or it is a thing that wasn't
>>yet required.
>>
>>I work on Debian Sarge with 2.6.10 kernel and using gcc 3.3.5. Kernel
>>for target device is located in /home/jan/ipcorder/src/kernel/kernel.
>>Toolchain for target device is located in /opt/brcm/hndtools-mipsel-linux.
>>
>>I've run into various problems while trying to cross-compile.
>>
>>
>>
>>1. 'CPPFLAGS=-I/opt/hndtools-mipsel-linux/include
>>LDFLAGS=-L/opt/hndtools-mipsel-linux/lib ./configure --host=mipsel-linux
>>--build=i686-pc-linux-gnu
>>--with-kernel-src=/home/jan/asus/src/linux/linux/'
>>
>>Completes successsfully. With just one expectable warning:
>> kernel-sources version is different from the current kernel.
>>
>>However it seems that it ignores usage of mipsel-linux-gcc:
>>
>>checking for mipsel-linux-gcc... no <--------------
>>checking for gcc... gcc
>>checking for C compiler default output file name... a.out
>>checking whether the C compiler works... yes
>>checking whether we are cross compiling... yes
>>checking for suffix of executables...
>>checking for suffix of object files... o
>>
>>
>>
>>2. When I try to pass the correct compiler to ./configure using:
>>'CC=mipsel-linux-gcc [...] ./configure [...]'
>>it doesn't work at all because:
>>
>>checking for mipsel-linux-gcc... mipsel-linux-gcc
>>checking for C compiler default output file name... configure: error: C
>>compiler cannot create executables
>>See `config.log' for more details.
>>
>>But this is logical - that compiler's output can't be run on i686
>>processors.
>>
>>
>>
>>1a-make: Using (1) and typing make is bad. It tries to compile mipsel
>>kernel with i386 gcc:
>>
>>In file included from Adiutil.h:49,
>> from eu_utils.c:27:
>>/home/jan/ipcorder/src/linux/linux/include/linux/kernel.h:143:2: #error
>>"Please fix asm/byteorder.h"
>>In file included from
>>/home/jan/ipcorder/src/linux/linux/include/linux/kernel.h:15,
>> from Adiutil.h:49,
>> from Me.c:119:
>>/home/jan/ipcorder/src/linux/linux/include/asm/byteorder.h:27:4: #error
>>"MIPS, but neither __MIPSEB__, nor __MIPSEL__???"
>>
>>
>>
>>1b-make: Using (1) and typing 'CC=mipsel-linux-gcc make' fails very soon
>>with:
>>
>>mipsel-linux-gcc -DLINUX -D__KERNEL__ -DMODULE
>>-I/home/jan/ipcorder/src/linux/linux//include
>>'-DEAGLEUSBVERSION="2.1.1"' -Wall -Wstrict-prototypes
>>-fomit-frame-pointer -fno-strict-aliasing -pipe
>>-mpreferred-stack-boundary=2 -O2 -c -o eu_main.o eu_main.c
>>cc1: invalid option `preferred-stack-boundary=2' <-----------------
>>make[1]: *** [eu_main.o] Error 1
>>make[1]: Leaving directory `/home/jan/src/eagle-usb-2.1.1/driver'
>>make: *** [build] Error 2
>>
>>
>>
>>My conclusion is that configure script and make procedure isn't designed
>>for cross-compilation at all, or I must be doing something very very
>>wrong. Can you, please, give me any comments about this issue?
>>
>>Thank you very much for your time and help,
>>with regards,
>>Jan Rous aka ja.ro
>>
>
>
>
