From: martinez.javier@gmail.com (Javier Martinez Canillas)
To: kernelnewbies@lists.kernelnewbies.org
Subject:
Date: Mon, 15 Oct 2012 13:20:00 +0200 [thread overview]
Message-ID: <CAAwP0s19T_5HiyN9KQTLUcbhOdLrLXR8XXiZ4vCFowJBU5Na_A@mail.gmail.com> (raw)
In-Reply-To: <CAKzXvN-VUncJOiqkrdotKJRc4R6OxpbdzKL5JxnLyWnO_JnsHA@mail.gmail.com>
On Mon, Oct 15, 2012 at 12:53 PM, Niroj Pokhrel <nirojpokhrel@gmail.com> wrote:
> Thank Matthias!!!
> I have tried using printk . What I really want to do now is to implement the
> methods I have written by calling from the user space. Like I want to read
> or write to the character devices via user space.
>
Hi Niroj,
Please don't top post, it is not polite since forces readers to scroll
to the bottom to gain some context about the conversation.
> On Mon, Oct 15, 2012 at 3:49 PM, Matthias Brugger
> <matthias.bgg@googlemail.com> wrote:
>>
>> Hi,
>>
>>
>> On 10/15/2012 11:24 AM, Niroj Pokhrel wrote:
>>>
>>> Hi,
>>> I'm new to linux and kernel . I'm ongoing with the linux device drivers.
>>> I've followed the the book LDD but i'm lost about how to call my
>>> driver's specific method from the user space.
>>> Eg: if have developed a character device and inserted the module then
>>> how can i make sure that when I read or write that it implement the
>>> functions via the methods i have implemented in my module.
>>
>>
>> the most easy way would be to put some printk output in your read/write
>> functions of your driver. So with cat/echo from userspace you should be able
>> to verify your implementation.
>>
>> Regards,
>> Matthias
>>
>>>
>>> --
>>> Niroj Pokhrel
>>> NIT Jamshedpur,
>>> B.Tech,Electronics and Communication
>>>
>>>
>>> _______________________________________________
>>> Kernelnewbies mailing list
>>> Kernelnewbies at kernelnewbies.org
>>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>>
>>
>
>
>
> --
> Niroj Pokhrel
> NIT Jamshedpur,
> B.Tech,Electronics and Communication
>
There is no need to implement anything in user-space.
If your char dev driver has been correctly implemented and registered
then the standard file operation syscalls can be used to access the
device. The Linux kernel virtual filesystem will use the information
on the character device node (major number) to know which struct
file_operations (and hence file operations callbacks) has to be used.
Hope it helps,
--
Javier
prev parent reply other threads:[~2012-10-15 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 9:24 No subject Niroj Pokhrel
2012-10-15 10:19 ` Matthias Brugger
2012-10-15 10:53 ` Niroj Pokhrel
2012-10-15 11:12 ` Kumar amit mehta
2012-10-15 11:20 ` Javier Martinez Canillas [this message]
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=CAAwP0s19T_5HiyN9KQTLUcbhOdLrLXR8XXiZ4vCFowJBU5Na_A@mail.gmail.com \
--to=martinez.javier@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).