On Tue, Sep 29, 2009 at 3:34 PM, Leonidas . wrote:
>
>
> On Tue, Sep 29, 2009 at 3:31 PM, Nagaprabhanjan Bellari <
> nagp@gmail.com> wrote:
>
>> If you take /proc filesystem for example, you can write something to it
>> and can read something from it depending on what you last wrote.
>> -nagp
On Tue, Sep 29, 2009 at 3:31 PM, Nagaprabhanjan Bellari
wrote:
> If you take /proc filesystem for example, you can write something to it and
> can read something from it depending on what you last wrote.
> -nagp
>
> On Fri, Sep 18, 2009 at 9:46 PM, Peter Teoh wrote:
>
>> On Fri, Sep 18, 2009 at 9:
If you take /proc filesystem for example, you can write something to it and
can read something from it depending on what you last wrote.
-nagp
On Fri, Sep 18, 2009 at 9:46 PM, Peter Teoh wrote:
> On Fri, Sep 18, 2009 at 9:07 PM, Leonidas . wrote:
> >
> >
> > On Fri, Sep 18, 2009 at 5:36 AM, Pet
On Fri, Sep 18, 2009 at 5:36 AM, Peter Teoh wrote:
> >
> > I think you are talking about ioctl on a single minor number device, my
> > concern is more
> > about choice here. Meaning whether using ioctls with different commands
> on a
> > single dev
> > node be preferable to issuing reads on 3 dif
>
> I think you are talking about ioctl on a single minor number device, my
> concern is more
> about choice here. Meaning whether using ioctls with different commands on a
> single dev
> node be preferable to issuing reads on 3 different minor number device
> nodes.
>
>
> -Leo.
>
>
just take the
On Fri, Sep 18, 2009 at 9:07 PM, Leonidas . wrote:
>
>
> On Fri, Sep 18, 2009 at 5:36 AM, Peter Teoh wrote:
>>
>> >
>> > I think you are talking about ioctl on a single minor number device, my
>> > concern is more
>> > about choice here. Meaning whether using ioctls with different commands
>> > o
2009/9/18 Leonidas . :
>
>
> On Fri, Sep 18, 2009 at 7:32 AM, Pei Lin wrote:
>>
>> 2009/9/17 Leonidas . :
>> >
>> >
>> > Hi list,
>> >
>> > I know that introducing/using new ioctls is frawned upon by the
>> > community.
>> > They might still be needed for controlling various hw parameters, Just
>>
On Fri, Sep 18, 2009 at 7:32 AM, Pei Lin wrote:
> 2009/9/17 Leonidas . :
> >
> >
> > Hi list,
> >
> > I know that introducing/using new ioctls is frawned upon by the
> community.
> > They might still be needed for controlling various hw parameters, Just
> > wanted
> > to understand the data trans
2009/9/17 Leonidas . :
>
>
> Hi list,
>
> I know that introducing/using new ioctls is frawned upon by the community.
> They might still be needed for controlling various hw parameters, Just
> wanted
> to understand the data transfer side of ioctls with a use case.
>
> E.g. My kernel module needs to
sorrythe API is usb_read() etc - essentially these are from libusb.so:
usb_bulk_read
usb_bulk_write
usb_busses
usb_claim_interface
usb_clear_halt
usb_close
usb_control_msg
usb_device
usb_find_busses
usb_find_devices
usb_get_busses
usb_get_descriptor
usb_get_descriptor_by_endpoint
usb_get_stri
what kind of device is that? USB/PCI etc based? for many USB
devices, u just need userspace tools. For eg:
1. libusb-devel (or libusb-devdepending on the distros), or
libpci etcfor writing userspace application to talk to the device.
2. add udev rules. (for eg, this url:
http:
Hi list,
I know that introducing/using new ioctls is frawned upon by the community.
They might still be needed for controlling various hw parameters, Just
wanted
to understand the data transfer side of ioctls with a use case.
E.g. My kernel module needs to pass a buffer of 1-2Mb to userspace
when
12 matches
Mail list logo
