Re: [RTnet-users] Porting mpc8260 fcc_enet.c

2007-06-14 Thread Juha Niskanen
2007/6/13, Jan Kiszka <[EMAIL PROTECTED]>: .. > Looks like an IRQ re-enabling problem. I recall Philippe recently fixing > such a thing... Here it is [1]. Looks like that. I add additional rtdm_irq_enable and get it working. /* Handle receive event in its own function. */ i

Re: [RTnet-users] Porting mpc8260 fcc_enet.c

2007-06-13 Thread Jan Kiszka
Wolfgang Grandegger wrote: > Jan Kiszka wrote: >> Juha Niskanen wrote: >>> 2007/6/3, Wolfgang Grandegger <[EMAIL PROTECTED]>: Juha Niskanen wrote: > Hi Jan, > [...] >>> I can allready start the rtnet and get a lot of error messages. >>> >>> rteth0: tx queue full!.

Re: [RTnet-users] Porting mpc8260 fcc_enet.c

2007-06-13 Thread Wolfgang Grandegger
Jan Kiszka wrote: > Juha Niskanen wrote: >> 2007/6/3, Wolfgang Grandegger <[EMAIL PROTECTED]>: >>> Juha Niskanen wrote: Hi Jan, >>> [...] >>> >> I can allready start the rtnet and get a lot of error messages. >> >> rteth0: tx queue full!. >> rteth0: tx queue full!. >>

Re: [RTnet-users] Porting mpc8260 fcc_enet.c

2007-06-13 Thread Jan Kiszka
Juha Niskanen wrote: > 2007/6/3, Wolfgang Grandegger <[EMAIL PROTECTED]>: >> Juha Niskanen wrote: >> > Hi Jan, >> > >> [...] >> >> >> > I can allready start the rtnet and get a lot of error messages. >> >> > >> >> > rteth0: tx queue full!. >> >> > rteth0: tx queue full!. >> >> > >> >> >> >> Transmi

Re: [RTnet-users] Porting mpc8260 fcc_enet.c

2007-06-13 Thread Juha Niskanen
2007/6/3, Wolfgang Grandegger <[EMAIL PROTECTED]>: > Juha Niskanen wrote: > > Hi Jan, > > > [...] > > >> > I can allready start the rtnet and get a lot of error messages. > >> > > >> > rteth0: tx queue full!. > >> > rteth0: tx queue full!. > >> > > >> > >> Transmission is not working, maybe its IRQ

Re: [RTnet-users] Porting mpc8260 fcc_enet.c

2007-06-04 Thread Wolfgang Grandegger
Juha Niskanen wrote: > 2007/6/4, Wolfgang Grandegger <[EMAIL PROTECTED]>: >> Juha Niskanen wrote: >>> 2007/6/3, Wolfgang Grandegger <[EMAIL PROTECTED]>: Wolfgang Grandegger wrote: > Jan Kiszka wrote: >> Juha Niskanen wrote: >>> Hi, >>> >>> I am porting mpc8260 fcc_enet.c fr

Re: [RTnet-users] Porting mpc8260 fcc_enet.c

2007-06-04 Thread Juha Niskanen
2007/6/4, Wolfgang Grandegger <[EMAIL PROTECTED]>: > Juha Niskanen wrote: > > 2007/6/3, Wolfgang Grandegger <[EMAIL PROTECTED]>: > >> Wolfgang Grandegger wrote: > >> > Jan Kiszka wrote: > >> >> Juha Niskanen wrote: > >> >>> Hi, > >> >>> > >> >>> I am porting mpc8260 fcc_enet.c from 2.6.18 to rtnet,

Re: [RTnet-users] Porting mpc8260 fcc_enet.c

2007-06-04 Thread Wolfgang Grandegger
Juha Niskanen wrote: > 2007/6/3, Wolfgang Grandegger <[EMAIL PROTECTED]>: >> Wolfgang Grandegger wrote: >> > Jan Kiszka wrote: >> >> Juha Niskanen wrote: >> >>> Hi, >> >>> >> >>> I am porting mpc8260 fcc_enet.c from 2.6.18 to rtnet, >> > >> > I recommend using the a more recent version of Linux wit

Re: [RTnet-users] Porting mpc8260 fcc_enet.c

