On 14:52 Tue 05 May , Sanjeev Premi wrote:
> The current configuration doesn't define default
> bootfile; leading to this warning at execution:
>
> OMAP3_EVM # dhcp
> ...
> ...
> DHCP client bound to address 192.168.1.11
> *** Warning: no boot file name; using 'AC18BE16.img'
> TFTP from server
On 14:52 Tue 05 May , Sanjeev Premi wrote:
> The current configuration doesn't define default
> bootfile; leading to this warning at execution:
>
> OMAP3_EVM # dhcp
> ...
> ...
> DHCP client bound to address 192.168.1.11
> *** Warning: no boot file name; using 'AC18BE16.img'
> TFTP from server
Sanjeev Premi wrote:
> The current configuration doesn't define default
> bootfile; leading to this warning at execution:
>
> OMAP3_EVM # dhcp
> ...
> ...
> DHCP client bound to address 192.168.1.11
> *** Warning: no boot file name; using 'AC18BE16.img'
> TFTP from server 0.0.0.0; our IP address i
> -Original Message-
> From: Wolfgang Denk [mailto:w...@denx.de]
> Sent: Tuesday, May 05, 2009 3:51 PM
> To: Premi, Sanjeev
> Cc: u-boot@lists.denx.de; Pillai, Manikandan
> Subject: Re: [U-Boot] [PATCH] OMAP3EVM: Set default bootfile
>
> Dear Sanjeev Premi,
>
> -Original Message-
> From: Wolfgang Denk [mailto:w...@denx.de]
> Sent: Tuesday, May 05, 2009 3:51 PM
> To: Premi, Sanjeev
> Cc: u-boot@lists.denx.de; Pillai, Manikandan
> Subject: Re: [U-Boot] [PATCH] OMAP3EVM: Set default bootfile
>
> Dear Sanjeev Premi,
>
Dear Sanjeev Premi,
In message <1241515371-24359-1-git-send-email-pr...@ti.com> you wrote:
> The current configuration doesn't define default
> bootfile; leading to this warning at execution:
Note that this is not a problem, but a decision of the board
maintainer.
Also, you can always just use s
The current configuration doesn't define default
bootfile; leading to this warning at execution:
OMAP3_EVM # dhcp
...
...
DHCP client bound to address 192.168.1.11
*** Warning: no boot file name; using 'AC18BE16.img'
TFTP from server 0.0.0.0; our IP address is 192.168.1.11;
sending through gateway
7 matches
Mail list logo