On Sun, Jan 4, 2009 at 12:46 PM, Raseel wrote:
> On 04-Jan-09, at 12:27 PM, "rohit vashist"
> wrote:
>
> Hi
>>
>> Can we know the disk space of any unmounted device using any shell command
>> or any?
>>
>> --
>> Regards
>> Rohit
>>
>
> If the device is unmounted, linux has no notion of it's exi
On 12:27 Sun 04 Jan , rohit vashist wrote:
> Hi
>
> Can we know the disk space of any unmounted device using any shell command
> or any?
# fdisk -l
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecar...@nl.linux.org
Please read the FAQ at http://kern
On 04-Jan-09, at 12:27 PM, "rohit vashist"
wrote:
Hi
Can we know the disk space of any unmounted device using any shell
command or any?
--
Regards
Rohit
If the device is unmounted, linux has no notion of it's existence.
Atleast not enough to know non- hardware specific details.
Tha
Hi
Can we know the disk space of any unmounted device using any shell command
or any?
--
Regards
Rohit
The entire series of V4L internals is documented here:
http://lwn.net/Articles/203924/
(and many other links contained within)
and the API documented here:
http://v4l2spec.bytesex.org/spec/book1.htm
And even IVTV have been rewritten to conform to V4L API standards (and
all done in userspace as
On Sat, Jan 3, 2009 at 1:52 AM, niamathullah sharief
wrote:
> Hello
>
> I am looking for a very basic "c" example that will connect to a V4L2 webcam
> and capture a frame. I am basically looking to write a class which I can use
> to create a new Webcam object. which will grab a frame from the came
ah...two points:
a. that the timer is NOT per-CPU. but a global entity. but many
CPU can own the timer - as deduced from timer->base structure, but
only one is running - based on timer->runng_base. correct? so
logically the logic of clean deletion (making sure not being in used
in anothe
On Sun, Jan 4, 2009 at 4:06 AM, Alexander Potashev wrote:
> On 15:14 Sat 03 Jan , Peter Teoh wrote:
>> Ok, how about this: completely suspending all I/O can be done. two
>> possible answer:
>>
>> 1. suspension on root device: reboot using a LiveCD, and mount the
>> rootfs as readonly.
On 15:14 Sat 03 Jan , Peter Teoh wrote:
> Ok, how about this: completely suspending all I/O can be done. two
> possible answer:
>
> 1. suspension on root device: reboot using a LiveCD, and mount the
> rootfs as readonly.
> 2. suspension on non-root device: unmount it first - after
On Sat, 3 Jan 2009, Alexander Potashev wrote:
> Hello, Robert!
>
> On 10:12 Sat 03 Jan , Robert P. J. Day wrote:
> > the last i heard, while ioctl's aren't going away any time soon,
> > they're deprecated in favour of ... uh, files under /sys? am i
>
> How is it possible to replace ioctls b
Hello, Robert!
On 10:12 Sat 03 Jan , Robert P. J. Day wrote:
> the last i heard, while ioctl's aren't going away any time soon,
> they're deprecated in favour of ... uh, files under /sys? am i
How is it possible to replace ioctls by files in /sys? Should my kernel
module create a file in /
El Sat, Jan 03, 2009 at 11:13:45PM +0800 Peter Teoh ha dit:
> On Sat, Jan 3, 2009 at 6:20 PM, Microbit_Ubuntu
> wrote:
> > Hello all,
> >
> > I've just joined up with this list, so this is mainly an initial "ping"
> > to see if I can post.
> > I'm a newbie studying embedded linux on an Olimex SAM
On Sat, Jan 3, 2009 at 5:45 PM, niamathullah sharief
wrote:
> i know that "ioctl()" is an system callbut can anyone tell me how it
> works...from where it called?
these are the things u need to know:
a. ioctl() is a syscall.
b. from userspace ioctl(), it will jump to sys_ioctl(), in
On Sat, Jan 3, 2009 at 6:20 PM, Microbit_Ubuntu
wrote:
> Hello all,
>
> I've just joined up with this list, so this is mainly an initial "ping"
> to see if I can post.
> I'm a newbie studying embedded linux on an Olimex SAM9-L9260 target,
> cross compiling on Ubuntu 8.10.
>
> Eventually I'd like t
On Sat, 3 Jan 2009, Rohit Sharma wrote:
> ioctls are also known as generic system calls. Its a simple switch
> case implementation inside a device.
> you send command and argument through ioctls as parameters.
> Its a way you use to interact with the device itself.
>
> for using it just open the d
ioctls are also known as generic system calls. Its a simple switch
case implementation inside a device.
you send command and argument through ioctls as parameters.
Its a way you use to interact with the device itself.
for using it just open the device and use its fd to invoke ioctls.
for eg.
fd
On Sat, Jan 3, 2009 at 1:08 AM, rohit vashist
wrote:
>
>
> On Sat, Jan 3, 2009 at 2:51 AM, Greg Freemyer
> wrote:
>>
>> On Fri, Jan 2, 2009 at 3:34 PM, rohit vashist
>> wrote:
>> > Hi
>> >
>> > I went through the code of iostat.In the ninth field it gives the count
>> > of
>> > number of I/O,but
If you are new to Kernel Programming then you should go to The Latest
version of The Linux Kernel Module Programming Guide
just google for it
On Sat, Jan 3, 2009 at 3:15 PM, niamathullah sharief
wrote:
> i know that "ioctl()" is an system callbut can anyone tell me how it
> works...from whe
i know that "ioctl()" is an system callbut can anyone tell me how it
works...from where it called?
Add more friends to your messenger and enjoy! Go to
http://messenger.yahoo.com/invite/
Hello all,
I've just joined up with this list, so this is mainly an initial "ping"
to see if I can post.
I'm a newbie studying embedded linux on an Olimex SAM9-L9260 target,
cross compiling on Ubuntu 8.10.
Eventually I'd like to ask a couple of questions. On the subject of
timer INTs, I actually
On Sat, Jan 3, 2009 at 12:35 AM, Peter Teoh wrote:
> On Fri, Jan 2, 2009 at 5:55 PM, Shyam Burkule wrote:
>> Hi All,
>>
>> In Understanding The Linux Kernel, 3rd edition I read that
>> *scheduler_tick()* is invoked once every tick to perform some operations
>
> Yes, it is still valid and happens
21 matches
Mail list logo
