Messages in this thread | | | Date | Thu, 25 Sep 2008 13:06:19 -0700 (PDT) | Subject | Re: [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM | From | David Miller <> |
| |
From: Jiri Kosina <jkosina@suse.cz> Date: Thu, 25 Sep 2008 19:24:57 +0200 (CEST)
> If being set to 0 (it's so easy to call memset(0) on a bogus pointer, > there are usually lots of them in the code) or to random garbage, it would > seem to be much more understandable, than 0xff.
Setting framebuffer bytes to 0xff is pretty common, for example for color keys and anti-aliasing pixel values.
| |