linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <porter@cox.net>
To: luca gambazzi <luca.gambazzi@epfl.ch>
Cc: Matt Porter <porter@cox.net>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Linux on Force Computers CPCI-3750 eth drivers
Date: Wed, 9 Apr 2003 08:02:01 -0700	[thread overview]
Message-ID: <20030409080200.A24217@home.com> (raw)
In-Reply-To: <1049880169.3724.16.camel@shampoo.epfl.ch>; from luca.gambazzi@epfl.ch on Wed, Apr 09, 2003 at 11:22:49AM +0200


On Wed, Apr 09, 2003 at 11:22:49AM +0200, luca gambazzi wrote:
> I'm booting with the pcore kernel.
>
> the pcore_find_bridges function in pcore_pci.c recognize my card as a
> 6750, but the 3750 uses a 21150 bridge and not a 21154.

That makes sense.  When I did the port I had a 6750 and 680.  They
are very similar but Force is too stupid to provide a method to
uniquely identify a board at runtime.  So, you see the kludge where
anything booting a pcore kernel that has an MPC106 is a 6750 and
if it has a MPC107 then it must be a 680.

> Do you know where can i find documentation to solve this problem?
> and where I have to modify?

Talk to Force.  You need the 3750 manual.  I suspect that it has
different interrupt routing than the 6750.  Right now, you are
picking up the pcore_6750_map_irq table which has irq 10 for the
on-board tulip.  More than likely it's routed to a different input
on the 3750.  You would create a pcore_3750_map_irq, and provide
some way to uniquely identify that you are on a 3750 and have the
kernel use that map_irq function.

> here you can find the bios log, maybe you can find an answer.
> http://lsa1pc32.epfl.ch/~gamba/robox/

Definitely looks like pci interrupt routing is incorrect.  tulip
driver isn't getting interrupts.  One warning, once you get
3750 docs...don't trust them, they are often incorrect. :)

When you get this working, please post a patch so it can be
incorporated.  Good luck.

Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-04-09 15:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09  9:22 Linux on Force Computers CPCI-3750 eth drivers luca gambazzi
2003-04-09 15:02 ` Matt Porter [this message]
2003-04-09 15:22 ` Matt Porter
2003-04-11 10:40   ` luca gambazzi
  -- strict thread matches above, loose matches on Subject: below --
2003-03-29 14:55 Linux on Force Computers CPCI-3750 luca gambazzi
2003-03-29 15:43 ` Tom Rini
2003-04-04 11:49   ` Linux on Force Computers CPCI-3750 eth drivers luca gambazzi
2003-04-04 21:00     ` Tom Rini
2003-04-04 21:11     ` Matt Porter

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=20030409080200.A24217@home.com \
    --to=porter@cox.net \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=luca.gambazzi@epfl.ch \
    /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).