Rob Gubler wrote: > It looks like support for the 82575 chipset is in the "igb" driver, and not > in e1000. More info here: > http://lwn.net/Articles/241884/ > http://downloadcenter.intel.com/Detail_Desc.aspx?strState=LIVE&ProductID=38&DwnldID=17071&agr=Y&lang=eng&PrdMap=38 > > I imagine since no one has posted to the RTnet mailing list about this > chipset the chances of someone working on a port for this NIC is pretty > slim. I suppose I should look into porting it to RTnet :)
I suppose you are right. :) Jan > > -Rob > > > On Sun, Apr 19, 2009 at 4:38 PM, Rob Gubler <rgub...@gmail.com> wrote: > >> Hello, >> >> I am trying to use RTnet with my Intel 82575 NICs. I am using >> xenomai-2.5-rc1, linux 2.6.29.1, and rtnet-0.9.11. I've tried rtnet's >> e1000.ko, and e1000_new.ko drivers. Neither seems to recognize the device. >> When I built my kernel I excluded support for "Intel(R) 82575/82576 >> PCI-Express Gigabit Ethernet," so the interface isn't shown via the standard >> `ifconfig`. >> >> It seems as though the device may not be supported. The new e1000 driver >> in the RTnet experimental directory is based on the e1000-7.6.15.5 driver >> provided by the Intel guys. I downloaded the original 7.6.15.5 version, >> along with the latest, 8.0.6, and an additional driver, e1000e-0.5.18.3. I >> did a quick search for "82575" in all of these drivers (including the RTnet >> experimental e1000) and they reference the same thing: >> >> ./src/e1000_defines.h:112:/* Reserved (bits 4,5) in >= 82575 */ >> ./src/e1000_defines.h:118:/* SDP 4/5 (bits 8,9) are reserved in >= 82575 */ >> ./src/e1000_defines.h:145:/* IAME enable bit (27) was removed in >= 82575 >> */ >> >> Is there a quick and dirty hack I can try that will tie the "82575" device >> ID to a driver of similar chipset? Is the problem that a PCI Express driver >> is not written for this card? It looks as though, Mathias Koehrer did some >> work to port the 7.6.15.5 e1000 driver to RTNet. Mathias, do you have time >> to port latest e1000 driver(s) to RTnet? (Assuming that will fix my problem >> :) Any advice to help me get up and running would be great. >> >> >> >> Below is my `lspci` output for the device: >> >> 0f:00.1 Ethernet controller: Intel Corporation 82575GB Gigabit Network >> Connection (rev 02) >> Subsystem: Intel Corporation Device 145a >> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ >> Stepping- SERR+ FastB2B- DisINTx- >> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- >> <MAbort- >SERR- <PERR- INTx- >> Latency: 0, Cache Line Size: 64 bytes >> Interrupt: pin B routed to IRQ 17 >> Region 0: Memory at fcaa0000 (32-bit, non-prefetchable) [size=128K] >> Region 1: Memory at fc600000 (32-bit, non-prefetchable) [size=2M] >> Region 2: I/O ports at ccc0 [size=32] >> Region 3: Memory at fcad8000 (32-bit, non-prefetchable) [size=16K] >> Capabilities: [40] Power Management version 2 >> Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA >> PME(D0-,D1-,D2-,D3hot-,D3cold-) >> Status: D0 PME-Enable- DSel=0 DScale=0 PME- >> Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 >> Enable- >> Address: 0000000000000000 Data: 0000 >> Capabilities: [60] MSI-X: Enable- Mask- TabSize=10 >> Vector table: BAR=3 offset=00000000 >> PBA: BAR=3 offset=00002000 >> Capabilities: [a0] Express (v2) Endpoint, MSI 00 >> DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns, >> L1 <64us >> ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- >> DevCtl: Report errors: Correctable- Non-Fatal- Fatal+ >> Unsupported- >> RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ >> MaxPayload 256 bytes, MaxReadReq 512 bytes >> DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- >> TransPend- >> LnkCap: Port #4, Speed 2.5GT/s, Width x4, ASPM unknown, Latency >> L0 <4us, L1 <64us >> ClockPM- Suprise- LLActRep- BwNot- >> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk- >> ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- >> LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ >> DLActive- BWMgmt- ABWMgmt- >> >> >> >> >> Some realvant `dmesg` output: >> >> [ 2106.197710] >> [ 2106.197711] *** RTnet 0.9.11 - built on Apr 19 2009 09:42:57 *** >> [ 2106.197712] >> [ 2106.197715] RTnet: initialising real-time networking >> [ 2162.251681] Intel(R) PRO/1000 Network Driver - rt_e1000_new version >> 7.6.15.5 ported to RTnet (pciif: all) >> >> >> >> Some realvant `lsmod` output: >> >> Module Size Used by >> rt_e1000_new 151452 0 >> rt_loopback 2400 1 >> rtipv4 28020 0 >> rtpacket 5980 0 >> rtnet 38400 4 rt_e1000_new,rt_loopback,rtipv4,rtpacket >> >> >> >> Starting the device: >> >> $ sudo ./rtifconfig rteth0 up >> ioctl: No such device >> >> >> -Rob >> > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Stay on top of everything new and different, both inside and > around Java (TM) technology - register by April 22, and save > $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. > 300 plus technical and hands-on sessions. Register today. > Use priority code J9JMT32. http://p.sf.net/sfu/p > > > ------------------------------------------------------------------------ > > _______________________________________________ > RTnet-users mailing list > RTnet-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/rtnet-users
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
