linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: jumpingProgrammer <rabbitzp@163.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: a question of mpc8313, maybe simple
Date: Mon, 23 Jun 2008 18:13:41 -0700 (PDT)	[thread overview]
Message-ID: <18081728.post@talk.nabble.com> (raw)
In-Reply-To: <20080623170956.GA6978@loki.buserror.net>


Thanks a lot for answer my question.
But i am newhand and not very clear about it.
Do you mean:
1. in this case i do not need to include DMA when i "make menuconfig" ?
        The path is Device Drivers->DMA.
2. in this case i do not need add any DMA information in mpc8313erdb.dts?

Now i am reading PCI driver in kernel 2.6.20 to catch your meaning.


Scott Wood-2 wrote:
> 
> On Mon, Jun 23, 2008 at 05:48:07AM -0700, jumpingProgrammer wrote:
>> i am working with a board of mpc8313 using default mpc8313erdb.dts.
>> But i do not know how can i correctly use DMA to transport data from
>> memory
>> to a PCI device.
>> i tryed this
>> {
>>      .....
>>      request_irq(IRQ,....);
>>      request_dma(.....);
>>      ....
>> }
>> 
>> In request_irq() , i do not know what is the parameter IRQ.
> 
> Use pci_dev->irq.
> 
>> And , i did not find any words about DMA in mpc8313erdb.dts .
> 
> PCI devices can do bus-mastering DMA themselves; request_dma() is for ISA
> devices.
> 
> -Scott
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
> 
> 

-- 
View this message in context: http://www.nabble.com/a-question-of-mpc8313%2C-maybe-simple-tp18069331p18081728.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.

  reply	other threads:[~2008-06-24  1:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 12:48 a question of mpc8313, maybe simple jumpingProgrammer
2008-06-23 17:09 ` Scott Wood
2008-06-24  1:13   ` jumpingProgrammer [this message]
2008-06-24 17:58     ` 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=18081728.post@talk.nabble.com \
    --to=rabbitzp@163.com \
    --cc=linuxppc-dev@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).