From: Sergej Pupykin <ml@sergej.pp.ru>
To: Sergej Pupykin <ml@sergej.pp.ru>,
Jesse Barnes <jbarnes@virtuousgeek.org>, Greg KH <greg@kroah.com>,
dri-devel@lists.freedesktop.org, stable@kernel.org
Subject: Re: [stable] [PATCH] drm/kms: remove spaces from connector names
Date: Mon, 13 Dec 2010 13:43:48 +0300 [thread overview]
Message-ID: <877hfevtp7.wl%sergej.pupykin@dsr-company.com> (raw)
In-Reply-To: <20101210180513.28235.qmail@stuge.se>
At Fri, 10 Dec 2010 19:05:13 +0100,
Peter Stuge <peter@stuge.se> wrote:
> append can contain any arbitrary string, which will be parsed by the
> kernel. I e.g. use:
>
> append="root=/dev/sda2 snd_ac97_codec.power_save=1 usbcore.autosuspend=1 hpet=force quiet drm_kms_helper.poll=0"
>
> And grub also supports an append string with spaces, that is probably
> used by every distribution.
>
> The question is, what will the kernel parser do about that space?
It seems lilo also have no support for such parameters.
append="video=9-pin DIN:1024x768-24@60e"
does not work (kernel panic: DIN: bad variable name)
As I understand, I should pass somehow to kernel string like:
video="9-pin DIN:1024x768-24@60e", but lilo uses doublequotes as
r-value bounds.
in_quote variable in next_arg() is set only for " character.
next prev parent reply other threads:[~2010-12-13 10:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 23:14 [PATCH] drm/kms: remove spaces from connector names Alex Deucher
2010-12-08 23:30 ` [stable] " Greg KH
2010-12-08 23:32 ` Dave Airlie
2010-12-09 17:18 ` Jesse Barnes
2010-12-09 17:33 ` Sergej Pupykin
2010-12-09 17:46 ` Jesse Barnes
2010-12-09 22:15 ` [stable] " Peter Stuge
2010-12-10 12:24 ` Sergej Pupykin
2010-12-10 18:05 ` Peter Stuge
2010-12-13 10:43 ` Sergej Pupykin [this message]
2010-12-13 11:31 ` [stable] " Sergej Pupykin
2010-12-09 0:01 ` Dave Airlie
2010-12-09 0:04 ` Alex Deucher
2010-12-09 0:09 ` [PATCH] drm/kms: remove spaces from connector names (v2) Alex Deucher
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=877hfevtp7.wl%sergej.pupykin@dsr-company.com \
--to=ml@sergej.pp.ru \
--cc=dri-devel@lists.freedesktop.org \
--cc=greg@kroah.com \
--cc=jbarnes@virtuousgeek.org \
--cc=stable@kernel.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.