From: Fortini Matteo <matteo.fortini@mta.it>
To: Roberto Guerra <roberto.j.guerra@gmail.com>
Cc: "u-boot@lists.denx.de" <u-boot@lists.denx.de>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Linux seamless booting
Date: Mon, 12 Oct 2009 15:54:59 +0200 [thread overview]
Message-ID: <4AD33533.5030900@mta.it> (raw)
In-Reply-To: <7c4144600910120623k2c9aea89ia0f255164f03ff89@mail.gmail.com>
Yes, that's what we're currently using, but the problem is a little
broader: I should answer to CAN messages in at most 100-200ms from
powerup, and that can be done in u-boot.
However, handing CAN transmission control over to Linux is quite
complicated nowadays, since it would involve passing structures in
memory and hacking through device init.
It'd be nice to have a framework with which u-boot could hand-over
devices to Linux in a clean and defined way.
We were thinking about starting some kind of development in that
direction, but with very little resources, so I was looking for someone
who had looked at the same problem.
Thanks,
Matteo
Roberto Guerra ha scritto:
> Did you try "setenv bootdelay 0" in uboot?
>
> On Mon, Oct 12, 2009 at 7:07 AM, Fortini Matteo <matteo.fortini@mta.it> wrote:
>
>> Hi all,
>> we've been working on a PPC512x board booting with u-boot + linux 2.6.24.6,
>> and one major issue for our application is boot time.
>>
>> Right now, we went down to less than 6s boot time (i.e. time from power off
>> to launch of the user app), even with some drivers installed, i.e.:
>>
>> * CAN bus
>> * GPU on PCI bus
>> * USB host
>> * UBI
>>
>> with r/o squashfs root and r/w ubifs configuration filesystem mounted from a
>> NOR flash memory.
>>
>> This time could be enough for the high-level application (we're showing a
>> splash screen in about 2-3s so it's ok if the main app takes a little longer
>> to come up), but the whole system is connected to others via CAN and we
>> can't afford the "black out" period between u-boot and linux.
>>
>> Some other operating systems (e.g. QNX) have this "seamless booting"
>> function, in which drivers are started in stages, so that a (minimal)
>> functionality can be given in milliseconds, and more functionalities come up
>> as time goes by.
>>
>> Is there a way to support something similar with the u-boot -> linux
>> solution?
>>
>> Thank you,
>> Matteo
>> _______________________________________________
>> Linuxppc-dev mailing list
>> Linuxppc-dev@lists.ozlabs.org
>> https://lists.ozlabs.org/listinfo/linuxppc-dev
>>
>>
> .
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Fortini Matteo <matteo.fortini@mta.it>
To: u-boot@lists.denx.de
Subject: [U-Boot] Linux seamless booting
Date: Mon, 12 Oct 2009 15:54:59 +0200 [thread overview]
Message-ID: <4AD33533.5030900@mta.it> (raw)
In-Reply-To: <7c4144600910120623k2c9aea89ia0f255164f03ff89@mail.gmail.com>
Yes, that's what we're currently using, but the problem is a little
broader: I should answer to CAN messages in at most 100-200ms from
powerup, and that can be done in u-boot.
However, handing CAN transmission control over to Linux is quite
complicated nowadays, since it would involve passing structures in
memory and hacking through device init.
It'd be nice to have a framework with which u-boot could hand-over
devices to Linux in a clean and defined way.
We were thinking about starting some kind of development in that
direction, but with very little resources, so I was looking for someone
who had looked at the same problem.
Thanks,
Matteo
Roberto Guerra ha scritto:
> Did you try "setenv bootdelay 0" in uboot?
>
> On Mon, Oct 12, 2009 at 7:07 AM, Fortini Matteo <matteo.fortini@mta.it> wrote:
>
>> Hi all,
>> we've been working on a PPC512x board booting with u-boot + linux 2.6.24.6,
>> and one major issue for our application is boot time.
>>
>> Right now, we went down to less than 6s boot time (i.e. time from power off
>> to launch of the user app), even with some drivers installed, i.e.:
>>
>> * CAN bus
>> * GPU on PCI bus
>> * USB host
>> * UBI
>>
>> with r/o squashfs root and r/w ubifs configuration filesystem mounted from a
>> NOR flash memory.
>>
>> This time could be enough for the high-level application (we're showing a
>> splash screen in about 2-3s so it's ok if the main app takes a little longer
>> to come up), but the whole system is connected to others via CAN and we
>> can't afford the "black out" period between u-boot and linux.
>>
>> Some other operating systems (e.g. QNX) have this "seamless booting"
>> function, in which drivers are started in stages, so that a (minimal)
>> functionality can be given in milliseconds, and more functionalities come up
>> as time goes by.
>>
>> Is there a way to support something similar with the u-boot -> linux
>> solution?
>>
>> Thank you,
>> Matteo
>> _______________________________________________
>> Linuxppc-dev mailing list
>> Linuxppc-dev at lists.ozlabs.org
>> https://lists.ozlabs.org/listinfo/linuxppc-dev
>>
>>
> .
>
>
next prev parent reply other threads:[~2009-10-12 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 11:07 Linux seamless booting Fortini Matteo
2009-10-12 11:07 ` [U-Boot] " Fortini Matteo
2009-10-12 13:23 ` Roberto Guerra
2009-10-12 13:23 ` [U-Boot] " Roberto Guerra
2009-10-12 13:54 ` Fortini Matteo [this message]
2009-10-12 13:54 ` Fortini Matteo
2009-10-13 12:22 ` Kenneth Johansson
2009-10-13 12:22 ` Kenneth Johansson
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=4AD33533.5030900@mta.it \
--to=matteo.fortini@mta.it \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=roberto.j.guerra@gmail.com \
--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 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.