From: Kumar Gala <kumar.gala@freescale.com>
To: Adrian Cox <adrian@humboldt.co.uk>
Cc: <linuxppc-embedded@lists.linuxppc.org>,
Kumar Gala <kumar.gala@motorola.com>, <mgreer@mvista.com>
Subject: Re: [PATCH][RFC] Second version of MPC10x OCP
Date: Thu, 24 Jun 2004 12:03:52 -0500 [thread overview]
Message-ID: <786932E0-C600-11D8-8121-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <1088078926.1372.13.camel@localhost>
On Jun 24, 2004, at 11:36 AM, Adrian Cox wrote:
> On Thu, 2004-06-24 at 04:32, Kumar Gala wrote:
>> I'm confused are we adding the OCP struct for every 10x device? Did
>> we
>> get closure on the question if 105, 106 & 8240 would also work?
>
> According to the chip manuals:
> 107, 8240, and 8245 have the internal peripherals and should work.
> 105 and 106 don't have internal peripherals.
>
> mpc10x_common.c supports 106, 107, 8240, and 8245, but does not support
> 105.
>
> The code only adds the OCP devices if the device is not 106.
>
> My patch is slightly broken where I edited out a local board variant by
> hand. I'll produce a cleaned up patch based on my Sandpoint tree once
> I've tested it together with the 85xx I2C driver.
Ok, I think the 1st patch had this code, and 2nd seemed to lose it (or
I did not see it).
- kumar
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-06-24 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-20 15:47 [PATCH][RFC] Second version of MPC10x OCP Adrian Cox
2004-06-23 18:51 ` Mark A. Greer
2004-06-24 3:32 ` Kumar Gala
2004-06-24 16:36 ` Adrian Cox
2004-06-24 17:03 ` Kumar Gala [this message]
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=786932E0-C600-11D8-8121-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale.com \
--cc=adrian@humboldt.co.uk \
--cc=kumar.gala@motorola.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mgreer@mvista.com \
/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).