From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Daniel Ritz <daniel.ritz-ml@swissonline.ch>
Cc: linuxppc-dev@ozlabs.org,
Edward Felberbaum <efelberbaum@hotmail.com>,
linux-pcmcia@lists.infradead.org, paulus@samba.org
Subject: Re: Oops: machine check, sig: 7 [#1] - 16-bit Pccard - SOLVED!!!
Date: Tue, 11 Apr 2006 11:30:14 +1000 [thread overview]
Message-ID: <1144719014.19353.11.camel@localhost.localdomain> (raw)
In-Reply-To: <200604092257.52206.daniel.ritz-ml@swissonline.ch>
> > I see from the dmesg output from my original post that memory ranges
> > 0xfdd7f000 and 0xfddff000 are used by the Gatwick and Heathrow mac io
> > controllers. That explains the conflict with PCMCIA over 0xfd000000.
>
> interesting...the memory ranges are used by other devices yet the
> request_resource() call in PCMCIA succeeds,,,and PCI resources shoudn't
> be there in the first place then...
>
> ok, it's in file arch/powerpc/platforms/powermac/feature.c...
> i can't see any request_resource() calls in there...so CC'ing the PPC guys..
> they can sure comment...
Most of the macio stuff is in drivers/macintosh/macio_asic.c ... the
whole macio itself is a PCI device and thus should already "occupy" it's
possibly address range...
> >
> > Question, can I minimize the range of memory that is reserved 0xffffff - or
> > is it a waste of time?
> >
>
> yeah, you probably could, but it sounds like a waste of time...
>
> > Eddie
> >
>
> rgds
> -daniel
prev parent reply other threads:[~2006-04-11 1:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BAY104-F3E7D812AD1E707C145856ABC90@phx.gbl>
2006-04-09 20:57 ` Oops: machine check, sig: 7 [#1] - 16-bit Pccard - SOLVED!!! Daniel Ritz
2006-04-11 1:30 ` Benjamin Herrenschmidt [this message]
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=1144719014.19353.11.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=daniel.ritz-ml@swissonline.ch \
--cc=efelberbaum@hotmail.com \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 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.