Sunnz <[EMAIL PROTECTED]> writes: > Just wondering... what could be the worse thing that could happen if > the firmware is badly written, say for a wireless device? Could it be > possible to bring the whole system down? Or would it just crash the > device itself, as if the hardware had a defect?
anecdotal evidence suggests that badly written firmware for a wireless network circuit (wpi comes to mind, that's a device with firmware the user has to install manually) is indeed capable of creating instability in more than just its own driver (possibly by confusing other parts of the networking code). Some of us have found that to be incrementally better than the device not working at all, but if badly designed devices like those can be avoided, all the better. Sometimes the user is simply stuck with the equipment they have, with no reasonable chance to replace it. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.datadok.no/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
