All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: hollis@austin.ibm.com
Cc: linuxppc-dev@lists.linuxppc.org, davidm@amberdata.demon.co.uk,
	Sven.Dickert@planb.de
Subject: Re: RFC: i8259.c cleanup
Date: Wed, 07 Nov 2001 01:37:17 -0500	[thread overview]
Message-ID: <3BE8D69D.5020600@mvista.com> (raw)
In-Reply-To: 20011106171559.D9471@austin.ibm.com


hollis@austin.ibm.com wrote:


> The following patch (to linuxppc_2_4_devel) does exactly that - it reads from
> 0xbffffff0 instead of the 8259 directly.

Ummmmm.....this probably works OK on PReP, but I don't think it is going
to have the desired effect on other systems using an 8259 :-).  You need
to find a way to to make the code you changed unique to PReP.

Thanks.


	-- Dan


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

  reply	other threads:[~2001-11-07  6:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-06 23:15 RFC: i8259.c cleanup hollis
2001-11-07  6:37 ` Dan Malek [this message]
2001-11-07  9:31   ` Geert Uytterhoeven
2001-11-07  9:40     ` Gabriel Paubert
2001-11-07  9:38 ` Gabriel Paubert
2001-11-07 17:06   ` hollis
2001-11-07 17:17     ` Geert Uytterhoeven
2001-11-07 21:17     ` Gabriel Paubert
2001-11-07 22:01       ` hollis
2001-11-07 20:46 ` Val Henson
  -- strict thread matches above, loose matches on Subject: below --
2001-11-07  4:43 Michael Sokolov
2001-11-07  6:31 ` Dag Nygren
2001-11-07  7:00   ` Dan Malek
2001-11-07  7:09     ` Dag Nygren
2001-11-07  6:38 ` Dan Malek
2001-11-07 20:31 Michael Sokolov
2001-11-07 21:13 Michael Sokolov
2001-11-07 21:22 ` Geert Uytterhoeven
2001-11-07 21:22 Michael Sokolov
2001-11-07 21:26 ` Geert Uytterhoeven
2001-11-07 22:43 Michael Sokolov
2001-11-07 22:55 Michael Sokolov
2001-11-07 23:00 Michael Sokolov
2001-11-07 23:04 Michael Sokolov

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=3BE8D69D.5020600@mvista.com \
    --to=dan@mvista.com \
    --cc=Sven.Dickert@planb.de \
    --cc=davidm@amberdata.demon.co.uk \
    --cc=hollis@austin.ibm.com \
    --cc=linuxppc-dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.