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

Richard Cochran richard.cochran at omicron.at
Fri Oct 16 17:31:19 EST 2009

> -----Original Message-----
> From: Scott Wood [mailto:scottwood at 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 Ethernet doesn't work.
> The point is to fix u-boot so that it *does* work with only one dts.  If
> people not upgrading u-boot is your concern, we could put the fixup in the
> Linux platform code instead.

Yes, I was thinking that upgrading u-boot can be problematic for
people who don't have a JTAG flash tool, in case things go wrong. The
whole kernel-uboot-dts triangle is a constant source of confusion, IMHO.

But I thought the whole point of the device tree was, that it is easy
to produce a dts that exactly matches a particular physical board
design. If MPC8313-ERDB REVC has a different IRQ routing, then doesn't
it deserve its own dts? Or do only *some* of the REVC boards have this

> And feel free to ask through official Freescale support channels why the
> U-Boot that shipped on these boards does not have such a fixup (or why they
> decided it was better to make late-rev 8313's interrupt assignments match
> other 83xx than for all revs of the same part number to have the same
> interrupt assignments).

It sounds like you are not overly satisfied with Freescale's handling
of their BSPs ;)

To be fair, I am happy that Freescale appears to take Linux support
seriously, but I do think they drop the ball once a BSP is
published. For example, the MPC8313-ERDB ships with kernel 2.6.23
(with the old style dts) and a fair number of non-mainstream
patches. It is not so easy to get a recent kernel booting on that

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 default config?

Maybe that's only wishful thinking, but I am happy to contribute what I


More information about the Linuxppc-dev mailing list