From: Jan Kiszka <jan.kiszka@domain.hid>
To: Wolfgang Grandegger <wg@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Problems with compat_module_param_array() with Linux 2.4
Date: Wed, 18 Jul 2007 21:00:25 +0200 [thread overview]
Message-ID: <469E6349.5000209@domain.hid> (raw)
In-Reply-To: <469E10D5.8000602@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
Wolfgang Grandegger wrote:
> Hello,
>
> yesterday I realized a problem with compat_module_param_array() with
> ksrc/drivers/can/sja1000/rtcan_mem.c under Linux 2.4. It uses
> CONFIG_XENO_DRIVERS_CAN_SJA1000_MEM_MAX_DEV to define the number of mem
> devices, which is set to '(4)' by "make [menuc]onfig". Unfortunately,
> the brackets '()' break compat_module_param_array() because it treats
> the count as string:
>
> #define compat_module_param_array(name, type, count, perm) \
> static inline void *__check_existence_##name(void) { return
> &name; } \
> MODULE_PARM(name, "1-" __MODULE_STRING(count)
> _MODULE_PARM_STRING_##type)
>
> Any idea how to fix that? I actually tend to remove the configuration
> option CONFIG_XENO_DRIVERS_CAN_SJA1000_MEM_MAX_DEV and hardcode it to
> "4" (without brackets) in the driver. It's kind of overkill, anyhow.
I would say that this problem is not "with compat_module_param_array",
but about the Kconfig-based constant. I don't see a way to make the
module parameter array size configurable even under vanilla 2.4. Simply
go for a patchable constant in the source code like other drivers do.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-07-18 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 13:08 [Xenomai-core] Problems with compat_module_param_array() with Linux 2.4 Wolfgang Grandegger
2007-07-18 19:00 ` Jan Kiszka [this message]
2007-08-15 16:15 ` Wolfgang Grandegger
2007-08-15 17:14 ` Jan Kiszka
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=469E6349.5000209@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=wg@domain.hid \
--cc=xenomai@xenomai.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.