| View previous topic :: View next topic |
| Author |
Message |
xeonburn
Apprentice
Joined: 21 Oct 2003
Posts: 172
|
 Posted: Mon May 10, 2004 6:05 am Post subject: AC97 Pctel modem in I8500, I5150, others |
 |
|
I have been trying to get this darn winmodem to work under 2.6... which doesn't seem to be a common occurrence. I got the patched experimental pctel driver and modded it to recognize my modem 8086:24c6... the configure goes well but the makefile errors:
| Code: |
as vuart.s -o vuart.o
as i8xxhal.s -o i8xxhal.o
ar rv i8xxhal.a i8xxhal.o
ar: creating i8xxhal.a
a - i8xxhal.o
gcc -Wp,-MD,./.ptserial.o.d -fno-strength-reduce -DAUDIO_ROUTING -DINTEL -DVERSION=\"0.9.7-6\" -DGCC_VERSION=\"3.3.3\" -DMODVERSIONS -DEXPORT_SYMTAB -DBUILD_SYSTEM=\""`uname -s -m -r -p`\"" -I/usr/src/linux/include -DHAL_I8XX -include /usr/src/linux/include/linux/autoconf.h -I/usr/src/linux/include/asm/mach-default -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -fomit-frame-pointer -nostdinc -iwithprefix include -DMODULE -DKBUILD_BASENAME=pctel -DKBUILD_MODNAME=pctel -c -o ptserial.o ptserial-2.6.0.c
ptserial-2.6.0.c: In function `check_modem_status':
ptserial-2.6.0.c:931: error: `ASYNC_CALLOUT_ACTIVE' undeclared (first use in this function)
ptserial-2.6.0.c:931: error: (Each undeclared identifier is reported only once
ptserial-2.6.0.c:931: error: for each function it appears in.)
ptserial-2.6.0.c: In function `rs_close':
ptserial-2.6.0.c:2866: error: `ASYNC_CALLOUT_ACTIVE' undeclared (first use in this function)
ptserial-2.6.0.c: In function `rs_hangup':
ptserial-2.6.0.c:2954: error: `ASYNC_CALLOUT_ACTIVE' undeclared (first use in this function)
ptserial-2.6.0.c: In function `block_til_ready':
ptserial-2.6.0.c:3024: error: `ASYNC_CALLOUT_ACTIVE' undeclared (first use in this function)
ptserial-2.6.0.c: In function `get_pci_irq':
ptserial-2.6.0.c:3893: error: structure has no member named `irq_resource'
make: *** [ptserial.o] Error 1
|
Does this look like a GCC problem? anyone have a similar experience? |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
