From: "Ed Soloko" <ed@gridironsystems.com>
To: bluesmoke-devel@lists.sourceforge.net
Cc: mchehab@redhat.com
Subject: Intel 5400 EDAC Driver Issues
Date: Thu, 3 Dec 2009 09:55:47 -0800 (PST) [thread overview]
Message-ID: <013901ca7442$e96b0910$bc411b30$@com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1576 bytes --]
Hi,
I am working on the Intel 5400 EDAC driver as our product needs to monitor
memory ecc errors and such. I have found a number of discrepancies between
the code in [i5400_edac.c] and the 5400 MCH datasheet. I am wondering if
anyone else has noticed them and more importantly has changes for them.
Otherwise, I will embark upon the changes. The last commit to this code
seems to be Roberson's of 2009-10-29.
I noticed the following
1. The datasheet reference is for the 5000 MCH (minor, I know).
2. REDMEMB is an offset into Device 21,22, Function 1 but the code
uses it as an offset into Device 16, function 1 via
pvt->branchmap_werrors.
3. RECMEMA and RECMEMB usage is being incorrectly used similar to
REDMEMB.
4. The values of RECMEMA, RECMEMB, and RECFB_DIMMA are 0xf0, 0xf4,
0xf8, respectively. These are incorrect. They should be 0xe0, 0xe4, 0xe8,
respectively.
5. The pci device referenced by pvt_branch_0 is the device for
Device 21, Function 0. There needs to be a pci_device in struct i5400_pvt
for Device 21, Function 1.
6. Same comment as item #5 but for branch_1, Device 22, Function 1.
7. The function i5400_get_error_info() needs to obtain the values at
offsets NRECMEMA, NRECMEMB, and REDMEMB, from Device 21,22, Function 1
instead of Device 16, Function 1.
This is what I have found so far. If anyone can confirm what I have
found or have changes already please let me know.
Also, has this driver been used in production by anyone?
Thanks,
Ed Soloko
GridIron Systems, Inc.
[-- Attachment #1.2: Type: text/html, Size: 9583 bytes --]
[-- Attachment #2: Type: text/plain, Size: 300 bytes --]
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
bluesmoke-devel mailing list
bluesmoke-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel
reply other threads:[~2009-12-03 17:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='013901ca7442$e96b0910$bc411b30$@com' \
--to=ed@gridironsystems.com \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=mchehab@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.