I been using nfo-2.6.3.tar.gz from http://homepage2.nifty.com/mrym3/taiyodo/eng for quite some time, and just up to b134 with the gldv3 interface and suncc compilers.

Unfortunately, after trying rich lowe's b142, I believe that the [gldv3] interface is no longer compatible. (I seem to recall seeing some movement in ARC cases).

Aug 19 08:59:23 shuttleX nfo: [ID 130221 kern.info] nfo0: type2 (nForce MCP-T) (vid: 0x10de, did: 0x0066, revid: 0xa1)
Aug 19 08:59:23 shuttleX nfo: [ID 217474 kern.info] nfo0: ilr 0x1401010b
Aug 19 08:59:23 shuttleX nfo: [ID 694339 kern.warning] WARNING: gem0: gem_do_attach: mac_alloc failed Aug 19 08:59:23 shuttleX nfo: [ID 602368 kern.warning] WARNING: nfo0: gem_do_attach failed

Effectively mac.h and mac_provider.h are different in /usr/include/sys

rich...@shuttlex:/export/dossiers/nfo-2.6.3# cc -V
cc: Sun C 5.10 SunOS_i386 2009/06/03
usage: cc [ options] files.  Use 'cc -flags' for details
rich...@shuttlex:/export/dossiers/nfo-2.6.3# CC -V
CC: Sun C++ 5.10 SunOS_i386 128229-02 2009/09/21
Usage: CC [ options ] files.  Use 'CC -flags' for details


rich...@shuttlex:/export/dossiers/nfo-2.6.3# /usr/ccs/bin/make
cc -c -xO3 -D"__INLINE__=" -U_NO_LONGLONG -D_KERNEL -U_ASM_INLINES -D_SYSCALL32 -D_SYSCALL32_IMPL -Dsun -D__sun -D__SVR4 -DC2_AUDIT -Xa -xspace -v -xc99=%all -errtags=yes -errwarn=%all -xstrconst -Di86pc -DDEBUG -DDEBUG_LEVEL=1 -DGEM_DEBUG_LEVEL=0 -UTEST_TXDESC_FULL -UTEST_RX_EMPTY -UDEBUG_HANG -UTEST_BIGENDIAN -UTEST_FOVW -UTEST_FMT1 -UTEST_FMT2 -UTEST_NF3 -UDEBUG_TCP_CKSUM -UDEBUG_UDP_CKSUM -UDEBUG_TX_SINGLE -I ./common -DGEM_CONFIG_POLLING -DGEM_CONFIG_GLDv3 -DGEM_CONFIG_VLAN_HW -DGEM_CONFIG_CKSUM_OFFLOAD -DSOLARIS10 -Unotdef -UNEVER -UGEM_GCC_RUNTIME -UGEM_COMPAT -USANITY -UGEM_CONFIG_FMA -UMODULE -UGEM_CONFIG_RX_DIRECT -DGEM_CONFIG_TX_DIRECT -UOS_PUTBACK -UCONFIG_PM -UCONFIG_CKSUM_OFFLOAD -UCONFIG_LSO -DCONFIG_POLLING -DWA_TX16 -UWA_SHORT_FRAG -DVERSION='"2.6.3"' nfo_gem.c -o i386/nfo_gem.o cc -c -xO3 -D"__INLINE__=" -U_NO_LONGLONG -D_KERNEL -U_ASM_INLINES -D_SYSCALL32 -D_SYSCALL32_IMPL -Dsun -D__sun -D__SVR4 -DC2_AUDIT -Xa -xspace -v -xc99=%all -errtags=yes -errwarn=%all -xstrconst -Di86pc -DDEBUG -DDEBUG_LEVEL=1 -DGEM_DEBUG_LEVEL=0 -UTEST_TXDESC_FULL -UTEST_RX_EMPTY -UDEBUG_HANG -UTEST_BIGENDIAN -UTEST_FOVW -UTEST_FMT1 -UTEST_FMT2 -UTEST_NF3 -UDEBUG_TCP_CKSUM -UDEBUG_UDP_CKSUM -UDEBUG_TX_SINGLE -I ./common -DGEM_CONFIG_POLLING -DGEM_CONFIG_GLDv3 -DGEM_CONFIG_VLAN_HW -DGEM_CONFIG_CKSUM_OFFLOAD -DSOLARIS10 -Unotdef -UNEVER -UGEM_GCC_RUNTIME -UGEM_COMPAT -USANITY -UGEM_CONFIG_FMA -UMODULE -UGEM_CONFIG_RX_DIRECT -DGEM_CONFIG_TX_DIRECT -UOS_PUTBACK -UCONFIG_PM -UCONFIG_CKSUM_OFFLOAD -UCONFIG_LSO -DCONFIG_POLLING -DWA_TX16 -UWA_SHORT_FRAG -DVERSION='"2.6.3"' gem.c -o i386/gem.o "gem.c", line 5909: initialization type mismatch (E_INITIALIZATION_TYPE_MISMATCH) "gem.c", line 5910: initialization type mismatch (E_INITIALIZATION_TYPE_MISMATCH)
cc: acomp failed for gem.c
*** Error code 1
make: Fatal error: Command failed for target `i386/gem.o'

For info, I tried looking at a more recent driver for different interface on this site as well (gani-2.6.7), if I copy gem_mii.h and gem.c it seems to get further, but then it really bombs out, perhaps due to intrinsic differences in the evolution of these drivers...
Has anybody been able to get over this problem ?
--
This message posted from opensolaris.org
_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss

Reply via email to