Date: Tue, 29 Mar 2011 12:42:56 +0800 From: Adrian Chadd <adrian@freebsd.org> To: Nerius Landys <nlandys@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: What's so special about 0xffff EEPROM checksum Message-ID: <AANLkTinSxEYj00__4JF=88iQOSiP=MDDU-ATBGGtYU4O@mail.gmail.com> In-Reply-To: <AANLkTime069OeZ%2B6mJrES2uSZDeE6YjFmpOKx7UC1K=v@mail.gmail.com> References: <AANLkTime069OeZ%2B6mJrES2uSZDeE6YjFmpOKx7UC1K=v@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Where else have you found this check? Adrian On 29 March 2011 08:41, Nerius Landys <nlandys@gmail.com> wrote: > I'm looking at driver code in the FreeBSD kernel, and pretty much > everywhere I look I see a check for EEPROM checksum. It's always > 0xffff. What is so special about this value 0xffff? Is this value > agreed upon by hardware manufacturers? So basically they have one end > slot for data where they put in the last bytes in order to ensure that > the checksum is always 0xffff? > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTinSxEYj00__4JF=88iQOSiP=MDDU-ATBGGtYU4O>