From: Scott Wood <scottwood@freescale.com>
To: Richard Cochran <richard.cochran@omicron.at>
Cc: "'linuxppc-dev@lists.ozlabs.org'" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment.
Date: Thu, 15 Oct 2009 11:27:28 -0500 [thread overview]
Message-ID: <20091015162728.GB3730@loki.buserror.net> (raw)
In-Reply-To: <95DC1AA8EC908B48939B72CF375AA5E30E2AE72C@alice.at.omicron.at>
On Thu, Oct 15, 2009 at 02:19:30PM +0200, Richard Cochran wrote:
> >-----Original Message----- From: Scott Wood [mailto:scottwood@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.
Possibly incorrectly.
> 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.
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).
-Scott
next prev parent reply other threads:[~2009-10-15 16:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 10:31 [PATCH] * mpc8313erdb.dts: Fixed eTSEC interrupt assignment Roland Lezuo
2009-09-09 18:22 ` Scott Wood
2009-09-09 20:28 ` Kumar Gala
2009-09-09 20:35 ` Kim Phillips
2009-10-12 16:06 ` Kim Phillips
[not found] ` <1255635643.20355.2.camel@tbfg-desktop>
2009-10-16 22:27 ` Kim Phillips
2009-09-09 20:49 ` Mark Bishop
2009-10-14 7:41 ` Richard Cochran
2009-10-14 15:27 ` Scott Wood
2009-10-15 12:19 ` Richard Cochran
2009-10-15 16:27 ` Scott Wood [this message]
2009-10-16 6:31 ` Richard Cochran
2009-10-16 16:01 ` Scott Wood
2009-10-16 16:30 ` Kumar Gala
2009-10-20 10:01 ` Richard Cochran
2009-10-20 15:56 ` Scott Wood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091015162728.GB3730@loki.buserror.net \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=richard.cochran@omicron.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).