From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jeff Dike <jdike@addtoit.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Roman Zippel <zippel@linux-m68k.org>,
jdike@karaya.com, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Russell King <rmk@arm.linux.org.uk>
Subject: Re: uninline check_signature()
Date: Tue, 17 Jul 2007 22:31:08 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707172225260.23024@anakin> (raw)
In-Reply-To: <alpine.LFD.0.999.0707171102040.19166@woody.linux-foundation.org>
On Tue, 17 Jul 2007, Linus Torvalds wrote:
> On Tue, 17 Jul 2007, Geert Uytterhoeven wrote:
> > M68k uses I/O memory for all I/O (hence it sets CONFIG_HAS_IOMEM), but
> > many m68k machines don't have PCI or ISA (hence it doesn't set
> > CONFIG_PCI resp. CONFIG_ISA).
>
> It doesn't matter whether the machine has PCI or ISA. The only thing that
> matters is whether the thing compiles (which in turn depends on whether it
> has "readb()", which in turn is what HAS_IOMEM is all about).
>
> So I do think that HAS_IOMEM is the right thing here.
Good, I guess then either I'll have to do something similar to what ARM does:
| #elif !defined(readb)
|
| #define readb(c) (__readwrite_bug("readb"),0)
| #define readw(c) (__readwrite_bug("readw"),0)
| #define readl(c) (__readwrite_bug("readl"),0)
| #define writeb(v,c) __readwrite_bug("writeb")
| #define writew(v,c) __readwrite_bug("writew")
| #define writel(v,c) __readwrite_bug("writel")
|
| #define check_signature(io,sig,len) (0)
|
| #endif /* __mem_pci */
(but use the real BUG() instead, I don't think the above will still
compile now check_signature() is out-of-line)
And we'll all live with a check_signature() in our kernel, which is used
only by a few legacy drivers that depend on ISA || PCI...
OR I'll have to disable HAS_IOMEM on m68k, and invent a new Kconfig
symbol for lots of other stuff that currently depends on HAS_IOMEM...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2007-07-17 20:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200707161802.l6GI2tNp007390@hera.kernel.org>
2007-07-16 22:12 ` Heiko Carstens
2007-07-16 22:29 ` Andrew Morton
2007-07-16 22:35 ` Linus Torvalds
2007-07-16 23:03 ` Heiko Carstens
2007-07-17 13:22 ` Geert Uytterhoeven
2007-07-17 16:33 ` Jeff Dike
2007-07-17 16:46 ` Geert Uytterhoeven
2007-07-17 18:03 ` Linus Torvalds
2007-07-17 20:31 ` Geert Uytterhoeven [this message]
2007-07-17 20:38 ` Al Viro
2007-07-17 20:40 ` Linus Torvalds
2007-07-18 6:45 ` Geert Uytterhoeven
2007-08-12 10:24 ` [PATCH] Introduce CONFIG_CHECK_SIGNATURE (was: Re: uninline check_signature()) Geert Uytterhoeven
2007-07-17 8:50 ` uninline check_signature() Geert Uytterhoeven
2007-07-17 8:53 ` Geert Uytterhoeven
2007-07-18 11:33 ` Maciej W. Rozycki
2007-07-17 8:59 ` Pekka Enberg
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=Pine.LNX.4.64.0707172225260.23024@anakin \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=heiko.carstens@de.ibm.com \
--cc=jdike@addtoit.com \
--cc=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=schwidefsky@de.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®