hello developer friends,/ salut,
first of all, thank you for your efforts to produce
this driver, it is much appreciated.
i'm trying to get my dlink 200i to work with
eagle-usb-1.9.8 and fc2. it's got vendor id,1110, prod
id 900f. i use a pppoe connection which i know to have
vpi 0 and vci 35. the encapsulation type is PPPOE LLC.
so i added a 21 entry to
utils/scripts/eu_config_bash. i also noticed that the
code snippet below didn't build correctly on my
2.6.6-1.383 kernel that comes from fc2. i'm guessing
my kern is patched with the wait_ms already removed.
msleep is in my System.map. I noticed that my linux
src has include/linux/delay.h that does define mdelay
but my /usr/include/linux/ has no delay.h.
#if LINUX_VERSION_CODE > KERNEL_VERSION(2,6,6)
/*
* wait_ms disappear from 2.6.7 in favor of msleep
*/
static __inline__ void wait_ms(unsigned int ms)
{
if(!in_interrupt()) {
msleep (ms);
}
else
{
mdelay (ms);
}
}
#endif
to get past the above issue, i changed > to >= and
then the build finished. but i saw the following
warning:
gcc -O2 -pipe -Wall -pedantic -DLINUX -g
-DCONF_DIR="\"/etc/eagle-usb\""
-DBIN_DIR="\"/etc/eagle-usb/dsp\""
'-DEAGLEUSBVERSION="1.9.8"' eaglectrl.c -o eaglectrl
In file included from ../eu_types.h:29,
from ../eagle-usb.h:30,
from eaglectrl.c:40:
/usr/include/asm/bitops.h:327:2: warning: #warning
This includefile is not available on all
architectures.
/usr/include/asm/bitops.h:328:2: warning: #warning
Using kernel headers in userspace: atomicity not
guaranteed
so that worried me a lot. i then proceeded with my
eagleconfig. it got to the part about waiting for
modem to initialize and then reported an error.
looking at my dmesg, i see:
[eagle-usb] New USB ADSL device detected, waiting for
DSP code...
[eagle-usb] Interface 0 accepted.
[eagle-usb] created proc entry at :
/proc/driver/eagle-usb/002-003
floppy0: no floppy controllers found
[eagle-usb] ioctl EU_IO_OPTIONS received
[eagle-usb] ioctl EU_IO_DSP received
[eagle-usb] Loading DSP code to device...
[eagle-usb] DSP code successfully loaded to device
Badness in wait_ms at
/root/eagle-usb-1.9.8/driver/macros.h:133
Stack pointer is garbage, not printing trace
[eagle-usb] ioctl EU_IO_OPTIONS received
[eagle-usb] ioctl EU_IO_DSP received
[eagle-usb] Loading DSP code to device...
[eagle-usb] DSP code successfully loaded to device
[EAGLE-USB] EU_IO_GETIF: eth not yet created !!
[eagle-usb] ioctl EU_IO_OPTIONS received
[eagle-usb] ioctl EU_IO_DSP received
[eagle-usb] Loading DSP code to device...
[eagle-usb] DSP code successfully loaded to device
The part above about stack pointer is garbage really
worries me. For further information, i ran eagle diag
which reports:
Linux version 2.6.6-1.383custom ([EMAIL PROTECTED]) (gcc version
3.3.3 20040412 (Red Hat Linux 3.3.3-7)) #2 Fri Jun 18
22:55:10 MYT 2004
gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7)
# module loaded ? [ OK ]
# modem operational ? [ KO ]
# Config eagle-usb : vpi/vci/encapsulation 0 35 1
# pppd launched ? [ KO ]
# ping IP ? [ KO ]
# test DNS resolution ? [ KO ]
Complete diagnostic has been saved on
/var/log/eagle-usb/eagle_diag_20040619094922.txt
Please keep only relevant data and remove personal
informations.
if i do /etc/init.d/eagle restart, i see:
[EAGLE-USB] EU_IO_GETIF: eth not yet created !!
So I'm looking for feedback on this issue. I would
suspect that the wait_ms is a serious issue. I look
forward to any advice on how to proceed.
btw, my lsusb output for my usb modem:
Bus 002 Device 002: ID 1110:900f Analog Devices
Canada, Ltd (Allied Telesyn) AT-AR215 DSL Modem
Best regards,
Melkor
__________________________________
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.
http://mobile.yahoo.com/maildemo
