linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Keith Clayton <clay-ton@pacbell.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Fighting with Sonnet g3/l2 upgrade
Date: Sun, 14 Jan 2001 16:54:54 -0800	[thread overview]
Message-ID: <20010114165454.A443@yoda> (raw)
In-Reply-To: <19341209055331.21808@smtp.wanadoo.fr>; from benh@kernel.crashing.org on Sun, Jan 14, 2001 at 01:21:47PM +0100

[-- Attachment #1: Type: text/plain, Size: 2662 bytes --]

Nope, the Sonnet card isn't providing an IDE interface.  But that got me
thinking.  Is it possible that the l2 card is grabbing the interrupt in
question? Is there some way to check what interrupt values are being used
in the MacOS?  I can't check the Sonnet card in linux b/c linux won't boot
with it activated.  I do know that my ide interface is using interrupt 13.

Ohare based bridge.  I did some checking in the ide-pmac.c code and it
it appears that 13 is "picked out of the air".  Could this be the source of
the problem . . that the card utilizes an interrupt that matches the ide
interface?  Since the card isn't on the pci bus any sort of resource
management is out the window.

Now, supposing I were to go into ide-pmac and hard code an interrupt of 14
for the ohare bridge, rather than 13.  Are there other places in the code
that I need to worry about this (14 is a free irq according to
/proc/interrupts when I boot sans Sonnet card).

Thanks for taking the time to help figure out what's up with this.

Cheers,
Keith


On Sun, Jan 14, 2001 at 01:21:47PM +0100, Benjamin Herrenschmidt wrote:
> >Also, while this is probably a BAD idea, is it possible to create a BootX
> >build
> >where the g_l2cr_available (i think that's right) flag is set to true
> from the
> >start so that the Set G3 cache option is available for me?  Using the
> >powerlogix util I can find the G3 Cache value and I can use resedit to set it
> >by hand in the BootX Settings file. Then maybe have a bunch of debugging
> >output or something.
> >
> >I don't expect this to be a magic bullet or anything but I'm hoping to
> >understand where things are going wrong and see if it can be worked around.
> >
> >Sorry to bug you Ben . . if I had CodeWarrior myself, I'd be able to do more
> >experimentation myself first.
> 
> The hda: lost interrupt problems and the G3/L2 cache issues are 2
> different things.
> 
> Is your Sonet card also providing an IDE interface ? In this case, it's
> possible that the chipset on this card is not supported by 2.2.18 without
> the big IDE patch (which need to be fixed for powerpc).
> 
> For the G3, I'd rather figure out the correct L2CR value and "fix" it
> from userland (via /proc)
> 
> Ben.

-- 
<><><><><><><><><><><><>
Keith Clayton
clay-ton@pacbell.net

"If you don't trust me with your source code,
            why should I trust you with my computer?"

GPG key: http://home.pacbell.net/clay-ton/keith_public_key.html         
         http://www.keyserver.net                             
 
GPG fingerprint: 0C47 F1A1 0434 588C 9457  D53F D86A 5449 43F6 09A0  



[-- Attachment #2: Type: application/pgp-signature, Size: 0 bytes --]

      reply	other threads:[~2001-01-15  0:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-13 20:56 Fighting with Sonnet g3/l2 upgrade Keith Clayton
2001-01-14 12:21 ` Benjamin Herrenschmidt
2001-01-15  0:54   ` Keith Clayton [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=20010114165454.A443@yoda \
    --to=clay-ton@pacbell.net \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).