From: Takashi Iwai <tiwai@suse.de>
To: Pavel Machek <pavel@suse.cz>
Cc: perex@suse.cz, Tjeerd.Mulder@fujitsu-siemens.com,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: via82xx cmd line parsing is evil [was Re: Sound on newer arima notebook...]
Date: Thu, 01 Apr 2004 10:37:55 +0200 [thread overview]
Message-ID: <s5hptasw0t8.wl@alsa2.suse.de> (raw)
In-Reply-To: <20040401082905.GE224@elf.ucw.cz>
At Thu, 1 Apr 2004 10:29:05 +0200,
Pavel Machek wrote:
>
> Hi!
>
> > > via82xx command line parsing code is *evil*. It has completely
> > > different parameters as a module / in kernel, and in-kernel parameters
> > > shift according to the joystick support! (which is config_time option). Ouch.
> >
> > yep, i know it - it annoys me too...
> >
> > > Is there some easy way to convert MODULE_PARM with an array to some
> > > more modern interface?
> >
> > there is a patch pending in my tree to allow empty boot options, such
> > as
> > snd-via82xx=,,,,,2
> > but it doesn't improve so much.
> >
> > perhaps the better way would be like
> >
> > snd-via82xx=enable:1,ac97_quirk:4
> >
> > ??
> >
> > in this way, it's hard to keep the compatibility with old boot
> > parameters, but i don't think no one will complain if they see it
> > nicer.
>
> Its so broken that we do not want compatibility, I believe. Having to
> use snd-via82xx=,,,,,2 normally, but add one "," if joystick is
> configured in is evil.
>
> snd-via82xx=enable:1 syntax is ugly, too, and we have better syntax
> already. via82xx.enable=1 via82xx.ac97_quirk=2 should be possible with
> new param handling code.
oh that's good to know.
> I'm just not sure how it is supposed to work
> with arrays:
>
> static char *psmouse_proto;
> static unsigned int psmouse_max_proto = -1U;
> module_param_named(proto, psmouse_proto, charp, 0);
> MODULE_PARM_DESC(proto, "Highest protocol extension to probe (bare,
> imps, exps). Useful for KVM switches.");
>
> ...automatically produces "proto" param for module and "psmouse.proto"
> param for kernel.
>
> Something similar should be the way to go.
ok, i'll take a look at it.
thanks!
Takashi
next prev parent reply other threads:[~2004-04-01 8:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 14:52 Sound on newer arima notebook Pavel Machek
2004-03-31 15:08 ` Takashi Iwai
2004-04-01 8:09 ` via82xx cmd line parsing is evil [was Re: Sound on newer arima notebook...] Pavel Machek
2004-04-01 8:23 ` Takashi Iwai
2004-04-01 8:29 ` Pavel Machek
2004-04-01 8:37 ` Takashi Iwai [this message]
2004-04-01 9:04 ` Takashi Iwai
2004-04-01 9:04 ` Pavel Machek
2004-04-01 9:15 ` Takashi Iwai
2004-04-01 10:41 ` Pavel Machek
2004-04-01 18:24 ` Pavel Machek
2004-04-01 18:28 ` Takashi Iwai
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=s5hptasw0t8.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=Tjeerd.Mulder@fujitsu-siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=perex@suse.cz \
/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.