From: Pantelis Antoniou <panto@intracom.gr>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: Adrian Cox <adrian@humboldt.co.uk>, Matt Porter <porter@cox.net>,
"Kumar K. Gala" <kumar.gala@motorola.com>,
Stefan Nickl <Stefan.Nickl@kontron.com>,
Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH][RFC] I2C support for MPC107 and relatives
Date: Mon, 14 Jun 2004 17:38:02 +0300 [thread overview]
Message-ID: <40CDB84A.7010906@intracom.gr> (raw)
In-Reply-To: <36790086-BE08-11D8-8344-000393DBC2E8@freescale.com>
Kumar Gala wrote:
>
> Adrian,
>
> It would be really helpful if you could take a look at getting the
> driver working on a MPC107 based systems. We have not had time to look
> at that fully. However, are intent has always to get the same driver
> working for MPC10x, 824x, 85xx systems since the block is very similar.
>
> - kumar
>
> On Jun 14, 2004, at 8:24 AM, Adrian Cox wrote:
>
>> On Mon, 2004-06-14 at 14:01, Stefan Nickl wrote:
>>
>>> On Mon, 2004-06-14 at 13:37, Adrian Cox wrote:
>>>
>>>> On Mon, 2004-06-14 at 12:01, Stefan Nickl wrote:
>>>>
>>>>> FYI: The Motorola folks recently pushed a I2C driver called
>>>>> i2c-mpc.c
>>>>> into the 2.4 tree, it seems to be fully OCP'ed, save it seems the
>>>>> platform hooks are only present for 8540 yet.
>>>>
>>>>
>>>> Do you know which 2.4 tree? It's not in linuxppc_2_4_devel or in the
>>>> main 2.4 kernel. If their driver works with my OCP patch, it would
>>>> save
>>>> a whole lot of effort.
>>>
>>>
>>> Sorry, I was talking about
>>> bk://ppc.bkbits.net/linuxppc-2.4
>>
>>
>> It does similar things to mine, but it can support the controller on 8
>> as well as 32 bit busses. I may try putting it into my 2.6 tree and
>> using it on the MPC107.
>>
>> - Adrian Cox
>> Humboldt Solutions Ltd.
>
>
>
>
>
>
I'm thinking about taking the plunge and OCPfying 8xx so perhaps we
can get this thing organized.
I'd like to have a hierarhy of the peripherals like so:
______- CPM -______ ___________ ___
/ / \ \ \
/ / \ \ \
Timers SCC1..n _ SMC__ IDMA DSP-f etc.
/ | \ \ | \
/ | \ \ \ \
UART HDLC Enet QMC UART Transp.
/ \
HDLC0..63 Transp0..63
Of course with only one protocol active per SCC/SMC.
Is something like this supported with the OCP code, and if not
how could I get around in making it work?
IMO, we could share alot of the stuff between the CPM1/CPM2/CPM3...
Regards
Pantelis
P.S. I suck at ASCII art
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-14 14:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 10:10 [PATCH][RFC] OCP support for MPC107 and relatives Adrian Cox
2004-06-14 10:23 ` [PATCH][RFC] I2C " Adrian Cox
2004-06-14 11:01 ` Stefan Nickl
2004-06-14 11:37 ` Adrian Cox
2004-06-14 13:01 ` Stefan Nickl
2004-06-14 13:24 ` Adrian Cox
2004-06-14 13:39 ` Kumar Gala
2004-06-14 14:38 ` Pantelis Antoniou [this message]
2004-06-14 13:43 ` [PATCH][RFC] OCP " Kumar Gala
2004-06-14 13:59 ` Kumar Gala
2004-06-14 14:47 ` Adrian Cox
2004-06-14 15:46 ` Matt Porter
2004-06-15 0:38 ` Kumar Gala
2004-06-14 17:05 ` Mark A. Greer
2004-06-15 8:10 ` Adrian Cox
2004-06-15 17:33 ` Mark A. Greer
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=40CDB84A.7010906@intracom.gr \
--to=panto@intracom.gr \
--cc=Stefan.Nickl@kontron.com \
--cc=adrian@humboldt.co.uk \
--cc=dwmw2@infradead.org \
--cc=kumar.gala@freescale.com \
--cc=kumar.gala@motorola.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=porter@cox.net \
/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).