Re: [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment.

2009-10-20 Thread Scott Wood
On Tue, Oct 20, 2009 at 12:01:19PM +0200, Richard Cochran wrote: > > -Original Message- > > From: Scott Wood [mailto:scottw...@freescale.com] > > > > What problems have you been having with upstream kernels on mpc8313erdb, > > other than this IRQ issue? It should work, though the BSP may h

RE: [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment.

2009-10-20 Thread Richard Cochran
> -Original Message- > From: Scott Wood [mailto:scottw...@freescale.com] > > What problems have you been having with upstream kernels on mpc8313erdb, > other than this IRQ issue? It should work, though the BSP may have extra > features that haven't been pushed upstream. I have been workin

Re: [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment.

2009-10-16 Thread Kim Phillips
On Thu, 15 Oct 2009 21:40:43 +0200 Roland Lezuo wrote: > On Mon, 2009-10-12 at 11:06 -0500, Kim Phillips wrote: > > On Wed, 9 Sep 2009 15:28:01 -0500 > > Kumar Gala wrote: > > > On Sep 9, 2009, at 1:22 PM, Scott Wood wrote: > > > > We really should have a u-boot fixup based on SVR. > > > > Rola

Re: [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment.

2009-10-16 Thread Kumar Gala
On Oct 16, 2009, at 11:01 AM, Scott Wood wrote: I have the LITE5200B, MPC8313-ERDB, MPC8572DS, and the P2020DS in house, and it is really the same, sad story with each of them. Wouldn't it be grand if the development boards would boot "out of the box" when compiling the most recent kernel with

Re: [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment.

2009-10-16 Thread Scott Wood
On Fri, Oct 16, 2009 at 08:31:19AM +0200, Richard Cochran wrote: > > -Original Message- > > From: Scott Wood [mailto:scottw...@freescale.com] > > Subject: Re: [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment. > > > > On Thu, Oct 15, 2009 at 02:

RE: [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment.

2009-10-15 Thread Richard Cochran
> -Original Message- > From: Scott Wood [mailto:scottw...@freescale.com] > Subject: Re: [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment. > > On Thu, Oct 15, 2009 at 02:19:30PM +0200, Richard Cochran wrote: > > 2. Having only one dts for his board, but

Re: [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment.

2009-10-15 Thread Scott Wood
On Thu, Oct 15, 2009 at 02:19:30PM +0200, Richard Cochran wrote: > >-Original Message- From: Scott Wood [mailto:scottw...@freescale.com] > >Because that would be three times the device trees to maintain, and a > >source of user confusion. > > I wonder which is more confusing for the user:

RE: [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment.

2009-10-15 Thread Richard Cochran
>-Original Message- From: Scott Wood [mailto:scottw...@freescale.com] >Because that would be three times the device trees to maintain, and a >source of user confusion. I wonder which is more confusing for the user: 1. Choosing one of three dts files. 2. Having only one dts for his board,

Re: [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment.

2009-10-14 Thread Scott Wood
bject: Re: [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment. > > > >On Fri, Sep 04, 2009 at 12:31:25PM +0200, Roland Lezuo wrote: > >> The following patch is needed to correctly assign the IRQs for the > >> gianfar driver on the MPC8313ERDB-revc boards. ERR

RE: [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment.

2009-10-14 Thread Richard Cochran
>-Original Message- >From: linuxppc-dev-bounces On Behalf Of Scott Wood >Sent: Wednesday, September 09, 2009 8:22 PM >To: Roland Lezuo >Cc: linuxppc-dev@lists.ozlabs.org >Subject: Re: [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment. > >On Fri, Sep 04,

Re: [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment.

2009-10-12 Thread Kim Phillips
On Wed, 9 Sep 2009 15:28:01 -0500 Kumar Gala wrote: > > On Sep 9, 2009, at 1:22 PM, Scott Wood wrote: > > > On Fri, Sep 04, 2009 at 12:31:25PM +0200, Roland Lezuo wrote: > >> The following patch is needed to correctly assign the IRQs for the > >> gianfar driver on the MPC8313ERDB-revc boards. E

Re: [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment.

2009-09-09 Thread Mark Bishop
Quoting Scott Wood : On Fri, Sep 04, 2009 at 12:31:25PM +0200, Roland Lezuo wrote: The following patch is needed to correctly assign the IRQs for the gianfar driver on the MPC8313ERDB-revc boards. ERR and TX are swapped as well as the interrupt lines for the two devices. And it will incorrect

Re: [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment.

2009-09-09 Thread Kim Phillips
On Wed, 9 Sep 2009 15:28:01 -0500 Kumar Gala wrote: > > On Sep 9, 2009, at 1:22 PM, Scott Wood wrote: > > > On Fri, Sep 04, 2009 at 12:31:25PM +0200, Roland Lezuo wrote: > >> The following patch is needed to correctly assign the IRQs for the > >> gianfar driver on the MPC8313ERDB-revc boards. E

Re: [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment.

2009-09-09 Thread Kumar Gala
On Sep 9, 2009, at 1:22 PM, Scott Wood wrote: On Fri, Sep 04, 2009 at 12:31:25PM +0200, Roland Lezuo wrote: The following patch is needed to correctly assign the IRQs for the gianfar driver on the MPC8313ERDB-revc boards. ERR and TX are swapped as well as the interrupt lines for the two device

Re: [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment.

2009-09-09 Thread Scott Wood
On Fri, Sep 04, 2009 at 12:31:25PM +0200, Roland Lezuo wrote: > The following patch is needed to correctly assign the IRQs for the > gianfar driver on the MPC8313ERDB-revc boards. ERR and TX are swapped > as well as the interrupt lines for the two devices. And it will incorrectly assign them on ol