Re: [PATCH] x86 built-in command line (resend)

Matt Mackall wrote:
On Mon, Jul 31, 2006 at 12:07:02PM -0700, H. Peter Anvin wrote:
Matt Mackall wrote:
I'm resending this as-is because the earlier thread petered out
without any strong arguments against this approach. x86_64 patch to
follow.
"No strong arguments?"

I still maintain that this patch has the wrong priority in case more than one set of arguments are provided.

But you still haven't answered how that lets you work around firmware
that passes parameters you don't like.


That a fairly unique problem, and is most likely in a minority application. For that case a CONFIG option to ignore the firmware-provided command line would make sense. I do not believe it should be the only option or even the default.

It would be particularly good if this could be standardized across architectures, which is another reason to do it right.

-hpa

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: [2.6 patch] dont allow users to set CONFIG_BROKEN=y
    ... the menus to look for something matching your hardware is nice, even if that something is marked BROKEN at least you've then found a place to start working on. ... or do you intend to have a bunch of patches that remove BROKEN for a config option so that people can test them during the -rc and then add it back for them all before a real release? ... nobody will be able to test that patch unless they are willing ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: [PATCH 1/2] Add /sys/firmware/memmap
    ... >> provided memory map. ... > Thanks for the patch. ... > Do we really need another CONFIG option? ...
    (Linux-Kernel)
  • Re: [PATCH] Early boot debugging via FireWire (ohci1394_dma=early)
    ... If the config option is not enabled, no code is changed, and if the ... boot paramenter is not given, no new code is executed, and independent ... information from machines which have no serial ports such ... I've tentatively added your patch to x86.git (pending more ...
    (Linux-Kernel)
  • Re: [PATCH] Debug shared irqs.
    ... but it's the wrong point in the cycle -- we're ... getting ready for Fedora Core 5 at the moment; it's not the time to be ... We can apply the patch... ... a config option -- people aren't forced to turn it on. ...
    (Linux-Kernel)
  • Re: [PATCH] Debug shared irqs.
    ... > getting ready for Fedora Core 5 at the moment; it's not the time to be ... We can apply the patch... ... > a config option -- people aren't forced to turn it on. ... I'm skilled at sending maintainers new bug reports ...
    (Linux-Kernel)