From: "Jacky Lam" <jackylam@astri.org>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: General porting question
Date: Thu, 9 Oct 2003 23:36:07 +0800 [thread overview]
Message-ID: <001901c38e7b$0f6ed830$0202a8c0@homevl9biy3v7e> (raw)
In-Reply-To: 20031009063812.A11979@home.com
> Almost.
>
> You can not use virt_to_* on the address returned by
> pci_alloc_consistent().
Why?
By the way, this problem will only affect the consistency of dma buffer.
In my case, it will only cause wrong output sound. But my card seems don't
consume the dma and doesn't give any interrupt in return. It's fine on PC
and I can receive interrupt if I write to the card's register to force an
interrupt. What other possible porting problem can be here? Really
strange....
>
> You need to hold on to the dma_addr_t returned, perform
> a bus_to_virt(dma_addr_t) and then a virt_to_* will work
> on that address.
umm....then does virt_to_phys(bus_to_virt(dma_addr_t))==dma_addr_t
or
bus_to_virt(dma_addr_t)==pci_alloc_consistent() ?
>
> However, I'm not sure of the "PCI related memory space" you
> are referring to. "PCI memory space" has a distinct meaning
> and the virt_to_*/*_to_bus APIs don't work there. Those APIs
> are only valid for system memory that is accessible through
> inbound transactions by a PCI bus master.
>
> You can use virt_to_* on an address returned from kmalloc
> or __get_free_pages.
I also don't understand....Could you or someone "invent" these things
kindly give some brief explaination here (especially for the reason how
consistent_alloc() is implemented)? I think it will benefit many PPC
beginner. Thanks very much.
Best regards,
Jacky
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-10-09 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 4:11 General porting question Jacky Lam
2003-10-09 4:24 ` Bret Indrelee
2003-10-09 5:35 ` Matt Porter
2003-10-09 6:18 ` Jacky Lam
2003-10-09 13:38 ` Matt Porter
2003-10-09 15:36 ` Jacky Lam [this message]
2003-10-09 16:37 ` Matt Porter
2003-10-09 17:23 ` Jacky Lam
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='001901c38e7b$0f6ed830$0202a8c0@homevl9biy3v7e' \
--to=jackylam@astri.org \
--cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.