From: Dag Nygren <dag@newtech.fi>
To: "Sarnath Kannan" <sparc64@rediffmail.com>
Cc: linuxppc-embedded@lists.linuxppc.org, dag@newtech.fi
Subject: Re: EPIC Initizn
Date: Wed, 07 Nov 2001 16:48:45 +0200 [thread overview]
Message-ID: <20011107144845.7023.qmail@dag.newtech.fi> (raw)
In-Reply-To: Message from "Sarnath Kannan" <sparc64@rediffmail.com> of "07 Nov 2001 14:35:57 GMT." <20011107143557.14912.qmail@mailweb32.rediffmail.com>
> The linux code is able to identify the NE2K ethernet
> card sitting on PCI bus and is able to talk with it.
> But my problem is that I am not getting interrupts.
> ( I verified by putting a printk in the ei_interrupt
> code )
> Another puzzling fact is that, if I program IRQ 16
> ( used by the NE2k driver. Card slot num 16,
> and hence connected to IRQ0 of EPIC ) of the EPIC for
> +ve polarity & Level Triggered , I get non-stop
> continous interrupts which just freeze the CPU.
> I am using the OpenPIC code, with slight modifns
> (modifns invovle chaning the OpenPIC data structure
> to reflect the EPIC register layout.. added a PADding..
> Another one is, I had changed OpenPIC init so that
> it initializes for 16-40 ( 16 inclusive ). )
>
> I just checked Mvista code. The "disable_IRQ" and
> "enable_IRQ" OpenPIC functions have been slightly changed
> to suit LEVEL triggered interrupt handling,
> May I know the necessity of the change ? My code
> doesnt work even after incorporating this fundaa
> into mine.
>
> Am I missing something ??
> Any help would be greatly appreciated.
Try the EPCI stuff in my VG4 port, posted earlier today.
Works fine for me. (I had the same problems you are listing)
BRGDS
Dag
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-11-07 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 14:35 EPIC Initizn Sarnath Kannan
2001-11-07 14:48 ` Dag Nygren [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=20011107144845.7023.qmail@dag.newtech.fi \
--to=dag@newtech.fi \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=sparc64@rediffmail.com \
/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).