From: "Ron Bianco" <ronb@junction.net>
To: "Cort Dougan" <cort@fsmlabs.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: linux 2.4.x, PPC and openPIC interrupt priorities
Date: Wed, 31 Jan 2001 18:27:32 -0800 [thread overview]
Message-ID: <000801c08bf6$88362780$4d012ac7@warp-speed> (raw)
In-Reply-To: <20010131170852.D19501@hq.fsmlabs.com>
Thanks a lot Cort, that's a big help.
We're wondering if rtlinux-3.0-pre10 patches can also be applied to your latest
bitkeeper 2.4.1-preX linux.
It is mentioned that the patches are to be applied to linux-2.4.0-test1.
It sure is unfortunate, to my mind, that regular linux handles interrupts that
'enable all/disable all', way.
But I understand the predicament of dealing with tons of different PICs. Must drive
driver writers nuts. :-)
Might actually make writing linux drivers for some hardware, impossible.
If we think we need mods to RTLinux for our purposes, I'll let you know.
regards, Ron
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-01 2:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 4:35 linux 2.4.x, PPC and openPIC interrupt priorities Ron Bianco
2001-02-01 0:08 ` Cort Dougan
2001-02-01 2:27 ` Ron Bianco [this message]
2001-02-01 2:28 ` Cort Dougan
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='000801c08bf6$88362780$4d012ac7@warp-speed' \
--to=ronb@junction.net \
--cc=cort@fsmlabs.com \
--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 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.