RE: [Linux-fbdev-devel] Generic VESA framebuffer driver and Videocard BOOT?

From: Pallipadi, Venkatesh <hidden>
Date: 2004-10-16 09:15:24
Also in: lkml

-----Original Message-----
From: Nigel Cunningham [mailto:ncunningham@linuxmail.org] 
Sent: Saturday, October 16, 2004 2:02 AM
To: Pallipadi, Venkatesh
Cc: Geert Uytterhoeven; Linux Frame Buffer Device Development; 
Linux Kernel Development; penguinppc-team@lists.penguinppc.org
Subject: Re: [Linux-fbdev-devel] Generic VESA framebuffer 
driver and Videocard BOOT?

Hi.

On Sat, 2004-10-16 at 04:29, Venkatesh Pallipadi wrote:
quoted
quoted
Why not? Of course you won't get any output before the 
graphics card has been
quoted
quoted
re-initialized to a sane and usable state...
True. I do it on my Dell 600m (Radeon 9000M) using usermodehelper and
it works just fine. It works both with VGA and X. I need to split up
the thaw_processes into two stages though. It may not work with fb as
fb driver resumes earlier. I use the patch below for the kernel and a
userlevel x86 emulator.

I have to say though, it will help if we have a such an 
emulator in the kernel.

Just a quick question: is this the right way to distinguish kernel
threads? I've been checking if the process has an mm context 
(if p->mm).
quoted
+		if (p->parent->pid != 1)
+			continue;
I guess p->mm is a better way to catch all kernel threads. My check
above actually catches all daemons (even userspace daemons like acpid). 

Thanks,
Venki
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help