From: Matthew Wilcox <matthew@wil.cx>
To: parisc-linux@parisc-linux.org
Subject: [parisc-linux] Current allmodconfig failures
Date: Thu, 21 Sep 2006 05:42:40 -0600 [thread overview]
Message-ID: <20060921114240.GL2585@parisc-linux.org> (raw)
$ 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!
WARNING: "pdc_iodc_putc" [drivers/serial/mux.ko] undefined!
WARNING: "isa_bus_to_virt" [drivers/net/ni52.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.
The pdc_iodc_putc() call I mentioned in a missive yesterday.
isa_bus_to_virt() is an interesting one. We don't currently have
virtual mappings for the ISA bus. This driver needs to be converted to
use ioremap(). I'm tempted to mark it !PARISC in Kconfig. Or rather,
mark it ARM || MIPS || X86 since those are the only architectures which
implement isa_bus_to_virt.
STI scares me. I don't understand why we need the dummy console. I
don't know if it makes any sense to build your console as a module. I
don't know why sticore is in the console directory.
I fixed all the other allmodconfig problems I found ;-)
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next reply other threads:[~2006-09-21 11:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 11:42 Matthew Wilcox [this message]
2006-09-22 18:44 ` [parisc-linux] Current allmodconfig failures Helge Deller
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=20060921114240.GL2585@parisc-linux.org \
--to=matthew@wil.cx \
--cc=parisc-linux@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.