[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [microblaze-uclinux] Ethernet update for David Banas' NuHorizons board project



OK, the attachment _is_ actually attached this time....

--- Steve Sanders <akasanders@yahoo.com> wrote:

> Sure, see attached.
> 
> It's truly hack, though, so standard disclaimers apply.
> 
> You'll likely need to have a datasheet w/Ethernet PHY register
> descriptions handy, but they are standardized registers.  And I do
> use
> the Linux-approved #defines to identify the registers to read/write,
> so
> it shouldn't be too bad.
> 
> MII_ADVERTISE: set bits 5, 6; clear 7, 8, 9.
> MII_BMSR: set 3, 12; clear 13, 14, 15
> MII_BMCR: set 9, 12
> 
> Bascially tells the PHY that it is only capable of 10Mbps and then
> forces a re-negotation to occur.  I should probably wait for the
> negotation to complete before proceeding, but ... that would be a
> very
> un-hacky thing to do.
> 
> Steve
> 
> --- David Banas <dbanas@nuhorizons.com> wrote:
> 
> > Steve,
> > 
> > Could you post your hack, please?
> > 
> > Thanks,
> > 
> > David Banas
> > Field Applications Engineer
> > Nu Horizons Electronics Corp.
> > 2070 Ringwood Avenue
> > San Jose, CA 95131
> > (408)434-0800 - office
> > (415)846-5837 - cell
> > http://www.nuhorizons.com
> > 
> > > -----Original Message-----
> > > From: owner-microblaze-uclinux@itee.uq.edu.au
> > [mailto:owner-microblaze-
> > > uclinux@itee.uq.edu.au] On Behalf Of Steve Sanders
> > > Sent: Thursday, March 24, 2005 9:25 AM
> > > To: microblaze-uclinux@itee.uq.edu.au
> > > Subject: Re: [microblaze-uclinux] Ethernet update for David
> Banas'
> > > NuHorizons board project
> > >
> > > FYI - I'm working on a board that's using a 44MHz system clock
> and
> > > Ethernet is working at 10Mbps.  To get it working ... I hacked up
> > the
> > > Ethernet driver to force 10Mbps-only mode and then triggered a
> > > re-negotiation with its link partner.  Worked OK after that.
> > >
> > > Also had some problems with it auto-detecting the PHY address
> > properly.
> > >   Sometimes would detect the PHY at 0x1, 0x2, or 0x3.  Hard-coded
> > the
> > > address with the appropriate value for my board (0x3)
> > >
> > > Steve
> > >

Attachment: adapter.c.diff.out
Description: adapter.c.diff.out