From: Grant Grundler <grundler@parisc-linux.org>
To: ultralinux@vger.kernel.org
Subject: Re: [Bug 9106] Sun Fire v100 dmfe driver bug
Date: Tue, 06 Nov 2007 06:53:22 +0000 [thread overview]
Message-ID: <20071106065322.GA25501@colo.lackof.org> (raw)
In-Reply-To: <001301c81f2a$74ae0bf0$6b01a8c0@Jive>
On Sun, Nov 04, 2007 at 01:49:58PM -0800, David Miller wrote:
> From: Grant Grundler <grundler@parisc-linux.org>
> Date: Sun, 4 Nov 2007 12:02:30 -0700
>
> > http://bugzilla.kernel.org/show_bug.cgi?id‘06
> >
> > I have two possible reasons why dmfe driver is reading zeros from the seprom for the MAC address.
> > 1) IO port space routing is fu-bar - ie we are only able to talk to the chip's config space.
> > 2) outl() is implemented as a postable MMIO write (semantics demand outl be non-postable).
>
> The SROM reads aren't failing, think out of the box, the more likely
> problem is:
>
> 3) Sun doesn't initialize the SROM for the onboard network devices.
> You have to obtain the MAC address and other settings by fetching
> them from the openfirmware device properties.
Dave,
Indeed - I wasn't thinking "outside the box". I didn't realize
firmware set up resources needed for bit-banging. I thought
the seprom was accessed via I/O Port space registers.
> So use something like:
>
> #ifdef CONFIG_OF
> struct device_node *dp = pci_device_to_OF_node(pdev);
> const char *addr;
>
> addr = of_get_property(dp, "local-mac-address", NULL);
> if (addr) {
> memcpy(dev->dev_addr, addr, ETH_ALEN);
> return 1;
> }
> return 0;
> #endif
Ok - will hack something up and ask the user to try that.
I'll also look for CONFIG_OF/CONFIG_SPARC in tulip_core.c as
suggested by Richard Mortimer.
Thanks!
grant
next prev parent reply other threads:[~2007-11-06 6:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 21:34 [Bug 9106] Sun Fire v100 dmfe driver bug Richard Mortimer
2007-11-04 21:49 ` David Miller
2007-11-06 6:53 ` Grant Grundler [this message]
2007-11-06 7:11 ` David Miller
2008-01-06 8:35 ` Grant Grundler
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=20071106065322.GA25501@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=ultralinux@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).