FEC Ethernet driver


    Sponsored Links


  • 1. displaying the udp socket details
    In vxworks shell, how to display the socket info and the port no. it is using ? For eg. I want to display the wdb socket along with the UDP port no. How do I confirm that wdb has created a UDP socket binding it to the UDP port no. 17185 ? inetstatShow() shows only TCP port no. and udpstatShow() doesn't give any info the socket creation nor about the port no. Does inetstatShow(), by default, shows WDB's UDP socket details (along with the port no.) ? If not, how to get this info ? The issue is not in finding the port no. of the socket, rather, to confirm if the socket is created and bound to the specified port.
  • 2. tcpdump in vxworks
    Hi, Can anyone tell me how to procced in porting the open BSD tcpdump code to vxworks (What are the tcpdump related networking hooks in vxowrks kernal i need to use) and remove the main funtion as it won't work in vxworks. Thanks, SVR
  • 3. target server - target connection failed in VxWorks 6.2 (workbench 2.4)
    I'm unable to create a tarter server - target connection in workbench 2.4 (VxWorks 6.2)and the log is below: ---------------------------------------------------- (Registry localhost): failed to launch target serverPossibly caused by: Back-end not connected Target Server Log: Checking License ...OK WTX Library version: Tgtsvr core version: Connecting to target agent... Error: rpccore backend client RPC: Timed out failed. ------------------------------------------------------- My target is a proprietary processor based on MIPS architecture. I don't know which CPU option to select, so set to default, it didn't work. Then I tried giving RM**** oprions hoping they indicate MIPS, but the same error. In the help, I saw the following: *************************** Check that the WDB connection to the target is fully operational by right-clicking a target in the Target Manager and selecting Target Tools > Run WTX Connection Test. This tool will verify that the communication link is correct. If there are errors, you can use the WTX and WDB logs to better track down what is wrong with the target. *************************** But, I don't find this option in my target manager. I previously used Tornado 2.2, the same image works; There, no need to specify any CPU type. But here, one needs to. Is specifying the wrong CPU an issue here or something else ?
  • 4. Flushing/Writing a file over NFS
    Hi i'm using the following: Tornado 2.2/VxWorks 5.5 for PowerPC, Sun host I'm doing fprintf()'s periodically to a file over NFS, after some time, the writes made to that file are not stored/written, and it's consistently happened under these 2 cases: - system runs idle for ~50 minutes, then write some output to the file and close it. - system runs, outputing a message every 2 minutes, after 14-16 hours, messages are not written to the file. I've read some posts about issues with writing large files over NFS, but my first case isn't a large file, but i tried adding the call to ioctl(), but it didn't help any. After my fprintf()'s, upon closing the file, I call fflush() followed by ioctl() using FIOSYNC, then fclose(). I am checking for errors for my function calls, and nothing is coming up. Also, the NFS file system is still accessible and the file i write to is still accessible and able to append to over and over. Is there anything else i'm missing? Any other calls or settings that need to be done? thanks, Kevin
  • 5. the data returned by lstFirst() and lstNext() vxworks library functions
    Is the data returned by the lstFirst() and lstNext() library functions in lstLib library in vxworks null terminated or do we have to de a null termination explicitly at the end of it.

FEC Ethernet driver

Postby xag » Wed, 28 Sep 2005 04:55:39 GMT

Does anyone write an ethernet driver for FEC device (Motorola ColdFire 


Similar Threads:

1.MPC860P FEC Linux Device Driver

Hi all,
  I'm new in this group,
I'm working on MPC860P FEC and using LXT972A from INTEl as PHY device.
I downloaded device drivers from Intel site which includes the FEC
driver fec.c and along with that fec_phy.c, fec_phy.h, lxt972a.c. My
problem is the device driver from Intel i.e., fec.c uses the structure
device in place of net_device structure which is used in all Linux
open sources so I was not able to compile and test my code.we are
using Montavista Linux for development. any body working on this pls
Thanx in advance..

2.MPC852T FEC Driver

could anyone know wher can I find a device driver C source code  for
the Fast Ethernet Controller of the MPC852T chip of Freescale.

Thanks in Advance


3.FEC W-Client USB.11g dongle driver failure

4.what does "flush_dcache_range" do in driver/net/fec.c

Hello, guys
         I'm migrating the fec driver to ARM(from the existent fec
driver for ColdFire or PPC). I want to know the purpose of the function
"flush_dcache_range" in the souce code driver/net/fec. Is it specific
to ColdFire or PPC? Does ARM also need this function? If yes, how to
write the corresponding code? Any hints are appreciated. Thanks.


5.[PATCH] fix work queues in FEC driver

6. [PATCH] include cacheflush.h in FEC driver

7. [PATCH] clean up reading of ICR register in FEC driver

8. [PATCH 5/5] net: make mpc5200 fec driver use of_mdio infrastructure

Return to VxWorks


Who is online

Users browsing this forum: No registered users and 43 guest