9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] i82547EI; bad EEPROM checksum
Date: Mon, 28 Feb 2011 07:27:18 -0500	[thread overview]
Message-ID: <3c385bfabf6c01c70f04316b2a9d5124@ladd.quanstro.net> (raw)
In-Reply-To: <357b5591-4883-4d9c-9ecc-b0e5afc6f609@p24g2000vbl.googlegroups.co>

On Mon Feb 28 04:55:15 EST 2011, abdullahibra@gmail.com wrote:
> hello
> i'm using 9atom on my pc but i have a problem with ethernet card, i
> have these lines when the system start
>  igbe: SPI EEPROM access not implemented
> igbe: bad EEPROM checksum - 0x0000
> igbe: SPI EEPROM access not implemented
> 
> i tried to compile the kernel and try again but with the same error
> pci | grep net  ===> 2.1.0: net 02.00.00 8086/1019 10 0:e0100000
> 131072 2:000040 01 32
> grep 1019 /sys/src/9/pc/etherigbe.c  ====>    i82547ei = (0x1019<<16)|
> 0x8086,
> 
> is there anyone have the same problem ? and how can i fix that if
> possible

now that this has leaked onto the list,
the intel manual seems to indicate that the
check that's being tripped is using an undefined
bit in the register.*

i think the first change to try would be to comment
out the check, so 

static int
at93c46r(Ctlr* ctlr)
{
	ushort sum;
	char rop[20];
	int addr, areq, bits, data, eecd, i;

	eecd = csr32r(ctlr, Eecd);
	if(eecd & Spi){
		print("igbe: SPI EEPROM access not implemented\n");
//		return 0;
	}
[...]

- erik

---
* PCI/PCI-X Family of Gigabit Ethernet Controllers
Software Developer's Manual (SDM) 82540EP/EM,
82541xx, 82544GC/EI, 82545GM/EM, 82546GB/EB, and 82547xx
version 4.0, §13.4.3 p. 232.



       reply	other threads:[~2011-02-28 12:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <357b5591-4883-4d9c-9ecc-b0e5afc6f609@p24g2000vbl.googlegroups.co>
2011-02-28 12:27 ` erik quanstrom [this message]
2011-02-28  9:43 visof
2011-02-28 10:53 ` Sergey Zhilkin
2011-02-28 12:23   ` erik quanstrom
2011-02-28 13:34     ` Sergey Zhilkin

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=3c385bfabf6c01c70f04316b2a9d5124@ladd.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).