linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Hemanth V" <hemanthv@ti.com>
To: linux-mmc@vger.kernel.org, pierre@ossman.eu
Subject: Highmem issues with MMC filesystem
Date: Wed, 17 Mar 2010 19:10:33 +0530	[thread overview]
Message-ID: <037201cac5d7$6c5b8c60$LocalHost@wipblrx0099946> (raw)

Hi All,

We are trying to enable highmem support for OMAP based boards, while doing 
so we are
unable to boot poky UI if the filesystem is in a MMC card.

The poky UI comes up fine if the filesystem is in NAND or NFS,
while with MMC it gives errors like segmentation faults/syntax error while 
there are none.
Seems like read from MMC is getting corrupted.

I tried  the 4 tests which are available as part of mmc_test for highmem, 
all of them seem to PASS.
Wanted to get inputs if there are any known issues with MMC block layer 
handling highmem pages.

Thanks
Hemanth 


             reply	other threads:[~2010-03-17 13:40 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17 13:40 Hemanth V [this message]
2010-03-17 13:49 ` Highmem issues with MMC filesystem Nicolas Pitre
2010-03-17 14:40   ` Hemanth V
2010-03-17 14:58     ` Nicolas Pitre
2010-03-18  9:23       ` Russell King - ARM Linux
2010-03-18 11:15         ` saeed bishara
2010-03-18 11:24           ` Russell King - ARM Linux
2010-03-18 13:20             ` Nicolas Pitre
2010-03-18 13:30               ` Shilimkar, Santosh
2010-03-18 14:19                 ` Russell King - ARM Linux
2010-03-18 14:41                   ` Hemanth V
2010-03-18 16:17                   ` Nicolas Pitre
2010-03-18 17:51                     ` Russell King - ARM Linux
2010-03-18 19:24                       ` Nicolas Pitre
2010-03-19  1:55                     ` Jamie Lokier
2010-03-19 13:17                       ` Nicolas Pitre
2010-03-19 13:27                         ` Russell King - ARM Linux
2010-03-19 17:59                           ` Nicolas Pitre
2010-03-19 18:26                             ` Catalin Marinas
2010-03-19 18:56                               ` Nicolas Pitre
2010-03-19 14:28                         ` Hemanth V
2010-03-19 14:36                           ` Shilimkar, Santosh
2010-03-19 14:45                             ` Russell King - ARM Linux
2010-03-19 14:41               ` Catalin Marinas
2010-03-19 14:46                 ` Russell King - ARM Linux
2010-03-19 14:52                   ` Catalin Marinas
2010-03-19 14:54                     ` Russell King - ARM Linux
2010-03-19 16:46                       ` Catalin Marinas
2010-03-19 16:52                         ` Russell King - ARM Linux
2010-03-19 17:47                     ` Nicolas Pitre
2010-03-19 18:27                       ` Nicolas Pitre
2010-03-19 18:38                         ` Russell King - ARM Linux
2010-03-19 18:51                           ` Nicolas Pitre
2010-03-22 11:45                             ` Russell King - ARM Linux
2010-03-22 12:36                               ` Nicolas Pitre
2010-03-19 20:14                         ` Nicolas Pitre
2010-03-22  9:05                           ` Hemanth V
2010-03-22 12:50                             ` Nicolas Pitre
2010-03-18 13:42             ` saeed bishara

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='037201cac5d7$6c5b8c60$LocalHost@wipblrx0099946' \
    --to=hemanthv@ti.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=pierre@ossman.eu \
    /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).