From: g.liakhovetski@gmx.de (Guennadi Liakhovetski)
To: linux-arm-kernel@lists.infradead.org
Subject: dma_declare_coherent_memory() again.
Date: Mon, 21 Feb 2011 16:37:00 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.1102211602140.26977@axis700.grange> (raw)
Hi All
AFAIU, dma_declare_coherent_memory() is still present on the following
platforms:
arch/arm/mach-mx3/mach-pcm037.c
arch/arm/mach-mx3/mach-mx31moboard.c
arch/arm/mach-shmobile/board-ap4evb.c
arch/arm/mach-shmobile/board-mackerel.c (latter 2 via
drivers/media/video/sh_mobile_ceu_camera.c)
and there are no pending patches to fix them for 2.6.38, is this right? If
there are no realistic plans for proper memory reservation on ARM in
2.6.38, shall I just submit patches to disable those calls on the above
platforms and hope, that the user manages to get RAM without boot-time
reservation? Or is a definite failure preferred?
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
next reply other threads:[~2011-02-21 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 15:37 Guennadi Liakhovetski [this message]
2011-02-21 20:25 ` dma_declare_coherent_memory() again Philippe Rétornaz
2011-02-22 8:41 ` Uwe Kleine-König
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=Pine.LNX.4.64.1102211602140.26977@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=linux-arm-kernel@lists.infradead.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