* [U-Boot] Q on expected u-boot behavior on ping response
@ 2016-08-30 10:19 John Rama
2016-09-01 1:42 ` Chris Packham
0 siblings, 1 reply; 4+ messages in thread
From: John Rama @ 2016-08-30 10:19 UTC (permalink / raw)
To: u-boot
Dear u-boot network experts,
I'm now working on NXP MX6Q Sabreauto board with AR8031 network card.
I'm using rel_imx_4.1.15_1.2.0_ga.
Basically, the network works fine. u-boot can send ping to other device, do the tftp boot as well.
But, I just realized that u-boot never respond on ping command from external device.
Only the exception is that while u-boot is trying to communicate to other device via network
(sending a ping command to others, or doing tftp boot, etc)
I'm not dug into detail yet.
But before doing so, I would like to confirm if this is a intentional behavior or not.
I have only tried the MX6Q Sabre auto device, since this is the only device I have now.
Thanks for the feedback.
John
^ permalink raw reply [flat|nested] 4+ messages in thread
* [U-Boot] Q on expected u-boot behavior on ping response
2016-08-30 10:19 [U-Boot] Q on expected u-boot behavior on ping response John Rama
@ 2016-09-01 1:42 ` Chris Packham
2016-09-01 3:25 ` John Rama
0 siblings, 1 reply; 4+ messages in thread
From: Chris Packham @ 2016-09-01 1:42 UTC (permalink / raw)
To: u-boot
On Tue, Aug 30, 2016 at 10:19 PM, John Rama <john.rama01@gmail.com> wrote:
> Dear u-boot network experts,
>
> I'm now working on NXP MX6Q Sabreauto board with AR8031 network card.
> I'm using rel_imx_4.1.15_1.2.0_ga.
>
> Basically, the network works fine. u-boot can send ping to other device, do the tftp boot as well.
>
> But, I just realized that u-boot never respond on ping command from external device.
> Only the exception is that while u-boot is trying to communicate to other device via network
> (sending a ping command to others, or doing tftp boot, etc)
>
> I'm not dug into detail yet.
> But before doing so, I would like to confirm if this is a intentional behavior or not.
Yes this is intentional. u-boot only starts the network driver when it
needs to use it (i.e. to send a ping or download something over tftp).
After it has finished the network driver is stopped. Any traffic on
the network will be ignored if u-boot isn't actively trying to perform
a network operation, even if it is addressed to the device.
> I have only tried the MX6Q Sabre auto device, since this is the only device I have now.
>
> Thanks for the feedback.
>
> John
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
^ permalink raw reply [flat|nested] 4+ messages in thread
* [U-Boot] Q on expected u-boot behavior on ping response
2016-09-01 1:42 ` Chris Packham
@ 2016-09-01 3:25 ` John Rama
0 siblings, 0 replies; 4+ messages in thread
From: John Rama @ 2016-09-01 3:25 UTC (permalink / raw)
To: u-boot
Thanks, Chris !!
Understood.
John
On 2016/09/01 10:42, Chris Packham wrote:
> On Tue, Aug 30, 2016 at 10:19 PM, John Rama <john.rama01@gmail.com> wrote:
>> Dear u-boot network experts,
>>
>> I'm now working on NXP MX6Q Sabreauto board with AR8031 network card.
>> I'm using rel_imx_4.1.15_1.2.0_ga.
>>
>> Basically, the network works fine. u-boot can send ping to other device, do the tftp boot as well.
>>
>> But, I just realized that u-boot never respond on ping command from external device.
>> Only the exception is that while u-boot is trying to communicate to other device via network
>> (sending a ping command to others, or doing tftp boot, etc)
>>
>> I'm not dug into detail yet.
>> But before doing so, I would like to confirm if this is a intentional behavior or not.
>
> Yes this is intentional. u-boot only starts the network driver when it
> needs to use it (i.e. to send a ping or download something over tftp).
> After it has finished the network driver is stopped. Any traffic on
> the network will be ignored if u-boot isn't actively trying to perform
> a network operation, even if it is addressed to the device.
>
>> I have only tried the MX6Q Sabre auto device, since this is the only device I have now.
>>
>> Thanks for the feedback.
>>
>> John
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
^ permalink raw reply [flat|nested] 4+ messages in thread
* [U-Boot] Q on expected u-boot behavior on ping response
@ 2016-08-30 11:39 John Rama
0 siblings, 0 replies; 4+ messages in thread
From: John Rama @ 2016-08-30 11:39 UTC (permalink / raw)
To: u-boot
Dear u-boot network experts,
I'm now working on NXP MX6Q Sabreauto board with AR8031 network card.
I'm using rel_imx_4.1.15_1.2.0_ga.
Basically, the network works fine. u-boot can send ping to other device, do the tftp boot as well.
But, I just realized that u-boot never respond on ping command from external device.
Only the exception is that while u-boot is trying to communicate to other device via network
(sending a ping command to others, or doing tftp boot, etc)
I'm not dug into detail yet.
But before doing so, I would like to confirm if this is a intentional behavior or not.
I have only tried the MX6Q Sabre auto device, since this is the only device I have now.
Thanks for the feedback.
John
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-09-01 3:25 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-08-30 10:19 [U-Boot] Q on expected u-boot behavior on ping response John Rama
2016-09-01 1:42 ` Chris Packham
2016-09-01 3:25 ` John Rama
-- strict thread matches above, loose matches on Subject: below --
2016-08-30 11:39 John Rama
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox