Re: Bringing the OpenCBM driver into the staging tree

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Gary Jennejohn
Date: Sunday, April 18, 2010 - 9:37 am

On Sun, 18 Apr 2010 08:24:59 -0700
Greg KH <greg@kroah.com> wrote:


Plenty of reasons.  One can block the interrupt to a certain driver which
may require that for weird hardware reasons while reenabling and allowing
other interrupts to be fielded and served.

That's how the VAX and Motorola 680x0 worked and AT&T Ver. III and IV had
the splx() macros to block individual interrupts.  I worked on this stuff
in the 1980's and it was extremely convenient.

Modern HW may not require it as much, but always blocking all interrupts
with cli() isn't optimal, although it does force one to come up with
creative solutions/workarounds :)

But it's been a while since I looked at interrupt handling in Linux and
maybe that has changed.

--
Gary Jennejohn
_______________________________________________
Kernel-mentors mailing list
Kernel-mentors@selenic.com
http://selenic.com/mailman/listinfo/kernel-mentors
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Bringing the OpenCBM driver into the staging tree, Frédéric Brière, (Sat Apr 17, 10:35 am)
Re: Bringing the OpenCBM driver into the staging tree, Gary Jennejohn, (Sun Apr 18, 2:40 am)
Re: Bringing the OpenCBM driver into the staging tree, Frédéric Brière, (Sun Apr 18, 5:52 am)
Re: Bringing the OpenCBM driver into the staging tree, Gary Jennejohn, (Sun Apr 18, 9:23 am)
Re: Bringing the OpenCBM driver into the staging tree, Gary Jennejohn, (Sun Apr 18, 9:37 am)
Re: Bringing the OpenCBM driver into the staging tree, Matt Mackall, (Sun Apr 18, 10:22 am)
Re: Bringing the OpenCBM driver into the staging tree, Frédéric Brière, (Sun Apr 18, 10:22 am)
Re: Bringing the OpenCBM driver into the staging tree, Frédéric Brière, (Sun Apr 18, 10:46 am)