summaryrefslogtreecommitdiff
path: root/board/rpxsuper
diff options
context:
space:
mode:
authorPaul Gortmaker <paul.gortmaker@windriver.com>2009-03-09 18:07:53 -0500
committerAndy Fleming <afleming@freescale.com>2009-03-09 18:08:04 -0500
commit0452352df118bc9dd684a056aaaa5fb4aed1178a (patch)
tree0b9b2eab86938ed1b961f984d18f57bd6b74b066 /board/rpxsuper
parent49b5aff491bd574935ecaf8545152066a25eff3d (diff)
downloadu-boot-imx-0452352df118bc9dd684a056aaaa5fb4aed1178a.zip
u-boot-imx-0452352df118bc9dd684a056aaaa5fb4aed1178a.tar.gz
u-boot-imx-0452352df118bc9dd684a056aaaa5fb4aed1178a.tar.bz2
tsec: report when there is no vendor specific PHY support
Commit af1c2b84 added a generic phy support, with an ID of zero and a 32 bit mask; meaning that it will match on any PHY ID. The problem is that there is a test that checked if a matching PHY was found, and if not, it printed the non-matching ID. But since there will always be a match (on the generic PHY, worst case), this test will never trip. In the case of a misconfigured PHY address, or of a PHY that isn't explicitly supported outside of the generic support, you will never see the ID of 0xffffffff, or the ID of the real (but unsupported) chip. It will silently fall through onto the generic support. This change makes that test useful again, and ensures that the selection of generic PHY support doesn't happen without some sort of notice. It also makes it explicitly clear that the generic PHY must be last in the PHY table. Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Acked-by: Andy Fleming <afleming@freescale.com>
Diffstat (limited to 'board/rpxsuper')
0 files changed, 0 insertions, 0 deletions