What Microchip doesn't (officially) tell you about the VSC8512
1–10 of 103 posts
Re: What Microchip doesn't (officially) tell you about the VSC8512
#2I'm really enjoying this series, and this one is a good example of how working with hardware can be really difficult as manufacturers aren't always fully open (or honest) about device's capabilities. But typically you don't find that out until you're already a long way through bring-up.
This was an impressive amount of research to get what he wanted out of the device!
Re: What Microchip doesn't (officially) tell you about the VSC8512
#3I'm really enjoying this series, and this one is a good example of how working with hardware can be really difficult as manufacturers aren't always fully open (or honest) about device's capabilities. But typically you don't find that out until you're already a long way through bring-up. This was an impressive amount of research to get what he wanted out of the device!
The same is common in software. A real nightmare for me was a client insisting their entire library was single threaded only to discover one small but aspect wasn't deep into development and debugging. Had to refactor a huge chunk of the project.
Re: What Microchip doesn't (officially) tell you about the VSC8512
#4This is amazing.
Oh, no wonder this is so comprehensive and fearless. It's Andrew Zonenberg.
Re: What Microchip doesn't (officially) tell you about the VSC8512
#5In perhaps a feat of nominative determinism, both the website and the feature are named serdes.
Re: What Microchip doesn't (officially) tell you about the VSC8512
#6In perhaps a feat of nominative determinism, both the website and the feature are named serdes.
SERDES is an acronym, it means serializer / deserializer, in the same way that MODEM is modulator / demodulator.
Re: What Microchip doesn't (officially) tell you about the VSC8512
#7This has generally been my experience of PHYs in general, lots of twisty passages all different
Re: What Microchip doesn't (officially) tell you about the VSC8512
#8Microchip seems to be reasonably good at opening stuff up that it's bought from other companies; various Atmel security ICs which were previously very secretive now have full datasheets freely downloadable from their site.
Re: What Microchip doesn't (officially) tell you about the VSC8512
#9Token ring was old in 1996 when my masters thesis focused on error handling behavior and simulation thereof.
I wonder if there are certain elements in certain "industrial complexes" that need to maintain or interface with legacy TR systems and that's why it's still hanging around in "dark silicon".
Re: What Microchip doesn't (officially) tell you about the VSC8512
#10On the topic of Microchip and secrecy: I downloaded and installed their IDE, MPLAB X IDE v6.20. It is for a pic3mx chip. The compiler looks like a completely generic gcc, built to cross-compile on a Windows host. However, they want a $1000.00 “licensing fee” in order to enable any optimization level above -O0.
This seems wrong. Wouldn’t this be a violation of the copyleft license covering gcc?
I’m guessing there’s some loophole, since otherwise EFF and folks would be going after them. Or perhaps they don’t know about this situation? Should I alert EFF to this situation