1. 19 3月, 2009 6 次提交
  2. 18 3月, 2009 10 次提交
  3. 17 3月, 2009 3 次提交
  4. 16 3月, 2009 5 次提交
  5. 15 3月, 2009 2 次提交
  6. 14 3月, 2009 1 次提交
  7. 13 3月, 2009 2 次提交
  8. 12 3月, 2009 8 次提交
  9. 11 3月, 2009 2 次提交
  10. 10 3月, 2009 1 次提交
    • P
      tsec: report when there is no vendor specific PHY support · 0452352d
      Paul Gortmaker 提交于
      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: NPaul Gortmaker <paul.gortmaker@windriver.com>
      Acked-by: NAndy Fleming <afleming@freescale.com>
      0452352d