2007-06-04 Thread Juha Niskanen
2007/6/3, Wolfgang Grandegger <[EMAIL PROTECTED]>: > Wolfgang Grandegger wrote: > > Jan Kiszka wrote: > >> Juha Niskanen wrote: > >>> Hi, > >>> > >>> I am porting mpc8260 fcc_enet.c from 2.6.18 to rtnet, > > > > I recommend using the a more recent version of Linux with the > > arch/powerpc tree. Th

Re: [RTnet-users] Porting mpc8260 fcc_enet.c

2007-06-04 Thread Juha Niskanen
2007/6/3, Wolfgang Grandegger <[EMAIL PROTECTED]>: > Jan Kiszka wrote: > > Juha Niskanen wrote: > >> Hi, > >> > >> I am porting mpc8260 fcc_enet.c from 2.6.18 to rtnet, > > I recommend using the a more recent version of Linux with the > arch/powerpc tree. The arch/ppc tree is not maintained any mor

Re: [RTnet-users] Porting mpc8260 fcc_enet.c

2007-06-03 Thread Wolfgang Grandegger
Juha Niskanen wrote: > Hi Jan, > [...] >> > I can allready start the rtnet and get a lot of error messages. >> > >> > rteth0: tx queue full!. >> > rteth0: tx queue full!. >> > >> >> Transmission is not working, maybe its IRQ line setup is broken. Thus > > Any idea of good place to start debuggin

Re: [RTnet-users] Porting mpc8260 fcc_enet.c

2007-06-03 Thread Wolfgang Grandegger
Wolfgang Grandegger wrote: > Jan Kiszka wrote: >> Juha Niskanen wrote: >>> Hi, >>> >>> I am porting mpc8260 fcc_enet.c from 2.6.18 to rtnet, > > I recommend using the a more recent version of Linux with the > arch/powerpc tree. The arch/ppc tree is not maintained any more. Any > chance to switch

Re: [RTnet-users] Porting mpc8260 fcc_enet.c

2007-06-03 Thread Wolfgang Grandegger
Jan Kiszka wrote: > Juha Niskanen wrote: >> Hi Jan, >> >> I forget mention my defines I add beginin of file: >> /* My configs */ >> #define CONFIG_EA8248 >> #define CONFIG_FCC1_ENET 1 >> #define CONFIG_FCC_LXT971 1 >> /* #define CONFIG_RTAI_RTNET_USE_MDIO 1 */ >> /* #define PHY_INTERRUPT 1 */ >> >>

Re: [RTnet-users] Porting mpc8260 fcc_enet.c

2007-06-03 Thread Wolfgang Grandegger
Jan Kiszka wrote: > Juha Niskanen wrote: >> Hi, >> >> I am porting mpc8260 fcc_enet.c from 2.6.18 to rtnet, I recommend using the a more recent version of Linux with the arch/powerpc tree. The arch/ppc tree is not maintained any more. Any chance to switch? > Please help me first: Is this a rewr

Re: [RTnet-users] Porting mpc8260 fcc_enet.c

2007-06-01 Thread Jan Kiszka
Juha Niskanen wrote: > Hi Jan, > > I forget mention my defines I add beginin of file: > /* My configs */ > #define CONFIG_EA8248 > #define CONFIG_FCC1_ENET 1 > #define CONFIG_FCC_LXT971 1 > /* #define CONFIG_RTAI_RTNET_USE_MDIO 1 */ > /* #define PHY_INTERRUPT 1 */ > > If I define CONFIG_RTAI_RTNE

Re: [RTnet-users] Porting mpc8260 fcc_enet.c

2007-06-01 Thread Juha Niskanen
Hi Jan, I forget mention my defines I add beginin of file: /* My configs */ #define CONFIG_EA8248 #define CONFIG_FCC1_ENET 1 #define CONFIG_FCC_LXT971 1 /* #define CONFIG_RTAI_RTNET_USE_MDIO 1 */ /* #define PHY_INTERRUPT 1 */ If I define CONFIG_RTAI_RTNET_USE_MDIO I get: ~ $ modprobe rtnet ***

Re: [RTnet-users] Porting mpc8260 fcc_enet.c

2007-05-31 Thread Jan Kiszka
Juha Niskanen wrote: > Hi, > > I am porting mpc8260 fcc_enet.c from 2.6.18 to rtnet, Please help me first: Is this a rewrite of the existing driver or an update/extension/2.6-compatibility patch? In the latter case, sending your changes in form of a real patch would be preferred for reviews ("svn