From: Thomas Koeller <thomas.koeller@baslerweb.com>
To: Manish Lachwani <mlachwani@mvista.com>
Cc: linux-mips@linux-mips.org
Subject: Re: yosemite interrupt setup
Date: Thu, 21 Oct 2004 19:58:24 +0200 [thread overview]
Message-ID: <200410211958.24269.thomas.koeller@baslerweb.com> (raw)
In-Reply-To: <4177E5F6.3010100@mvista.com>
On Thursday 21 October 2004 18:38, Manish Lachwani wrote:
> Hi Thomas
>
> No, these should remain in the Ethernet driver. Thats because no other
> driver depends on these. Those registers are MAC subsystem registers
> only. The ethernet driver does not do any interrupt setup for other
> devices.
Hi Manish,
first of all, forget about the yosemite, as I am no longer using it. I
am currently working on our own platform port.
All the components of the Ethernet/GPI subsystem interrupt the CPU
through the interrupt vector established by writing to the CPCFG0 and
CPCFG1 registers. So if I want to write a driver that uses one of
the GPIs, or the DUART, or a watchdog counter, or the two-bit interface,
or any other component of the subsystem, then this driver will be
dependent of the ethernet driver. Have a look at the manual if
you do not believe me. The titan ethernet driver is the only one to
use this interrupt _on_the_yosemite_, but this is only because all the
other components are not used at all.
The interrupt setup should definitly be in the platform - please reconsider
your position.
thanks,
Thomas
--
--------------------------------------------------
Thomas Koeller, Software Development
Basler Vision Technologies
thomas dot koeller at baslerweb dot com
http://www.baslerweb.com
==============================
next prev parent reply other threads:[~2004-10-21 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 17:52 yosemite interrupt setup Thomas Koeller
2004-10-20 18:03 ` Manish Lachwani
2004-10-20 18:13 ` Manish Lachwani
2004-10-21 9:49 ` Thomas Koeller
2004-10-21 16:38 ` Manish Lachwani
2004-10-21 17:58 ` Thomas Koeller [this message]
2004-10-21 18:08 ` Manish Lachwani
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=200410211958.24269.thomas.koeller@baslerweb.com \
--to=thomas.koeller@baslerweb.com \
--cc=linux-mips@linux-mips.org \
--cc=mlachwani@mvista.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