From: "Stefan Dösinger" <stefandoesinger@gmx.at>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Pavel Machek <pavel@ucw.cz>,
Kendall Bennett <KendallB@scitechsoft.com>,
linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [Linux-fbdev-devel] Re: Generic VESA framebuffer driver and Video card BOOT?
Date: Fri, 22 Oct 2004 14:57:41 +0200 [thread overview]
Message-ID: <200410221457.41542.stefandoesinger@gmx.at> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB6003287A2A@scsmsx403.amr.corp.intel.com>
> Right now I am using call_usermodehelper() to call the
> emulator during resume and the video comes back just fine on this
> system where Ole's patch didn't work.
Can you explain me how you do this? call_usermodehelper() doesn't work for me
at resume time.
BTW, I had a look at the radeon card's resume code at 0xc000:3 and attempted
to implement it in a kernel module. The code is pretty simple, but it's quite
long. My module isn't finished, it only turns off the display and resets the
memory. I had to stop because I've a lot of things to do for school now.
Ole Rohne meant that the code is potentially dangerous because it pokes around
with undocumented PLL registers, so I will not send it to the list: I will
send it only to those who explicitly ask for it.
Stefan Dösinger
next prev parent reply other threads:[~2004-10-22 12:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 23:44 [Linux-fbdev-devel] Re: Generic VESA framebuffer driver and Video card BOOT? Pallipadi, Venkatesh
2004-10-22 12:57 ` Stefan Dösinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-21 23:10 Pallipadi, Venkatesh
2004-10-21 23:23 ` Pavel Machek
2004-10-21 22:28 Pallipadi, Venkatesh
2004-10-21 23:00 ` Pavel Machek
2004-10-14 19:02 Kendall Bennett
2004-10-15 18:36 ` Kendall Bennett
2004-10-15 21:51 ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-10-15 22:12 ` Kendall Bennett
2004-10-16 0:41 ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-10-26 11:14 ` Paulo Marques
2004-10-27 1:58 ` Kendall Bennett
2004-10-27 11:11 ` Paulo Marques
2004-10-27 19:52 ` Kendall Bennett
2004-10-20 17:01 ` Kendall Bennett
2004-10-20 17:31 ` [Linux-fbdev-devel] " Pavel Machek
2004-10-20 18:44 ` Kendall Bennett
2004-10-20 19:10 ` [Linux-fbdev-devel] " Pavel Machek
2004-10-21 19:36 ` Kendall Bennett
2004-10-21 20:47 ` [Linux-fbdev-devel] " Richard Smith
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=200410221457.41542.stefandoesinger@gmx.at \
--to=stefandoesinger@gmx.at \
--cc=KendallB@scitechsoft.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=venkatesh.pallipadi@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).