From: Helge Deller <deller@gmx.de>
To: parisc-linux@lists.parisc-linux.org
Cc: Matthew Wilcox <matthew@wil.cx>
Subject: Re: [parisc-linux] Current allmodconfig failures
Date: Fri, 22 Sep 2006 20:44:03 +0200 [thread overview]
Message-ID: <200609222044.03317.deller@gmx.de> (raw)
In-Reply-To: <20060921114240.GL2585@parisc-linux.org>
On Thursday 21 September 2006 13:42, Matthew Wilcox wrote:
> $ grep undefined make.err
> WARNING: "flush_data_cache" [drivers/video/console/sticore.ko] undefined!
> WARNING: "sti_set" [drivers/video/console/sticon.ko] undefined!
> WARNING: "sti_putc" [drivers/video/console/sticon.ko] undefined!
> WARNING: "sti_bmove" [drivers/video/console/sticon.ko] undefined!
> WARNING: "sti_clear" [drivers/video/console/sticon.ko] undefined!
> WARNING: "dummy_con" [drivers/video/console/sticon.ko] undefined!
> WARNING: "conswitchp" [drivers/video/console/sticon.ko] undefined!
>
> I suspect the flush_data_cache() is a relic from the olden days -- I
> think the flush_icache_range() call should be sufficient.
Yes. flush_kernel_dcache_range() may need to stay as well.
> STI scares me.
Why ?
> I don't understand why we need the dummy console.
AFAIK, we need the dummy console, because at the point where other arches initialize their graphics subsystem, we can't do it.
We do it later when all infrastructure is available and then take_over_console().
> I don't know if it makes any sense to build your console as a module.
Why not ?
Switching from sti console to another one should be possible IMHO.
It's even good when debugging the STI functions.
> I don't know why sticore is in the console directory.
sticore is used by stifb and sticon.
It has more console functions, so IMHO it's OK.
Helge
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
prev parent reply other threads:[~2006-09-22 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 11:42 [parisc-linux] Current allmodconfig failures Matthew Wilcox
2006-09-22 18:44 ` Helge Deller [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=200609222044.03317.deller@gmx.de \
--to=deller@gmx.de \
--cc=matthew@wil.cx \
--cc=parisc-linux@lists.parisc-linux.org \
/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.