Skip to contentSkip to conversation

Disable features

U-Boot Derek Ou 4 participants 12 messages Apr 30, 2009 – May 1, 2009 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Derek Ou

author
#1 lore raw

Hi,

Quoted 3 lines

Is existing a way to globally disable some features such as ethernet or Nand support, instead of doing it for a specific board?

Other than recompiling, is it possible to disable Ethernet through environment settings? At our
work, we often need Ethernet only during development, manufacturing and troubleshooting. So
we put the Ethernet chip on the test fixture instead of the final board. However, compiling in
Ethernet slow down the booting process. So it will be great if Ethernet can be disabled and
enabled by flipping an environment setting.

Derek

#2 lore raw

Dear Derek Ou,

Quoted 3 lines · In message <[email protected]> you wrote:

Other than recompiling, is it possible to disable Ethernet through environment settings? At our

No.

Quoted 5 lines

work, we often need Ethernet only during development, manufacturing and troubleshooting. So
we put the Ethernet chip on the test fixture instead of the final board. However, compiling in
Ethernet slow down the booting process. So it will be great if Ethernet

Why would compiled in Network support slow down the boot process?

The network interface will only be initialized as soon as you use it. If you don't have one, then you probably will not try using it - then why would it delay your boot?

Quoted 2 lines

can be disabled and
enabled by flipping an environment setting.

This cannot be done in the current code (and it should not be necessary).

Best regards,

Wolfgang Denk

Signature · 5 lines
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"There are things that are so serious that you can  only  joke  about
them"                                                    - Heisenberg
author
#3 lore raw
Quoted 6 lines · Wolfgang Denk

Why would compiled in Network support slow down the boot process?

The network interface will only be initialized as soon as you use it. If you don't have one, then you probably will not try using it - then why would it delay your boot?

When we have the Network support compiled, it takes a few second to do the auto-negotiation
even though MAC chip is not on board. Then it fails out and goes to autoboot. Is it a
board specific problem or system problem?

Thanks,
Derek

#4 lore raw
Quoted 9 lines · Derek Ou
Quoted 7 lines · Wolfgang Denk

Why would compiled in Network support slow down the boot process?

The network interface will only be initialized as soon as you use it. If you don't have one, then you probably will not try using it - then why would it delay your boot?

Quoted 7 lines

When we have the Network support compiled, it takes a few second to do the auto-negotiation
even though MAC chip is not on board. Then it fails out and goes to autoboot. Is it a
board specific problem or system problem?

Which network controller are you using? Autonegotiation shouldn't happen until you use the interface, but not all drivers are written that way.

regards,
Ben

author
#5 lore raw

Hi, Ben,

Quoted 3 lines · Ben Warren

Do you have CONFIG_RESET_PHY_R defined? It forces a call to eth_init(), which most likely causes the delay you're seeing. Try commenting it out in your config file.

Yes, CONFIG_RESET_PHY_R is defined by default. And I can see it linking to the eth_init and then macb_init which results in the auto-negotiation. I am going to
comment it out and test it. But what is the use for this config? Why does ATMEL
define it in many of their boards?

Thanks,
Derek

#6 lore raw
Quoted 6 lines · Derek Ou

Hi, Ben,

Quoted 3 lines · Ben Warren

Do you have CONFIG_RESET_PHY_R defined? It forces a call to eth_init(), which most likely causes the delay you're seeing. Try commenting it out in your config file.

Quoted 8 lines

Yes, CONFIG_RESET_PHY_R is defined by default. And I can see it linking to
the eth_init and then macb_init which results in the auto-negotiation. I am going to
comment it out and test it. But what is the use for this config? Why does ATMEL
define it in many of their boards?

Two good questions. I don't know why, but seem to remember it coming up in this very forum.

Quoted 2 lines

Thanks,
Derek

regards,
Ben

#7 lore raw
In reply to Derek Ou

Dear Derek Ou,

Quoted 7 lines · In message <[email protected]> you wrote:

Yes, CONFIG_RESET_PHY_R is defined by default. And I can see it linking to the eth_init and then macb_init which results in the auto-negotiation. I am going to
comment it out and test it. But what is the use for this config? Why does ATMEL
define it in many of their boards?

It makes no sense to me to reset the PHY when no network command is being used. I imagine this might be a workaround for broken Linux drivers which do not correctly initialize the hardware themself.

