Re: [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



From: Jiri Kosina <jkosina@xxxxxxx>
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.
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux