From: luca gambazzi <luca.gambazzi@epfl.ch>
To: Matt Porter <porter@cox.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Linux on Force Computers CPCI-3750 eth drivers
Date: 11 Apr 2003 12:40:32 +0200 [thread overview]
Message-ID: <1050057631.13294.1.camel@shampoo.epfl.ch> (raw)
In-Reply-To: <20030409082223.C24217@home.com>
hi matt
as you said the problem was on the eth card irq,... the irq is 9.
i prepear a patch and i'll send you in next days.
happy weekend
luca
On Wed, 2003-04-09 at 17:22, Matt Porter wrote:
> On Wed, Apr 09, 2003 at 11:22:49AM +0200, luca gambazzi wrote:
> > Hi Matt
> >
> > 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.
> >
> > Do you know where can i find documentation to solve this problem?
> > and where I have to modify?
>
> Oh, I should have mentioned the shotgun alternative to waiting on docs
> from Force. Assume that the 3750 uses cascade irqs 9-12 for all pci
> interrupts just like the 6750. Try changing the 6750 tulip map_irq
> entry to be 9,11,12 and see if any work.
>
> BTW, saw your list of devices in the /proc/pci dump. Looks like a
> fun project. :)
>
> Regards,
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-04-11 10:40 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
2003-04-09 15:22 ` Matt Porter
2003-04-11 10:40 ` luca gambazzi [this message]
-- 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=1050057631.13294.1.camel@shampoo.epfl.ch \
--to=luca.gambazzi@epfl.ch \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=porter@cox.net \
/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).