linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Vikas Aggarwal" <va824363@albany.edu>
To: "Kim Phillips" <kim.phillips@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: mpc8248  SEC -- interrupt handler 'is' invoked
Date: Mon, 1 Aug 2005 14:50:49 -0400 (EDT)	[thread overview]
Message-ID: <35388.198.22.236.230.1122922249.squirrel@198.22.236.230> (raw)
In-Reply-To: <20050801123728.62764c7e.kim.phillips@freescale.com>

Hi Kim,
Yes, i checked to my knowledge that i am doing all these steps and also
checked the
bit positions.

I will send you the code excerpts. The code was written for 2.4 kernel and
8555E(downloaded from freescale)  and i ported it to  8248/kernel 2.6.

thanks for your help
-vikas


> On Sun, 31 Jul 2005 20:48:16 -0400 (EDT)
> "Vikas Aggarwal" <va824363@albany.edu> wrote:
>
>> Tried it as u said . No luck :(
>> But something more i noted now in CPSR(channel pointer status
>> register=0x2040)  that before ISR invoked it has 0x0:0x7.
>>
>> After ISR invoked it has 0x7:0x2007 .  The 7 in low bits means
>> channel_error and 2 is at "reserved" bits as per documentation, don't
>> know
>> what that means.
>>
>> I also tried kmalloc with GFP_DMA, for the memory where i create the
>> Descriptor.
>> Please keep giving ideas for debugging this as this is what driving me
>> right now.
>> regards
>> -vikas
>
>
> So you reset the master, then the channel, allocate the RNG descriptor,
> allocate the random data buffer, fill the descriptor with values for an
> RNG request the size of your buffer (filling with the physical address of
> your random data buffer), and submit the descriptor's physical address to
> the FR..
>
> btw, I'm finding it hard to help without seeing sec register transaction
> data, descriptor data, virtual and physical addresses, etc.
>
> Kim
>

  reply	other threads:[~2005-08-01 18:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-29 15:40 mpc8248 SEC -- interrupt handler not invoked Vikas Aggarwal
2005-07-29 20:33 ` Kim Phillips
2005-07-30  3:39   ` Vikas Aggarwal
2005-07-30 23:32     ` Kim Phillips
2005-08-01  0:48       ` mpc8248 SEC -- interrupt handler "is" invoked Vikas Aggarwal
2005-08-01 17:37         ` Kim Phillips
2005-08-01 18:50           ` Vikas Aggarwal [this message]
2005-08-02 15:45           ` mpc8248 SEC -- interrupt handler 'is' invoked Vikas Aggarwal
2005-08-03 16:47             ` Kim Phillips
2005-08-03 18:33               ` Vikas Aggarwal
2005-08-03 20:35                 ` Kim Phillips
2005-08-09 13:38                   ` Vikas Aggarwal
2005-08-09 15:13                     ` Kim Phillips
2005-08-09 20:52                   ` Vikas Aggarwal
2005-08-10 15:37                     ` Kim Phillips
2005-08-11 18:48                       ` Vikas Aggarwal

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=35388.198.22.236.230.1122922249.squirrel@198.22.236.230 \
    --to=va824363@albany.edu \
    --cc=kim.phillips@freescale.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /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).