On Sun, 2013-02-17 at 18:05 -0800, Greg KH wrote:
> On Sun, Feb 17, 2013 at 02:37:24PM +0000, Jonathan Andrews wrote:
> > From a user perspective it seems a bit crap to have to change the kernel
> > if you have a workload that preemption is harmful to.
> > In the case
> > The dim pixel code is timing critical (but as I said only a tiny
> > fraction of the total CPU usage). What I need to do is grab the CPU and
> > prevent any context switch (IRQ or PREEMPT) for this period.
> why you want to do this?
Because I need an I/O pin to change state for a short accurat
I hope this is the correct place, I expect to get abused.
I'm trying to do a mostly soft real-time task with a very small hard
real time element.
I've written some code to drive matrix LED signs using a Raspberry Pi.
Source here:
http://www.jonshouse.co.uk/download/128x32_red_green_led_sign.tar.
A few years ago I posted a feature request for a .config variable to
enable/disable screen blanking in console and frame buffer, I was told
it wasn't a real problem as userspace code was adequate.
Having used linux for a couple of years to build embedded devices im
having another go :-) It is a
4 matches
Mail list logo
