On Mon, 2009-10-12 at 15:54 +0200, Fortini Matteo wrote:
> 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.
if you are in that interval you definitely need to go to
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 st
Did you try "setenv bootdelay 0" in uboot?
On Mon, Oct 12, 2009 at 7:07 AM, Fortini Matteo 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 (
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 b
