How to design 100BASE-TX Ethernet schematics

Find reference designs and other technical resources
www.ti.com/interface/ethernet...
In this training you will learn how to design a 100BASE-TX Ethernet
schematic with a major focus on power supplies, straps and LEDs, clocks,
PHYs, MAC interfaces and magnetics.
Browse our industrial Ethernet PHYs
www.ti.com/interface/ethernet...
Browse our automotive Ethernet PHYs
www.ti.com/interface/ethernet...
Receive fast and reliable technical support from our engineers
e2e.ti.com/support/interface/f...

[@blakemcgill880]

Just want to say I appreciate all of these TI Precision Labs videos that have been coming out! They are easily digestible and informative!

[@selvakumarr6672]

Very information and covered in short time. Thanks to team.

[@rick_er2481]

Great video!

[@bennguyen1313]

So in order for an FPGA to respond to a Ping, it would need to implement layer 2 (Data Link: MAC and LLC) of the OSI model? Layer1 would be purely physical (transceiver/transformers)?
Any thoughts on the Ethernet IP cores from OpenCores, Xilinx, Lattice, etc?
For example, I imagine in order for Windows to see a custom NIC, it would need to have allocated some PCI address space for it.. but how would Windows know how to talk to it, in order to get for the operating system to access registers, including the MAC address. I assume a driver is involved (Jungo?), but is there a standard for what register contains which information?
And as a thought experiment, if you were to create a consumer NIC product, how would you buy unique MAC addresses for it?
On the other hand, if you use an off the shelf Ethernet/SPI controller (ex. ENC28J60), how would Windows see it? If the board containing the ENC28J60 provided an RS-232 Windows could talk to it, but it would recognize it as a COM port not a NIC!

[@phinok.m.628]

4:10 Yeah, I doubt my crystal can drive 500 megawatts... :D