linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [PATCH and RFC] Remove request_8xxirq
Date: Thu, 20 Jun 2002 17:04:17 -0400	[thread overview]
Message-ID: <3D124351.1020800@embeddededge.com> (raw)
In-Reply-To: 20020620203455.GG16052@opus.bloom.county


Tom Rini wrote:

> The first benefit of all of these changes is that it gets PCI working on
> MBX (and any other 8xx system with PCI).

No, it doesn't.  It just enables the 8259 to kinda work.  The PCI on MBX
does not work well, and this does nothing to improve it.  Does anyone have
a working MBX anymore?

> Comments?

There is more to these patches than just the interrupt change.  Why is
the CPM microcode, and so much of commproc.c changed?

Of course, I don't like it, but oh well.......It's just another hack that
doesn't do anything different.  Most importantly, I hate shit like this:

	request_irq(CPM_IRQ_OFFSET + CPMVEC_SMC2, ......

because you have to program the CPM with only the CPM vector number, not the
vector plus offset.  I want a real cascaded interrupt design, not just another
hack that opens the possibility to calling a generic PC function with the
wrong parameters.  The OpenPIC/EPIC are hacked just as badly, and there are
new integrated controllers coming that would benefit from a real design improvement
instead of just another hack.

I'm most concerned with the updates outside of just the interrupt stuff, and
I hope someone tests this.

Whatever you want......Have fun........


	-- Dan


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

  reply	other threads:[~2002-06-20 21:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-20 20:34 [PATCH and RFC] Remove request_8xxirq Tom Rini
2002-06-20 21:04 ` Dan Malek [this message]
2002-06-20 21:39   ` Tom Rini
2002-06-20 22:03     ` Dan Malek
2002-06-20 16:58       ` Benjamin Herrenschmidt
2002-06-20 22:34       ` Tom Rini
2002-06-20 21:16 ` Wolfgang Denk
     [not found] <20020620214551.GI16052@opus.bloom.county>
2002-06-20 21:58 ` Wolfgang Denk
     [not found]   ` <20020620221016.GK16052@opus.bloom.county>
     [not found]     ` <3D12F667.30902@bluewin.ch>
2002-06-24 17:00       ` Tom Rini
2002-06-24 17:49         ` Dan Malek
2002-06-24 17:59           ` Tom Rini
     [not found]         ` <3D1793E1.3030509@bluewin.ch>
     [not found]           ` <20020624224100.GL3489@opus.bloom.county>
2002-06-25  0:03             ` Dan Malek
     [not found] <3D124DF4.6060505@embeddededge.com>
2002-06-20 22:02 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2002-06-21  2:32 Andy Lowe
2002-06-21  4:35 ` Dan Malek
2002-06-21  4:54   ` Andy Lowe
     [not found] <15635.16331.965632.877856@argo.ozlabs.ibm.com>
2002-06-23 16:54 ` Stephan Linke

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=3D124351.1020800@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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).