lkml.org 
[lkml]   [2004]   [Oct]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRE: [Linux-fbdev-devel] Generic VESA framebuffer driver and Videocard BOOT?
Date
From

>-----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:
>> > Why not? Of course you won't get any output before the
>graphics card has been
>> > 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).
>
>> + 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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:07    [W:0.039 / U:1.208 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site