[U-Boot-Users] [DNX#2007012342000033] [PATCH 1/2] Add support for 802.3ae [...]

[OTRS Notification Master]

Hello list,

inside the automatic U-Boot patch tracking system a new ticket
[DNX#2007012342000033] was created:

<snip>
> On 1/22/07, Ben Warren <bwarren at qstreams.com> wrote:
> > Hello,
> >
> > This patch adds 'IEEE 802.3ae clause 25' capabilities to the MIIPHY
> > driver, which is needed for communicating with some 10GbE PHYs.  There
> > are two main differences between this and the standard 802.3 PHY
> > framing:
> >
> > 1.      802.3ae devices use a start bit sequence of '00' instead of '01'
> > 2.      Register addressing is indirect.  Read and write requests must be
> > preceded by an 'address' write, which sets page and offset.  The 'read'
> > opcode is now auto-incrementing.  A new 'fixed read' opcode is used for
> > successive reads of a single address.
> 
> > +       } else if (op == 'R') {
> > +               if (miiphy_read_fixed (devname, addr, reg, &data) != 0) {
> > +                       puts ("Error reading from the PHY\n");
> > +                       rcode = 1;
> > +               } else {
> > +                       printf ("%04X\n", data & 0x0000FFFF);
> > +               }
> 
> > +       "device                      - list available devices\n"
> > +       "mii device  <devname>           - set current device\n"
> > +       "mii info    <addr>              - display MII PHY info\n"
> > +       "mii read    <addr> <reg>        - read  MII PHY register\n"
> > +       "mii write   <addr> <reg> <data> - write MII PHY register\n"
> > +       "mii Read    <addr>              - read  MII PHY (fixed-address)\n"
> > +       "mii address <addr> <page> <reg> - set   MII PHY page and offset\n"
> 
> IMHO it's not a good idea to have 'Read' and 'read' do something
> different.  How about 'fread' instead.
> 
> -- 
> Hardware, n.:
>         The parts of a computer system that can be kicked.
</snip>

Your U-Boot support team