From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: Kronos <kronos@kronoz.cjb.net>,
fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: new radeon code and acquire/release_console_sem()
Date: Sun, 14 Sep 2003 02:38:08 +0200 [thread overview]
Message-ID: <1063499888.674.43.camel@gaston> (raw)
In-Reply-To: <20030914003406.4373.qmail@web14903.mail.yahoo.com>
On Sun, 2003-09-14 at 02:34, Jon Smirl wrote:
> I get this from insmod:
> radeonfb: Unknown symbol release_console_sem
I think the problem is that the core kernel doesn't export it,
I'll look into this. I added the console sem stuff to all the
PM code (atyfb, aty128fb and radeonfb so far, chipsfb soon)
because I want to prevent any access while setting up the
chip for sleep
Ben.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
prev parent reply other threads:[~2003-09-14 0:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-14 0:23 new radeon code and acquire/release_console_sem() Jon Smirl
2003-09-14 0:29 ` Benjamin Herrenschmidt
2003-09-14 0:34 ` Jon Smirl
2003-09-14 0:38 ` Benjamin Herrenschmidt [this message]
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=1063499888.674.43.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=jonsmirl@yahoo.com \
--cc=kronos@kronoz.cjb.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).