I guess Jean-Cristophe knows this better than we. Jean-Cristophe ?

Best regards,

Wolfgang Denk

Signature · 5 lines
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"Just think, with VLSI we can have 100 ENIACS on a chip!"
- Alan Perlis
#8 lore raw
Quoted 11 lines · Wolfgang Denk

Dear Derek Ou,

Quoted 7 lines · In message <[email protected]> you wrote:

Yes, CONFIG_RESET_PHY_R is defined by default. And I can see it linking to the eth_init and then macb_init which results in the auto-negotiation. I am going to
comment it out and test it. But what is the use for this config? Why does ATMEL
define it in many of their boards?

Quoted 3 lines

It makes no sense to me to reset the PHY when no network command is being used. I imagine this might be a workaround for broken Linux drivers which do not correctly initialize the hardware themself.

correct
IIRC if you do not do it the net drivers will have no mac address and you will not be alllow to use nfs as rootfs

Best Regards,
J.

#9 lore raw

Dear Jean-Christophe PLAGNIOL-VILLARD,

Quoted 7 lines · In message <[email protected]> you wrote:
Quoted 4 lines

It makes no sense to me to reset the PHY when no network command is being used. I imagine this might be a workaround for broken Linux drivers which do not correctly initialize the hardware themself.

correct
IIRC if you do not do it the net drivers will have no mac address and you will not be alllow to use nfs as rootfs

That's a bug in the Linux drivers in the first place, and a bug in the ARM Linux kernel's boot interface in the second place.

But then, I also see no correlation between setting a MAC address and waiting for autonegotiation to complte. We should be able to do the former without doing the latter. In any case, the behavious is wrong and should be fixed. See also
http://www.denx.de/wiki/view/DULG/EthernetDoesNotWorkInLinux

Best regards,

Wolfgang Denk

Signature · 5 lines
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The only person who always got his work done by Friday
                                                 was Robinson Crusoe.
#10 lore raw
In reply to Derek Ou

Dear Derek Ou,

Quoted 3 lines · In message <[email protected]> you wrote:

When we have the Network support compiled, it takes a few second to do the auto-negotiation

That should be part of the network init sequence, which should only be run when you run a network command.

Quoted 3 lines

even though MAC chip is not on board. Then it fails out and goes to autoboot. Is it a
board specific problem or system problem?

Board (or architecture) problem.

Which board / architecture is this?

Best regards,

Wolfgang Denk

Signature · 4 lines
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Madness takes its toll. Please have exact change.
author
#11 lore raw
Quoted 10 lines · Wolfgang Denk

Dear Derek Ou,

Quoted 3 lines · In message <[email protected]> you wrote:

When we have the Network support compiled, it takes a few second to do the auto-negotiation

That should be part of the network init sequence, which should only be run when you run a network command.

The board goes to auto-negotiation before boot delay count down. So it's before I can run
any command. I will look into the network init routine then.

Quoted 6 lines
Quoted 3 lines

even though MAC chip is not on board. Then it fails out and goes to autoboot. Is it a board specific problem or system problem?

Board (or architecture) problem.
Which board / architecture is this?

It's an Atmel AT91SAM9263(ek) board. ARM architecture.

Quoted 3 lines

Best regards,
Wolfgang Denk

Derek

#12 lore raw
Quoted 23 lines · Derek Ou
Quoted 5 lines · Wolfgang Denk

Dear Derek Ou,

In message <[email protected]> you wrote:

Quoted 8 lines
Quoted 4 lines

When we have the Network support compiled, it takes a few second to do the auto-negotiation

That should be part of the network init sequence, which should only be run when you run a network command.

The board goes to auto-negotiation before boot delay count down. So it's before I can run
any command. I will look into the network init routine then.

Quoted 4 lines
Quoted 4 lines

even though MAC chip is not on board. Then it fails out and goes to autoboot. Is it a board specific problem or system problem?

Quoted 10 lines
Quoted 4 lines

Board (or architecture) problem.
Which board / architecture is this?

It's an Atmel AT91SAM9263(ek) board. ARM architecture.

Quoted 4 lines

Best regards,
Wolfgang Denk

Do you have CONFIG_RESET_PHY_R defined? It forces a call to eth_init(), which most likely causes the delay you're seeing. Try commenting it out in your config file.

regards,
Ben