From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from outbound5-fra-R.bigfish.com (outbound-fra.frontbridge.com [62.209.45.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.bigfish.com", Issuer "*.bigfish.com" (not verified)) by ozlabs.org (Postfix) with ESMTP id 5ADBEDDE2E for ; Fri, 20 Jul 2007 01:02:53 +1000 (EST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C7CA15.9F3FE513" Subject: RE: ML403 Hard TEMAC, PLB and Linux 2.6 Date: Thu, 19 Jul 2007 09:00:33 -0600 In-Reply-To: From: "Rick Moleres" To: Message-Id: <20070719150106.669DC6805D@mail55-fra.bigfish.com> Cc: mamsadegh@hotmail.com, linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C7CA15.9F3FE513 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Hi, =20 The first thing I would try is to make sure eth1 comes up without first = bringing up eth0. In other words, does it come up independently? If = not, there could be something wrong with its configuration in the kernel = or perhaps a hardware design issue. If both interfaces come up = independently, but not together, then there=A1=AFs likely a driver issue = as we have not tested dual channel TEMAC with the Linux plb_temac = driver. Perhaps others on the list have. The areas that I would look = at would be: make sure each interface is getting a unique and correct = PHY address; make sure any calls to the shared registers of the two = channels are protected with semaphores/spinlocks. For example, I=A1=AFm = pretty sure the PHY registers are shared, so any PHY accesses should be = protected. I would think other Xilinx driver accesses like = Start/Stop/Reset/Get or SetOptions/etc=A1=AD should be protected as they = may access shared registers. =20 -Rick =20 ________________________________ From: Massimiliano.Patriarca@eurotel.it = [mailto:Massimiliano.Patriarca@eurotel.it] On Behalf Of = linux-ppc@eurotel.it Sent: Thursday, July 19, 2007 7:51 AM To: Rick Moleres Cc: Ming Liu; linuxppc-embedded@ozlabs.org; = linuxppc-embedded-bounces+linux-ppc=3Deurotel.it@ozlabs.org; = mamsadegh@hotmail.com Subject: RE: ML403 Hard TEMAC, PLB and Linux 2.6 =20 Hi, we are trying to use both side of an hard temac + 2 plb temac in a = Virtex4FX12 project.=20 we succesfull implemented a single temac Montavista tree with eth0.=20 when trying to use both temac, devices are correctly registered with = kernel-=20 eth0 comes up and working ok-=20 when manually start eth1 (/sbin/ifconfig eth1 up) kernel hang without = any error or info in the console=20 # dmesg=20 Linux version 2.6.10_mvl401-ml40x (massimiliano@linux-yhbz) (gcc version = 3.4.3 (MontaVista 3.4.3-25.0.135.0702900 2007-04-01)) #250 Wed Jul 18 = 12:20:43 CEST 2007=20 Eurotel motherboard init=20 Port by MontaVista Software, Inc. (source@mvista.com)=20 On node 0 totalpages: 7812=20 DMA zone: 7812 pages, LIFO batch:1=20 Normal zone: 0 pages, LIFO batch:1=20 HighMem zone: 0 pages, LIFO batch:1=20 Built 1 zonelists=20 Kernel command line: console=3Dttl0 root=3D/dev/xsysace2 rw ip=3Doff=20 Xilinx INTC #0 at 0x41200000 mapped to 0xFDFFF000=20 PID hash table entries: 128 (order: 7, 2048 bytes)=20 hr_time_init: arch_to_nsec =3D 8192000, nsec_to_arch =3D 1099511627=20 Console: colour dummy device 80x25=20 Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)=20 Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)=20 Memory: 28420k available (1864k kernel code, 528k data, 124k init, 0k = highmem)=20 Calibrating delay loop... 252.92 BogoMIPS (lpj=3D126464)=20 Mount-cache hash table entries: 512 (order: 0, 4096 bytes)=20 spawn_desched_task(00000000)=20 desched cpu_callback 3/00000000=20 ksoftirqd started up.=20 desched cpu_callback 2/00000000=20 desched thread 0 started up.=20 NET: Registered protocol family 16=20 Registering platform device 'xilinx_temac.0'. Parent at platform=20 Registering platform device 'xilinx_temac.1'. Parent at platform=20 Registering platform device 'xilinx_sysace.0'. Parent at platform=20 Registering platform device 'xilinx_gpio.0'. Parent at platform=20 Registering platform device 'xilinx_gpio.1'. Parent at platform=20 Registering platform device 'oled_fb.0'. Parent at platform=20 Generic PHY: Registered new driver=20 oled_fb: 4096 video memory mapped to c2011000=20 Console: switching to colour frame buffer device 16x8=20 xgpio #0 at 0x40000000 mapped to 0xC2020000=20 xgpio #1 at 0x40020000 mapped to 0xC2040000=20 io scheduler noop registered=20 io scheduler anticipatory registered=20 io scheduler deadline registered=20 io scheduler cfq registered=20 loop: loaded (max 8 devices)=20 elevator: using anticipatory as default io scheduler=20 System ACE at 0x41800000 mapped to 0xC2060000, irq=3D4, 1000944KB=20 xsysace: xsysace1 xsysace2=20 Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky=20 XTemac: using FIFO direct interrupt driven mode.=20 eth0: Xilinx TEMAC #0 at 0x20000000 mapped to 0xC2080000, irq=3D0=20 eth0: XTemac id 1.0f, block id 5, type 8=20 XTemac: using FIFO direct interrupt driven mode.=20 eth1: Xilinx TEMAC #1 at 0x20010000 mapped to 0xC20A0000, irq=3D10=20 eth1: XTemac id 1.0f, block id 5, type 8=20 i2c /dev entries driver=20 i2c-xil_custom: registered with I2C (0)=20 i2c-xil_custom: registered with I2C (1)=20 mice: PS/2 mouse device common for all mice=20 NET: Registered protocol family 2=20 IP: routing cache hash table of 512 buckets, 4Kbytes=20 TCP: Hash tables configured (established 2048 bind 4096)=20 NET: Registered protocol family 1=20 NET: Registered protocol family 17=20 EXT3-fs warning: maximal mount count reached, running e2fsck is = recommended=20 kjournald starting. Commit interval 5 seconds=20 EXT3 FS on xsysace2, internal journal=20 EXT3-fs: recovery complete.=20 EXT3-fs: mounted filesystem with ordered data mode.=20 VFS: Mounted root (ext3 filesystem).=20 Freeing unused kernel memory: 124k init=20 eth0: XTemac: Options: 0xb8f2=20 eth0: XTemac: speed set to 100Mb/s=20 eth0: XTemac: PHY Link carrier lost.=20 # /sbin/ifconfig eth1 up=20 # eth1: XTemac: Options: 0xb8f2=20 Any suggestion?=20 "Rick Moleres" =20 Sent by: linuxppc-embedded-bounces+linux-ppc=3Deurotel.it@ozlabs.org=20 08/02/2007 17.23=20 To "Ming Liu" , =20 cc linuxppc-embedded@ozlabs.org=20 Subject RE: ML403 Hard TEMAC, PLB and Linux 2.6 =20 =20 =20 Hi, As Ming says the Linux 2.6 TEMAC driver is made available in EDK 8.2.2 = as part of the BSP and Libraries generation for Linux 2.6. Note that we = made a recent fix for better PHY address detection and speed = negotiation. I've attached the adapter here, and it will be available in = EDK 9.1.1 when that's released. Thanks, Rick -----Original Message----- From: linuxppc-embedded-bounces+moleres=3Dxilinx.com@ozlabs.org = [mailto:linuxppc-embedded-bounces+moleres=3Dxilinx.com@ozlabs.org] On = Behalf Of Ming Liu Sent: Thursday, February 08, 2007 2:31 AM To: mamsadegh@hotmail.com Cc: linuxppc-embedded@ozlabs.org Subject: RE: ML403 Hard TEMAC, PLB and Linux 2.6 Hi, In xapp902, they are using the old cores for Temac. So it will be easier = to=20 generate a project in EDK 8.2. Not only the cores there are new, but = also=20 it can generate the driver for linux 2.6. BR Ming >From: Mohammad Sadegh Sadri >To: >CC: linuxppc-embedded@ozlabs.org >Subject: RE: ML403 Hard TEMAC, PLB and Linux 2.6 >Date: Thu, 8 Feb 2007 07:13:47 +0000 > > >Hi >Thanks for reply >Well, regarding xapp902, there is a very simple question, Where can I = find=20 it? It seems that Xilinx has deleted all of the links to these files. > > > > > >---------------------------------------- > > Subject: Re: ML403 Hard TEMAC, PLB and Linux 2.6 > > From: christophe.alayrac@cresitt.com > > To: mamsadegh@hotmail.com > > CC: linuxppc-embedded@ozlabs.org > > Date: Thu, 8 Feb 2007 06:51:45 +0100 > > > > Le mercredi 07 f=E9vrier 2007 ?22:30 +0000, Mohammad Sadegh Sadri a > > =E9crit : > > Hi Mohammad, > > > > Please find here after some answer > > > > > 1- I want to use, ML403, Hard TEMAC and PLB TEMAC cores. Is there = any=20 ready to use design, or any reference design available for this? > > > I'm using EDK 8.1 and I understood that, when I choose the ML403=20 board , EDK does not use hard temac, so , should I add it manually? ( = well=20 this is funny, but the wizard does not use hard temac , is it true? ) > > > Is there any ready EDK projects for ML403, with TEMAC and PLB = TEMAC=20 modules already inserted and cofigured? (I don't want to use GSRD ) ( If = yes would you please put the link here ) > > > > > You can start from XAPP 902 from Xilinx, this design demonstrate = TEMAC > > use in loopback mode. Some memers from that community have tried = from > > that design as a starting point. I did not nknow if the succeed. > > I would recommand to get EDK 8.2 SP2 and use the Wizard to build a = new > > design with TEMAC. > > > > > 2- Simply, Is there any driver available for linux 2.6 , for PLB=20 TEMAC and Hard TEMAC modules? If yes , can you put the link here, so = that I=20 can download it? > > > > > For the kernel you can get it from Montavista source code site using = GIT > > to download it (linux-xilinx-26). This is 2.6.17.4 version (last = week!) > > > > Then you will need to pacth the Kernel with TEMAC drivers (look for > > TEMAC PAULUS MVISTA with google, or follow my messages in that = mailing > > list) > > NOTE: If you use that TEMAC patch do not use SGDMA on your TEMAC, = use > > FIFO. > > > > > thanks > > Regards > > > > Chris > > > _________________________________________________________________ > > > Personalize your Live.com homepage with the news, weather, and = photos=20 you care about. > > > http://www.live.com/getstarted.aspx?icid=3DT001MSN30A0701 > > > _______________________________________________ > > > Linuxppc-embedded mailing list > > > Linuxppc-embedded@ozlabs.org > > > https://ozlabs.org/mailman/listinfo/linuxppc-embedded > > > >_________________________________________________________________ >Live Search: New search found >http://get.live.com/search/overview >_______________________________________________ >Linuxppc-embedded mailing list >Linuxppc-embedded@ozlabs.org >https://ozlabs.org/mailman/listinfo/linuxppc-embedded _________________________________________________________________ =D3=EB=C1=AA=BB=FA=B5=C4=C5=F3=D3=D1=BD=F8=D0=D0=BD=BB=C1=F7=A3=AC=C7=EB=CA= =B9=D3=C3 MSN Messenger: http://messenger.msn.com/cn =20 _______________________________________________ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded=20 ------_=_NextPart_001_01C7CA15.9F3FE513 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable

Hi,

 

The first thing I would try is to = make sure eth1 comes up without first bringing up eth0.  In other words, = does it come up independently?  If not, there could be something wrong = with its configuration in the kernel or perhaps a hardware design issue.  If = both interfaces come up independently, but not together, then there=A1=AFs = likely a driver issue as we have not tested dual channel TEMAC with the Linux = plb_temac driver.  Perhaps others on the list have.  The areas that I = would look at would be:  make sure each interface is getting a unique and correct PHY address; make sure any calls to the shared registers of the = two channels are protected with semaphores/spinlocks.  For example, = I=A1=AFm pretty sure the PHY registers are shared, so any PHY accesses should be = protected.  I would think other Xilinx driver accesses like Start/Stop/Reset/Get or SetOptions/etc=A1=AD should be protected as they may access shared = registers.

 

-Rick

 

From: Massimiliano.Patriarca@eurotel.it = [mailto:Massimiliano.Patriarca@eurotel.it] On Behalf Of = linux-ppc@eurotel.it
Sent: Thursday, July 19, = 2007 7:51 AM
To: Rick Moleres
Cc: Ming Liu; linuxppc-embedded@ozlabs.org; linuxppc-embedded-bounces+linux-ppc=3Deurotel.it@ozlabs.org; mamsadegh@hotmail.com
Subject: RE: ML403 Hard = TEMAC, PLB and Linux 2.6

 


Hi, we are trying to use both side of an hard = temac + 2 plb temac in a Virtex4FX12 project.
we succesfull implemented a single temac Montavista tree with = eth0.
when trying to use both temac, devices are correctly registered with = kernel-
eth0 comes up and working ok-
when manually start eth1 (/sbin/ifconfig eth1 up) kernel hang without any = error or info in the console

# dmesg
Linux version 2.6.10_mvl401-ml40x (massimiliano@linux-yhbz) (gcc version 3.4.3 (MontaVista 3.4.3-25.0.135.0702900 2007-04-01)) #250 Wed Jul 18 12:20:43 = CEST 2007
Eurotel motherboard init
Port by MontaVista Software, Inc. (source@mvista.com)
On node 0 totalpages: 7812
  DMA zone: 7812 pages, LIFO batch:1
  Normal zone: 0 pages, LIFO batch:1
  HighMem zone: 0 pages, LIFO batch:1
Built 1 zonelists
Kernel command line: console=3Dttl0 root=3D/dev/xsysace2 rw = ip=3Doff
Xilinx INTC #0 at 0x41200000 mapped to 0xFDFFF000
PID hash table entries: 128 (order: 7, 2048 bytes)
hr_time_init: arch_to_nsec =3D 8192000, nsec_to_arch =3D 1099511627
Console: colour dummy device 80x25
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes) =
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 28420k available (1864k kernel code, 528k data, 124k init, 0k = highmem)
Calibrating delay loop... 252.92 BogoMIPS (lpj=3D126464)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
spawn_desched_task(0000= 0000)
desched cpu_callback 3/00000000
ksoftirqd started up.
desched cpu_callback 2/00000000
desched thread 0 started up.
NET: Registered protocol family 16
Registering platform device 'xilinx_temac.0'. Parent at platform
Registering platform device 'xilinx_temac.1'. Parent at platform
Registering platform device 'xilinx_sysace.0'. Parent at platform
Registering platform device 'xilinx_gpio.0'. Parent at platform
Registering platform device 'xilinx_gpio.1'. Parent at platform
Registering platform device 'oled_fb.0'. Parent at platform
Generic PHY: Registered new driver
oled_fb: 4096 video memory mapped to c2011000
Console: switching to colour frame buffer device 16x8
xgpio #0 at 0x40000000 mapped to 0xC2020000
xgpio #1 at 0x40020000 mapped to 0xC2040000
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
loop: loaded (max 8 devices)
elevator: using anticipatory as default io scheduler
System ACE at 0x41800000 mapped to 0xC2060000, irq=3D4, 1000944KB =
 xsysace: xsysace1 xsysace2
Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky =
XTemac: using FIFO direct interrupt driven mode.
eth0: Xilinx TEMAC #0 at 0x20000000 mapped to 0xC2080000, = irq=3D0
eth0: XTemac id 1.0f, block id 5, type 8
XTemac: using FIFO direct interrupt driven mode.
eth1: Xilinx TEMAC #1 at 0x20010000 mapped to 0xC20A0000, = irq=3D10
eth1: XTemac id 1.0f, block id 5, type 8
i2c /dev entries driver
i2c-xil_custom: registered with I2C (0)
i2c-xil_custom: registered with I2C (1)
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
NET: Registered protocol family 1
NET: Registered protocol family 17
EXT3-fs warning: maximal mount count reached, running e2fsck is = recommended
kjournald starting.  Commit interval 5 seconds
EXT3 FS on xsysace2, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem).
Freeing unused kernel memory: 124k init
eth0: XTemac: Options: 0xb8f2
eth0: XTemac: speed set to 100Mb/s
eth0: XTemac: PHY Link carrier lost.

