From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] x86: x86-common.h: Add CONFIG_BOOTDELAY
Date: Thu, 21 Jan 2016 07:06:04 +0100 [thread overview]
Message-ID: <56A0754C.4030105@denx.de> (raw)
In-Reply-To: <20160119172553.GK3359@bill-the-cat>
Hi Tom,
On 19.01.2016 18:25, Tom Rini wrote:
> On Mon, Jan 18, 2016 at 02:49:56PM +0100, Stefan Roese wrote:
>
>> Without this CONFIG_BOOTDELAY, autobooting does not work at all. As
>> autoboot_command() from common/* will not get called. So lets define
>> CONFIG_BOOTDELAY, so that auto-booting works on x86.
>>
>> Signed-off-by: Stefan Roese <sr@denx.de>
>> Cc: Miao Yan <yanmiaobest@gmail.com>
>> Cc: Bin Meng <bmeng.cn@gmail.com>
>> Cc: Simon Glass <sjg@chromium.org>
>
> I think the right direction (and I haven't had time myself) is to make
> x86 use the generic distro framework. Dennis Gilmore pointed out a
> while ago Fedora at least can be easily made to generate the extlinux
> file on x86 even so it'll just work there :)
Yes, this is definitely the "right direction". Unfortunately I'm a bit
limited with the time I could spend on this. And frankly, I have not
much experience with the generic distro framework. So I would like
to postpone this distro rework for a bit now. And since x86 does not
support auto-booting at all without CONFIG_BOOTDELAY, I think it
makes sense to apply this patch now. And add the distro stuff a
bit later.
Thanks,
Stefan
prev parent reply other threads:[~2016-01-21 6:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 13:49 [U-Boot] [PATCH 1/2] x86: x86-common.h: Add CONFIG_BOOTDELAY Stefan Roese
2016-01-18 13:49 ` [U-Boot] [PATCH 2/2] x86: x86-common.h: Add generic FS commands Stefan Roese
2016-01-19 6:19 ` Bin Meng
2016-01-26 6:48 ` Bin Meng
2016-01-19 5:20 ` [U-Boot] [PATCH 1/2] x86: x86-common.h: Add CONFIG_BOOTDELAY Miao Yan
2016-01-19 6:19 ` Bin Meng
2016-01-26 6:48 ` Bin Meng
2016-01-28 15:04 ` Stefan Roese
2016-01-28 16:13 ` Stefan Roese
2016-01-28 16:16 ` Simon Glass
2016-01-28 16:18 ` Stefan Roese
2016-01-29 8:43 ` Bin Meng
2016-01-19 17:25 ` Tom Rini
2016-01-21 6:06 ` Stefan Roese [this message]
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=56A0754C.4030105@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/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