linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <kumar.gala@freescale.com>
To: "Vitaly Bordug" <vbordug@ru.mvista.com>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: RFC: cpm2_devices.c
Date: Wed, 15 Jun 2005 10:41:26 -0500	[thread overview]
Message-ID: <7e2a8c0e483e5dfdc532c47d20776bbd@freescale.com> (raw)
In-Reply-To: <42B049DC.7040703@ru.mvista.com>


On Jun 15, 2005, at 10:31 AM, Vitaly Bordug wrote:

> Kumar Gala wrote:
>
>>
>> On Jun 15, 2005, at 2:55 AM, Vitaly Bordug wrote:
>>
>>> Kumar,
>>> I assume this as a IMMR enumerating you promised to help with. Is it 
>>> in
>>> the final state? And what was the reason of fcc_regs_c removal?
>>> I'm also going to change the files name to cpm2_.. .
>>
>>
>> Yes, I removed the fcc_regs_c since its not always true.  Please don't
>> rename the file to cpm2_.  I think I'm going to end up renaming them
>> to pq2_ since that is the most appropriate name.  I'd say we are about
>> 80% the way to a final patch.
>>
> Great. Apart of naming issue - what else remaining to do?
> I mean how can I contribute to speed-up this?

At this point, I think a bit more discussion is going to be needed on 
if SI1, SI2, and CPM are "devices" or not.

Also, does the proposed FCC defn. sufficient or do we need the extended 
registers that exist on some of the newer PQ2/PQ3 devices?  I wasn't 
sure if the drivers used them or not.

- kumar

  reply	other threads:[~2005-06-15 15:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-14 18:18 RFC: cpm2_devices.c Allen Curtis
2005-06-15  3:35 ` Kumar Gala
2005-06-15  3:57   ` Allen Curtis
2005-06-15  4:13     ` Kumar Gala
2005-06-15  4:41       ` Allen Curtis
2005-06-15 14:24         ` Jason McMullan
2005-06-15 15:06           ` Kumar Gala
2005-06-15 17:48             ` Allen Curtis
2005-06-15 18:05               ` Vitaly Bordug
2005-06-15 14:29         ` Kumar Gala
2005-06-15 14:30         ` Kumar Gala
2005-06-16 15:12       ` Dan Malek
2005-06-16 15:33         ` Kumar Gala
2005-06-16 15:42           ` Allen Curtis
2005-06-16 15:53             ` Kumar Gala
2005-06-16 16:39               ` Allen Curtis
2005-06-16 19:33           ` Dan Malek
2005-06-15  7:55   ` Vitaly Bordug
2005-06-15 14:25     ` Kumar Gala
2005-06-15 14:33       ` Jason McMullan
2005-06-15 15:01         ` Kumar Gala
2005-06-15 15:31       ` Vitaly Bordug
2005-06-15 15:41         ` Kumar Gala [this message]
2005-06-15 16:07           ` Vitaly Bordug
2005-06-16  6:42           ` Pantelis Antoniou
2005-06-16  9:33             ` Wolfgang Denk
2005-06-16 15:02             ` Kumar Gala

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=7e2a8c0e483e5dfdc532c47d20776bbd@freescale.com \
    --to=kumar.gala@freescale.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=vbordug@ru.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).