# /sbin/ifconfig eth1 up
# eth1: XTemac: Options: 0xb8f2

Any suggestion?


"Rick = Moleres" <Rick.Moleres@xilinx.com>
Sent by: = linuxppc-embedded-bounces+linux-ppc=3Deurotel.it@ozlabs.org=

08/02/2007 17.23

To

"Ming Liu" <eemingliu@hotmail.com>, = <mamsadegh@hotmail.com>

cc

linuxppc-embedded@ozlabs.org =

Subject

RE: ML403 Hard TEMAC, PLB and Linux = 2.6

 

 

 




Hi,

As Ming says the Linux 2.6 TEMAC driver is made = available in EDK 8.2.2 as part of the BSP and Libraries generation for Linux 2.6. =  Note that we = made a recent fix for better PHY address detection and speed negotiation. I've = attached the adapter here, and it will be available in EDK 9.1.1 when that's = released.

Thanks,
Rick

-----Original Message-----
From: linuxppc-embedded-bounces+moleres=3Dxilinx.com@ozlabs.org [mailto:linuxppc-embedded-bounces+moleres=3Dxilinx.com@ozlabs.org] On = Behalf Of Ming Liu
Sent: Thursday, February 08, 2007 2:31 = AM
To: mamsadegh@hotmail.com
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: ML403 Hard TEMAC, PLB and Linux = 2.6

