public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "chandrasheakhar singh" <cp_singh@faith.co.jp>
To: linux-omap-open-source@linux.omap.com
Subject: Allocating user space memory inside LKM
Date: Wed, 7 Dec 2005 10:08:21 +0900	[thread overview]
Message-ID: <009d01c5facb$7be7a190$4b13a80a@cpsingh> (raw)

Dear all,

I'm working on a linux kernel 2.6.11 for h4 (OMAP 2420). I just want to get some memory
of user space inside kernel module. As when I'm sending PCM data to audio driver from kernel
module(KM) through audio_write (...) of driver API it gives  error as:

Audio: CopyFrom User failed.

In the 2.6.11 kernel  particularly for H4  target how to get some user space memory as 
for this target this alloc_user_space() function is not available.

Any light on this issue will be great help.

Best Regards
chandrasheakhar


















========================
\    chandrashekhar singh
 \   cp_singh@faith.co.jp
 /   Faith Inc. Tokyo
/  www.faith.co.jp
========================

                 reply	other threads:[~2005-12-07  1:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='009d01c5facb$7be7a190$4b13a80a@cpsingh' \
    --to=cp_singh@faith.co.jp \
    --cc=linux-omap-open-source@linux.omap.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