From: Pantelis Antoniou <pantelis.antoniou@gmail•com>
To: linuxppc-embedded@ozlabs•org
Subject: Re: [PATCH] cpm_uart: Made non-console uart work
Date: Fri, 9 Sep 2005 22:59:37 +0300 [thread overview]
Message-ID: <200509092259.37723.pantelis.antoniou@gmail.com> (raw)
In-Reply-To: <19EE6EC66973A5408FBE4CB7772F6F0A02FA20CD@ltnmail.xyplex.com>
On Friday 09 September 2005 22:21, Murch, Christopher wrote:
> We've recently applied the 2.6.13 patch. We're running on an embedded
> platform using 3 of the cpm uart ports on an 8xx cpu. After applying the
> 2.6.13 patch the non-console uarts no longer work. Upon investigation, we
> have found that cpu2cpm_addr() is giving us invalid results for memory
> addresses derived from dma_alloc_coherent(). This causes the cpm to hang.
> We believe that the better approach would be to use the dma address
> supplied by the call to dma_alloc_coherent() instead of trying to convert
> using bus_to_virt() and virt_to_bus(). We believe this is the approach
> taken by other drivers in the 2.6 kernel. Any comments?
> Thanks for your help.
>
Yes, it would be proper. This is a temporary hack.
What is the IMAP_ADDR value?
And where is the consistent pool located at your board?
> -Chris
> cmurch@mrv•com
Regards
Pantelis
next prev parent reply other threads:[~2005-09-09 19:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 19:21 [PATCH] cpm_uart: Made non-console uart work Murch, Christopher
2005-09-09 19:59 ` Pantelis Antoniou [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-12 13:47 Murch, Christopher
2005-08-02 15:24 Vitaly Bordug
2005-08-02 18:35 ` Kumar Gala
2005-08-02 21:26 ` Pantelis Antoniou
2005-08-02 21:39 ` Pantelis Antoniou
2005-08-03 7:16 ` Vitaly Bordug
2005-08-03 16:14 ` Pantelis Antoniou
2005-08-03 14:50 ` Vitaly Bordug
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=200509092259.37723.pantelis.antoniou@gmail.com \
--to=pantelis.antoniou@gmail$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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