Hi,
In xapp902, they are using the old cores for = Temac. So it will be easier to
generate a project in EDK 8.2. Not only the = cores there are new, but also
it can generate the driver for linux = 2.6.

BR
Ming

>From: Mohammad Sadegh Sadri <mamsadegh@hotmail.com>
>To: = <christophe.alayrac@cresitt.com>
>CC: = linuxppc-embedded@ozlabs.org
>Subject: RE: ML403 Hard TEMAC, PLB and Linux = 2.6
>Date: Thu, 8 Feb 2007 07:13:47 = +0000
>
>
>Hi
>Thanks for reply
>Well, regarding xapp902, there is a very = simple question, Where can I find
it? It seems that Xilinx has deleted all of the = links to these files.
>
>
>
>
>
>---------------------------------------- > > Subject: Re: ML403 Hard TEMAC, PLB and = Linux 2.6
> > From: = christophe.alayrac@cresitt.com
> > To: = mamsadegh@hotmail.com
> > CC: = linuxppc-embedded@ozlabs.org
> > Date: Thu, 8 Feb 2007 06:51:45 = +0100
> >
> > Le mercredi 07 f=E9vrier 2007 ?22:30 +0000, Mohammad Sadegh Sadri a
> > =E9crit = :
> > Hi Mohammad,
> >
> > Please find here after some = answer
> >
> > > 1- I want to use, ML403, Hard = TEMAC and PLB TEMAC cores. Is there any
ready to use design, or any reference design = available for this?
> > > I'm using EDK 8.1 and I = understood that, when I choose the ML403
board , EDK does not use hard temac, so , should = I add it manually? ( well
this is funny, but the wizard does not use hard = temac , is it true? )
> > > Is there any ready EDK projects = for ML403, with TEMAC and PLB TEMAC
modules already inserted and cofigured? (I don't = want to use GSRD ) ( If
yes would you please put the link here = )
> > >
> > You can start from XAPP 902 from = Xilinx, this design demonstrate TEMAC
> > use in loopback mode. Some memers from = that community have tried from
> > that design as a starting point. I did = not nknow if the succeed.
> > I would recommand to get EDK 8.2 SP2 = and use the Wizard to build a new
> > design with TEMAC.
> >
> > > 2- Simply, Is there any driver = available for linux 2.6 , for PLB
TEMAC and Hard TEMAC modules? If yes , can you = put the link here, so that I
can download it?
> > >
> > For the kernel you can get it from = Montavista source code site using
GIT
> > to download it (linux-xilinx-26). This = is 2.6.17.4 version (last week!)
> >
> > Then you will need to pacth the Kernel = with TEMAC drivers (look for
> > TEMAC PAULUS MVISTA with google, or = follow my messages in that mailing
> > list)
> > NOTE: If you use that TEMAC patch do = not use SGDMA on your TEMAC, use
> > FIFO.
> >
> > > thanks
> > Regards
> >
> > Chris
> > > _________________________________________________________________<= /tt>
> > > Personalize your Live.com = homepage with the news, weather, and photos
you care about.
> > > http://www.live.com/getstarted.aspx?icid=3DT001MSN30A0701
= > > > _______________________________________________
> > > Linuxppc-embedded mailing = list
> > > = Linuxppc-embedded@ozlabs.org
> > > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> >
>
>_______________________________________________________= __________
>Live Search: New search = found
>http://get.live.com/search/overview
>_______________________________________________<= /tt>
>Linuxppc-embedded mailing = list
>Linuxppc-embedded@ozlabs.org
>https://ozlabs.org/mailman/listinfo/linuxppc-embedded

___________________________________________________________= ______
=D3=EB=C1=AA=BB=FA=B5=C4=C5=F3=D3=D1=BD=F8=D0=D0=BD=BB=C1=F7= =A3=AC=C7=EB=CA=B9=D3=C3 MSN Messenger:  http://messenger.msn.com/cn =  

_______________________________________________=
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

------_=_NextPart_001_01C7CA15.9F3FE513--