From: "Menon, Nishanth" <nm@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
"Kamat, Nishant" <nskamat@ti.com>
Cc: "linux-arm-kernel@lists.arm.linux.org.uk"
<linux-arm-kernel@lists.arm.linux.org.uk>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Ramirez Luna, Omar" <x00omar@ti.com>,
"Kanigeri, Hari" <h-kanigeri2@ti.com>,
"Guzman Lugo, Fernando" <x0095840@ti.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
"2ameya@gmail.com" <2ameya@gmail.com>
Subject: RE: dma_alloc_coherent fragmentation
Date: Wed, 18 Mar 2009 15:08:19 -0500 [thread overview]
Message-ID: <7A436F7769CA33409C6B44B358BFFF0CFF643729@dlee02.ent.ti.com> (raw)
In-Reply-To: <20090318192442.GB30132@n2100.arm.linux.org.uk>
> -----Original Message-----
> From: Russell King - ARM Linux [mailto:linux@arm.linux.org.uk]
> Sent: Wednesday, March 18, 2009 9:25 PM
> To: Kamat, Nishant
> Cc: linux-arm-kernel@lists.arm.linux.org.uk; Menon, Nishanth; linux-
> omap@vger.kernel.org; Ramirez Luna, Omar; Kanigeri, Hari; Guzman Lugo,
> Fernando; Kevin Hilman; 2ameya@gmail.com
> Subject: Re: dma_alloc_coherent fragmentation
> Make sure you're up to date with fixes to the ioremap code, specifically
> 24f11ec001920f1cfaeeed8e8b55725d900bbb56. This is not in 2.6.28,
> 2.6.29-rc1, 2.6.29-rc2, but is in -rc3 and later. 2.6.29 itself hasn't
> been released yet so I don't know what "seems to happen on 2.6.28 and
> 2.6.29" actually means because its nonsense.
Apologies on the confusion.
For this issue, the pertinent tree would be the master branch of [1] linux-omap tree which is synced to 2.6.29-rc8. And yes, the mentioned commit ID is part of the git log.
Relevant test code and report of the crash is in [2]. Additional observation in [3]
Regards,
Nishanth Menon
Ref:
[1] http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git
[2] http://marc.info/?l=linux-omap&m=123719772811746&w=2
[3] http://marc.info/?l=linux-omap&m=123722460022336&w=2
next prev parent reply other threads:[~2009-03-18 20:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 13:03 dma_alloc_coherent fragmentation Kamat, Nishant
2009-03-18 19:24 ` Russell King - ARM Linux
2009-03-18 20:08 ` Menon, Nishanth [this message]
2009-03-19 6:42 ` Hiroshi DOYU
2009-03-19 9:06 ` Menon, Nishanth
2009-04-22 7:46 ` pramod gurav
2009-04-22 7:50 ` Shilimkar, Santosh
2009-04-22 8:23 ` pramod gurav
2009-04-22 8:51 ` Shilimkar, Santosh
2009-04-22 9:14 ` Gupta, Ramesh
2009-04-22 9:44 ` pramod gurav
2009-04-22 10:09 ` Shilimkar, Santosh
-- strict thread matches above, loose matches on Subject: below --
2009-03-13 15:59 Bridge issue #3! dma_alloc_coherent causing crash - pm branch Kevin Hilman
2009-03-14 4:26 ` Gupta, Ramesh
2009-03-16 9:54 ` dma_alloc_coherent bug? Menon, Nishanth
2009-03-16 17:29 ` Ameya Palande
2009-03-16 19:09 ` Menon, Nishanth
2009-03-17 6:16 ` dma_alloc_coherent fragmentation Menon, Nishanth
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=7A436F7769CA33409C6B44B358BFFF0CFF643729@dlee02.ent.ti.com \
--to=nm@ti.com \
--cc=2ameya@gmail.com \
--cc=h-kanigeri2@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nskamat@ti.com \
--cc=x0095840@ti.com \
--cc=x00omar@ti.com \
/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).