public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Brad Boyer <flar@allandria.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: linux-m68k@vger.kernel.org
Subject: Re: sonic ethernet and powerbook 520
Date: Wed, 28 Oct 2009 19:50:06 -0700	[thread overview]
Message-ID: <20091029025006.GA32242@cynthia.pants.nu> (raw)
In-Reply-To: <alpine.OSX.2.00.0910281848300.523@silk.local>

On Thu, Oct 29, 2009 at 03:22:21AM +1100, Finn Thain wrote:
> 
> I've just tested a new kernel on a powerbook 520, and it crashes while 
> reading the sonic's MAC address. The same kernel binary works fine with 
> Quadra comm-slot and on-board sonic NICs, which use the same code path.
> 
> The crash occurs while reading the MAC address during the driver probe. 
> Basically, nubus_readb(ONBOARD_SONIC_PROM_BASE) fails. Macsbug can't read 
> this address either.
> 
> Anyone want to take a guess at the real PROM base? If I had a rough idea I 
> could get Macsbug to search for the MAC address, but it's a bit difficult 
> when the memory map is full of holes. Is it worth trying to search 
> /dev/kmem?

I have no idea, but I don't think anyone else does either. The NetBSD
driver has a comment that implies pretty strongly that their driver
doesn't know where the PROM is on any PB with onboard sonic. They
read the address that is already programmed into the chip if the
PROM query fails. They also do a test probe of the address so it
doesn't die if the address doesn't go anywhere.

Does the driver work if you just skip that part and program in a
fixed value that you know is valid?

	Brad Boyer
	flar@allandria.com

  reply	other threads:[~2009-10-29  2:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-28 16:22 sonic ethernet and powerbook 520 Finn Thain
2009-10-29  2:50 ` Brad Boyer [this message]
2009-10-29  8:10   ` where to get XC68040FE33 chips? was, " Finn Thain

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=20091029025006.GA32242@cynthia.pants.nu \
    --to=flar@allandria.com \
    --cc=fthain@telegraphics.com.au \
    --cc=linux-m68k@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