Am Donnerstag, den 12.01.2012, 11:53 +0100 schrieb Michal Simek:
> Wolfgang Denk wrote:
> > Dear Stephan Linz,
> >
> > >> But what would be the best implementation for unspecified targets here?
> >
> > The question is actually a very simple one here: is there any board
> > configuration in mainl
Wolfgang Denk wrote:
Dear Stephan Linz,
In message <1325956366.18981.47.camel@keto> you wrote:
I'll provide the same way for the Xilinx LL_TEMAC driver as for the
Xilinx AXI-EMAC driver. I prepare the microblaze-generic board code to
support all potential Ethernet drivers but leave out the spec
Dear Stephan Linz,
In message <1325956366.18981.47.camel@keto> you wrote:
>
> I'll provide the same way for the Xilinx LL_TEMAC driver as for the
> Xilinx AXI-EMAC driver. I prepare the microblaze-generic board code to
> support all potential Ethernet drivers but leave out the specific usage.
> Yo
Stephan Linz wrote:
Am Donnerstag, den 05.01.2012, 20:19 +0100 schrieb Wolfgang Denk:
Dear Stephan Linz,
In message <1325783490.7827.45.camel@keto> you wrote:
Michals latest Microblaze platform patches will enable this driver for
board/xilinx/microblaze-generic and we know about a success stor
Am Donnerstag, den 05.01.2012, 20:19 +0100 schrieb Wolfgang Denk:
> Dear Stephan Linz,
>
> In message <1325783490.7827.45.camel@keto> you wrote:
> >
> > Michals latest Microblaze platform patches will enable this driver for
> > board/xilinx/microblaze-generic and we know about a success story on
Dear Stephan Linz,
In message <1325783490.7827.45.camel@keto> you wrote:
>
> Michals latest Microblaze platform patches will enable this driver for
> board/xilinx/microblaze-generic and we know about a success story on a
> propietary Virtex5 FX board (ppc440) -- tested by Ricardo Ribalda.
>
> So
Am Donnerstag, den 05.01.2012, 17:10 +0100 schrieb Wolfgang Denk:
> Dear Michal Simek,
>
> In message <4ef2f20b.6050...@monstr.eu> you wrote:
> >
> > > Are there going to be any users for this code?
> >
> > Sure. This driver lies out of mainline code for quite some times.
> > ll_temac is IP core
Dear Michal Simek,
In message <4ef2f20b.6050...@monstr.eu> you wrote:
>
> > Are there going to be any users for this code?
>
> Sure. This driver lies out of mainline code for quite some times.
> ll_temac is IP core which is used by Microblaze and xilinx ppc.
> There are two options for network IP
On Thu, Dec 1, 2011 at 2:39 PM, Stephan Linz wrote:
> +static int phywrite(struct eth_device *dev, u8 phy_addr,
> + u8 reg_addr, u16 phy_data)
> +{
> + struct temac_reg *regs = (struct temac_reg *)dev->iobase;
> +
> + out_be32(®s->lsw, (phy_data &
Wolfgang Denk wrote:
Dear Stephan Linz,
In message <1322771978-22008-2-git-send-email-l...@li-pro.net> you wrote:
Xilinx LocalLink Tri-Mode Ether MAC driver can be
used by Xilinx Microblaze or Xilinx ppc405/440 in
SDMA and FIFO mode. DCR or XPS bus can be used.
The driver uses and requires MII
Am Dienstag, den 20.12.2011, 23:56 +0100 schrieb Wolfgang Denk:
> Dear Stephan Linz,
Hello Wolfgang,
>
> In message <1322771978-22008-2-git-send-email-l...@li-pro.net> you wrote:
> > Xilinx LocalLink Tri-Mode Ether MAC driver can be
> > used by Xilinx Microblaze or Xilinx ppc405/440 in
> > SDMA
Dear Stephan Linz,
In message <1322771978-22008-2-git-send-email-l...@li-pro.net> you wrote:
> Xilinx LocalLink Tri-Mode Ether MAC driver can be
> used by Xilinx Microblaze or Xilinx ppc405/440 in
> SDMA and FIFO mode. DCR or XPS bus can be used.
>
> The driver uses and requires MII and PHYLIB.
>
Xilinx LocalLink Tri-Mode Ether MAC driver can be
used by Xilinx Microblaze or Xilinx ppc405/440 in
SDMA and FIFO mode. DCR or XPS bus can be used.
The driver uses and requires MII and PHYLIB.
CP: 4 warnings: 'Use of volatile is usually wrong'
I won't fix this, because it depends on the network
d
13 matches
Mail list logo
