When investigating time (mis)keeping on the D-Link DI614+, I found exactly the same thing there. Walking the strings of the firmware reveals a hardcoded list ntp servers and from observation it looks like they walk down the list, primary ntp servers first, to get the time.
The D-Link firmware is cobbled together from quite a few different libraries. It maybe the code exists in a library both systems use or the systems are re-badged from a common source.
This is good slashdot fodder, but the issue has been resolved. The awi driver (wireless prism card) is being removed from the floppy and the space problem is solved. Move along nothing to see here...
Looking at the copied code in the pdf files cited, a lot of it relates to bit packing, unpacking, and color transformations. Whilst this code may be copied, there are just so many ways to do these operations. Several of the examples include MMX instructions, but pipeline scheduling usually means there's a right way (speed-up) and a wrong way (slow down). If we were kind to Sigma Designs and assumed they wrote the routines independently then it wouldn't be surprising some of them were the same, ie only so many ways to do this stuff.
Slashdot Mirror
When investigating time (mis)keeping on the D-Link DI614+, I found exactly the same thing there. Walking the strings of the firmware reveals a hardcoded list ntp servers and from observation it looks like they walk down the list, primary ntp servers first, to get the time.
The D-Link firmware is cobbled together from quite a few different libraries. It maybe the code exists in a library both systems use or the systems are re-badged from a common source.
How many others then???
Minor correction: it was Rick Rashid who was director of the Mach O/S project.
This is good slashdot fodder, but the issue has been resolved. The awi driver (wireless prism card) is being removed from the floppy and the space problem is solved. Move along nothing to see here...
Looking at the copied code in the pdf files cited, a lot of it relates to bit packing, unpacking, and color transformations. Whilst this code may be copied, there are just so many ways to do these operations. Several of the examples include MMX instructions, but pipeline scheduling usually means there's a right way (speed-up) and a wrong way (slow down). If we were kind to Sigma Designs and assumed they wrote the routines independently then it wouldn't be surprising some of them were the same, ie only so many ways to do this stuff.