From: Cort Dougan <cort@fsmlabs.com>
To: Ron Bianco <ronb@junction.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: linux 2.4.x, PPC and openPIC interrupt priorities
Date: Wed, 31 Jan 2001 19:28:38 -0700 [thread overview]
Message-ID: <20010131192838.A24209@hq.fsmlabs.com> (raw)
In-Reply-To: <000801c08bf6$88362780$4d012ac7@warp-speed>; from Ron Bianco on Wed, Jan 31, 2001 at 06:27:32PM -0800
} 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.
You may want to just grab the tar file for the kernel source there. It's
pre-patched for all architectures. In fact, the most recent PPC trees need
no patches. The RTLinux code itself that is there (3.0-pre10) doesn't work
with 2.4.1-preX but we do have a copy that does work. That'll be in our final
3.0 release (hopefully later this week if our testing goes well).
} 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.
You can disable/enable interrupts individually but you can't adjust
priorities. Linux doesn't depend on priorities, either. Perhaps I wasn't
clear about that.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-02-01 2:28 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
2001-02-01 2:28 ` Cort Dougan [this message]
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=20010131192838.A24209@hq.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=ronb@junction.net \
/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.