linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Ron Bianco" <ronb@junction.net>
To: "linuxppc-embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: MontaVista->sandpoint_setup.c:  changing IRQs
Date: Thu, 27 Jul 2000 13:24:15 -0700	[thread overview]
Message-ID: <000401bff808$a2501f90$4d012ac7@warp-speed> (raw)


The sandpoint code sets up the EPIC to cascade to the 8259.

I've changed it to try to use the openpic for all irqs.  And changed the sandpoint_map[]
in sandpoint_pci.c to agree with my hardware.
And all other sandpoint specific irq stuff, including #if 0'ing  out all code related to
the 8259 in the sandpoint files.

FYI, I've tried to create 2 replacement files for sandpoint_setup.c and sandpoint_pci.c
with different names but changing the Makefile where the related object files are
referenced is not sufficient to have the new files included in the build.  I don't
understand all the components that control a build well enough yet to make successful
changes to the process.  I wish there was some detailed explaination somewhere.

I'm still uncertain that I've done all the right things.

In sandpoint_init_IRQ():

- I'm uncertain about:   irq_desc[i].ctl = &open_pic   where i is less than 16.    Should
I include 0 to 15 for this?

- Since there is no setup for the 8259 now in 'my' modified code, is there someplace
amongst all the openpic init stuff where I need to explicitly provide EPIC register setup
for all interrupts to direct mode?

Thanks, Ron


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

             reply	other threads:[~2000-07-27 20:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-27 20:24 Ron Bianco [this message]
     [not found] ` <3980B7FD.1BC681E6@mvista.com>
2000-07-28 19:27   ` MontaVista->sandpoint_setup.c: changing IRQs Mark A. Greer

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='000401bff808$a2501f90$4d012ac7@warp-speed' \
    --to=ronb@junction.net \
    --cc=linuxppc-embedded@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).