From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Dennis Munsie <dmunsie@cecropia.com>
Subject: Re: printk change in 2.6.18?
Date: Wed, 19 Jul 2006 07:46:03 +0800 [thread overview]
Message-ID: <44BD72BB.2090000@gmail.com> (raw)
In-Reply-To: <1756A939-0BF4-48F1-9CEC-DB468306073C@cecropia.com>
Dennis Munsie wrote:
> I just migrated my development over to 2.6.18-rc2, and I've now
> noticed that some of the printk's that used to work under 2.6.17
> stopped working under 2.6.18. The printk's that I'm referring to are
> in intelfbhw_mode_to_hw() which is ultimately called by
> intelfb_set_par() which is called by fb_set_var().
Does the printk's show up in syslog (dmesg)? How about when intelfb
and fbcon are just loaded? How about while doing an fbset?
>
> I can put a printk() at the top of fb_set_var(), and it shows up.
> But anything else in there fails to show up.
>
> Have there been any changes in the framebuffer that would suppress
> printk's in fb_set_var()? I didn't see anything obvious, but I'm
> probably missing something.
It's possible that the changes in the vt layer may have caused this
unintentionally.
Tony
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-07-18 23:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 21:05 printk change in 2.6.18? Dennis Munsie
2006-07-18 23:46 ` Antonino A. Daplas [this message]
2006-07-19 2:41 ` Dennis Munsie
2006-07-19 11:57 ` Antonino A. Daplas
2006-07-19 15:38 ` Dennis Munsie
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=44BD72BB.2090000@gmail.com \
--to=adaplas@gmail.com \
--cc=dmunsie@cecropia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.