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: Wolfgang Grandegger <wolfgang.grandegger@bluewin.ch>,
	Wolfgang Denk <wd@denx.de>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: [PATCH and RFC] Remove request_8xxirq
Date: Mon, 24 Jun 2002 20:03:58 -0400	[thread overview]
Message-ID: <3D17B36E.2040502@embeddededge.com> (raw)
In-Reply-To: 20020624224100.GL3489@opus.bloom.county


Tom Rini wrote:

> They're provided to keep compatibility.  I do want to see this get into
> 2.4, and breaking somebodys already working custom driver in 2.4 is bad.

Let's just do the minimal changes in 2.4 to make request_irq() work for
stuff like the PCMCIA drivers.  Forget about the 8259, as I think the only
board that uses it is the MBX, and if people really need it, they can hack
something in as it hasn't worked for years anyway.

> They're gone in the 2.5 version of the patch (since a driver supporting
> 2.5/2.6 will have all sorts of other compatibility macros anyhow).

I'm working on 2.5 now, and I'll implement something better/different
that may not ever make it into 2.4.  Also, you guys have removed all of
the intercepts for RTLinux and RTAI, so I need to put that back in
as well as create an interface for the interrupts.


	-- Dan


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

  parent reply	other threads:[~2002-06-25  0:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020620214551.GI16052@opus.bloom.county>
2002-06-20 21:58 ` [PATCH and RFC] Remove request_8xxirq 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 [this message]
     [not found] <15635.16331.965632.877856@argo.ozlabs.ibm.com>
2002-06-23 16:54 ` Stephan Linke
2002-06-21  2:32 Andy Lowe
2002-06-21  4:35 ` Dan Malek
2002-06-21  4:54   ` Andy Lowe
     [not found] <3D124DF4.6060505@embeddededge.com>
2002-06-20 22:02 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2002-06-20 20:34 Tom Rini
2002-06-20 21:04 ` Dan Malek
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

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=3D17B36E.2040502@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=trini@kernel.crashing.org \
    --cc=wd@denx.de \
    --cc=wolfgang.grandegger@bluewin.ch \
    /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).