On Mon, 25 Feb 2008, Arvid Brodin wrote:
> I need to write messages > 1023 characters long to the console from a
> module*. printk() is limited to 1023 characters, and splitting the message
> over several printk()'s results in a line break and "Month hh:mm:ss host
> kernel:" being inserted in
On Mon, 25 Feb 2008, Arvid Brodin wrote:
I need to write messages 1023 characters long to the console from a
module*. printk() is limited to 1023 characters, and splitting the message
over several printk()'s results in a line break and Month hh:mm:ss host
kernel: being inserted in my
On Thu, 14 Feb 2008, Mika Lawando wrote:
> Jasper Bryant-Greene schrieb:
>> On Thu, 2008-02-14 at 10:30 +0100, rzryyvzy wrote:
>>
>>> /dev/null is often very useful, specially if programs force to save data in
>>> some file. But some programs like to creates different temporary file
>>> names,
On Thu, 14 Feb 2008, Mika Lawando wrote:
Jasper Bryant-Greene schrieb:
On Thu, 2008-02-14 at 10:30 +0100, rzryyvzy wrote:
/dev/null is often very useful, specially if programs force to save data in
some file. But some programs like to creates different temporary file
names, so /dev/null
On Wed, 13 Feb 2008, [iso-8859-1] Ilpo Järvinen wrote:
> On Wed, 13 Feb 2008, linux-os (Dick Johnson) wrote:
>>
>> On Wed, 13 Feb 2008, [iso-8859-1] Ilpo Järvinen wrote:
>>
>>> They're defined later on in the same file with bodies and
>>> nothingin between
On Wed, 13 Feb 2008, [iso-8859-1] Ilpo Järvinen wrote:
> They're defined later on in the same file with bodies and
> nothingin between needs them.
>
> Signed-off-by: Ilpo Järvinen <[EMAIL PROTECTED]>
> ---
> include/linux/coda_linux.h |3 ---
> 1 files changed, 0 insertions(+), 3 deletions(-)
On Wed, 13 Feb 2008, [iso-8859-1] Ilpo Järvinen wrote:
They're defined later on in the same file with bodies and
nothingin between needs them.
Signed-off-by: Ilpo Järvinen [EMAIL PROTECTED]
---
include/linux/coda_linux.h |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff
On Wed, 13 Feb 2008, [iso-8859-1] Ilpo Järvinen wrote:
On Wed, 13 Feb 2008, linux-os (Dick Johnson) wrote:
On Wed, 13 Feb 2008, [iso-8859-1] Ilpo Järvinen wrote:
They're defined later on in the same file with bodies and
nothingin between needs them.
Signed-off-by: Ilpo Järvinen [EMAIL
On Fri, 8 Feb 2008, Mark Hounschell wrote:
> linux-os (Dick Johnson) wrote:
>>
>> The correct word should be "invalid," in spite of
>> the fact that the SCSI committee used invalid syntax.
>>
>> Alan is right. There is nothing illegal in the kernel
>
On Fri, 8 Feb 2008, Mark Hounschell wrote:
linux-os (Dick Johnson) wrote:
The correct word should be invalid, in spite of
the fact that the SCSI committee used invalid syntax.
Alan is right. There is nothing illegal in the kernel
and if there is, it must be removed as soon
The correct word should be "invalid," in spite of
the fact that the SCSI committee used invalid syntax.
Alan is right. There is nothing illegal in the kernel
and if there is, it must be removed as soon as it
is discovered!
On Fri, 8 Feb 2008, James Bottomley wrote:
>
> On Fri, 2008-02-08 at
The correct word should be invalid, in spite of
the fact that the SCSI committee used invalid syntax.
Alan is right. There is nothing illegal in the kernel
and if there is, it must be removed as soon as it
is discovered!
On Fri, 8 Feb 2008, James Bottomley wrote:
On Fri, 2008-02-08 at
-14 is EFAULT. This means that there was some access
to memory that was not mapped.
In the future, check /usr/include/asm/errno.h for exit
codes. Of course in user-space they are positive with
-1 being return from the function-call and errno being
set to this code. In the kernel, they are
-14 is EFAULT. This means that there was some access
to memory that was not mapped.
In the future, check /usr/include/asm/errno.h for exit
codes. Of course in user-space they are positive with
-1 being return from the function-call and errno being
set to this code. In the kernel, they are
On Fri, 18 Jan 2008, Theodore Tso wrote:
> On Thu, Jan 17, 2008 at 04:31:48PM -0800, Bryan Henderson wrote:
>> But I heard some years ago from a disk drive engineer that that is a myth
>> just like the rotational energy thing. I added that to the discussion,
>> but admitted that I haven't
On Fri, 18 Jan 2008, mokhtar wrote:
>
> Hi
>
> What are the different solution to make a user process communicate with a
> kernel modules?
>
> Whatis the the advantages and disadvanteges of each solutions ?
>
ioctl() is the universal Unix mechanism for control of drivers
(modules). open(),
On Fri, 18 Jan 2008, Theodore Tso wrote:
On Thu, Jan 17, 2008 at 04:31:48PM -0800, Bryan Henderson wrote:
But I heard some years ago from a disk drive engineer that that is a myth
just like the rotational energy thing. I added that to the discussion,
but admitted that I haven't actually
On Fri, 18 Jan 2008, mokhtar wrote:
Hi
What are the different solution to make a user process communicate with a
kernel modules?
Whatis the the advantages and disadvanteges of each solutions ?
ioctl() is the universal Unix mechanism for control of drivers
(modules). open(), close(),
On Thu, 10 Jan 2008, Jan Marek wrote:
> Hello lkml,
>
> I have problem with my computer: I have motherboard with AMD690G chipset
> and nVidia VGA card. But I cannot set BIOS, to assign for VGA unique
> IRQ. VGA card is sharing IRQ with two ohci_hcd (USB 1.1 controllers).
> But when I want use
On Thu, 10 Jan 2008, Jan Marek wrote:
Hello lkml,
I have problem with my computer: I have motherboard with AMD690G chipset
and nVidia VGA card. But I cannot set BIOS, to assign for VGA unique
IRQ. VGA card is sharing IRQ with two ohci_hcd (USB 1.1 controllers).
But when I want use for X
On Wed, 9 Jan 2008, Miklos Szeredi wrote:
> FASTCALL is defined empty in -mm, but UML is not compiled with
> -mregparm=3 and so this breaks things (I noticed problems with
> rwsem_down_write_failed).
>
> Tried recompiling UML with -mregparm=3, but that resulted in a strange
> failure immediately
On Wed, 9 Jan 2008, Miklos Szeredi wrote:
FASTCALL is defined empty in -mm, but UML is not compiled with
-mregparm=3 and so this breaks things (I noticed problems with
rwsem_down_write_failed).
Tried recompiling UML with -mregparm=3, but that resulted in a strange
failure immediately after
On Fri, 21 Dec 2007, Lennart Sorensen wrote:
> On Thu, Dec 20, 2007 at 04:27:37PM -0500, linux-os (Dick Johnson) wrote:
>> I need to get rid of -mregparm=3 on gcc's command line. It
>> is completely incompatible with the standard calling conventions
>> used in all our as
On Fri, 21 Dec 2007, Lennart Sorensen wrote:
> On Thu, Dec 20, 2007 at 05:56:19PM -0500, linux-os (Dick Johnson) wrote:
>> Okay. Thanks! I need to do that.
>
> On the (now somewhat old) 2.6.18 kernel I use it is an option under
> "Processor type and features" ca
On Thu, 20 Dec 2007, Bodo Eggert wrote:
> linux-os (Dick Johnson) <[EMAIL PROTECTED]> wrote:
>> On Thu, 20 Dec 2007, Sam Ravnborg wrote:
>
>>>> It never gets to the printk(). You were right about the
>>>> compilation. Somebody changed the ker
On Thu, 20 Dec 2007, Bodo Eggert wrote:
linux-os (Dick Johnson) [EMAIL PROTECTED] wrote:
On Thu, 20 Dec 2007, Sam Ravnborg wrote:
It never gets to the printk(). You were right about the
compilation. Somebody changed the kernel to compile with
parameter passing in REGISTERS! This means
On Fri, 21 Dec 2007, Lennart Sorensen wrote:
On Thu, Dec 20, 2007 at 05:56:19PM -0500, linux-os (Dick Johnson) wrote:
Okay. Thanks! I need to do that.
On the (now somewhat old) 2.6.18 kernel I use it is an option under
Processor type and features called Use register arguments, but yeah
On Fri, 21 Dec 2007, Lennart Sorensen wrote:
On Thu, Dec 20, 2007 at 04:27:37PM -0500, linux-os (Dick Johnson) wrote:
I need to get rid of -mregparm=3 on gcc's command line. It
is completely incompatible with the standard calling conventions
used in all our assembly-language files in our
On Thu, 20 Dec 2007, Sam Ravnborg wrote:
> On Thu, Dec 20, 2007 at 04:27:37PM -0500, linux-os (Dick Johnson) wrote:
>>
>> On Thu, 20 Dec 2007, Sam Ravnborg wrote:
>>
>>>>
>>>> It never gets to the printk(). You were right about the
>>>
On Thu, 20 Dec 2007, Roland Dreier wrote:
> > It doesn't seem to be something in .config. Do you know how to
> > reconfigure to get parameter passing put back like it was? Our
> > production applications have lots of assembly-language files
> > and I'm sure we are not going to be able to change
On Thu, 20 Dec 2007, Lennart Sorensen wrote:
> On Thu, Dec 20, 2007 at 11:13:19AM -0500, linux-os (Dick Johnson) wrote:
>> It never gets to the printk(). You were right about the
>> compilation. Somebody changed the kernel to compile with
>> parameter passing in
On Thu, 20 Dec 2007, Sam Ravnborg wrote:
>>
>> It never gets to the printk(). You were right about the
>> compilation. Somebody changed the kernel to compile with
>> parameter passing in REGISTERS! This means that EVERYTHING
>> needs to be compiled the same way, 'C' calling conventions
>> were
On Thu, 20 Dec 2007, Lennart Sorensen wrote:
> On Wed, Dec 19, 2007 at 03:56:45PM -0500, linux-os (Dick Johnson) wrote:
>>
>> On Wed, 19 Dec 2007, Lennart Sorensen wrote:
>>
>>> On Wed, Dec 19, 2007 at 03:10:28PM -0500, linux-os (Dick Johnson) wrote:
>>>&
On Thu, 20 Dec 2007, Lennart Sorensen wrote:
On Wed, Dec 19, 2007 at 03:56:45PM -0500, linux-os (Dick Johnson) wrote:
On Wed, 19 Dec 2007, Lennart Sorensen wrote:
On Wed, Dec 19, 2007 at 03:10:28PM -0500, linux-os (Dick Johnson) wrote:
Here is a so-called BUG when trying to insert
On Thu, 20 Dec 2007, Lennart Sorensen wrote:
On Thu, Dec 20, 2007 at 11:13:19AM -0500, linux-os (Dick Johnson) wrote:
It never gets to the printk(). You were right about the
compilation. Somebody changed the kernel to compile with
parameter passing in REGISTERS! This means that EVERYTHING
On Thu, 20 Dec 2007, Sam Ravnborg wrote:
It never gets to the printk(). You were right about the
compilation. Somebody changed the kernel to compile with
parameter passing in REGISTERS! This means that EVERYTHING
needs to be compiled the same way, 'C' calling conventions
were not good
On Thu, 20 Dec 2007, Roland Dreier wrote:
It doesn't seem to be something in .config. Do you know how to
reconfigure to get parameter passing put back like it was? Our
production applications have lots of assembly-language files
and I'm sure we are not going to be able to change all
On Thu, 20 Dec 2007, Sam Ravnborg wrote:
On Thu, Dec 20, 2007 at 04:27:37PM -0500, linux-os (Dick Johnson) wrote:
On Thu, 20 Dec 2007, Sam Ravnborg wrote:
It never gets to the printk(). You were right about the
compilation. Somebody changed the kernel to compile with
parameter passing
On Wed, 19 Dec 2007, Jan Engelhardt wrote:
>
> On Dec 19 2007 15:10, linux-os (Dick Johnson) wrote:
>
>
>> I got rid of __init and anything else that I thought could cause the fault,
>
> I anticipate the day removing __init causes a breakage, heh.
> I mean, if all i
On Wed, 19 Dec 2007, Lennart Sorensen wrote:
> On Wed, Dec 19, 2007 at 03:10:28PM -0500, linux-os (Dick Johnson) wrote:
>>
>>
>> Here is a so-called BUG when trying to insert the following
>> module into the kernel (2.6.22.1).
>>
>>
>> BUG: unab
Here is a so-called BUG when trying to insert the following
module into the kernel (2.6.22.1).
BUG: unable to handle kernel paging request at virtual address 6814ec83
printing eip:
c016d013
*pde =
Oops: [#1]
PREEMPT SMP
Modules linked in: MemDev parport_pc lp parport nfsd
On Tue, 18 Dec 2007, Robert Hancock wrote:
> shashi59 wrote:
>> I am newbie for Linux Kernel.How can I read the memory area like the range
>> between to .Directly i read that area it shows some error
>> like this "unable to handle kernel paging request at virtual address
>>
On Tue, 18 Dec 2007, Robert Hancock wrote:
shashi59 wrote:
I am newbie for Linux Kernel.How can I read the memory area like the range
between to .Directly i read that area it shows some error
like this unable to handle kernel paging request at virtual address
. So,I
Here is a so-called BUG when trying to insert the following
module into the kernel (2.6.22.1).
BUG: unable to handle kernel paging request at virtual address 6814ec83
printing eip:
c016d013
*pde =
Oops: [#1]
PREEMPT SMP
Modules linked in: MemDev parport_pc lp parport nfsd
On Wed, 19 Dec 2007, Lennart Sorensen wrote:
On Wed, Dec 19, 2007 at 03:10:28PM -0500, linux-os (Dick Johnson) wrote:
Here is a so-called BUG when trying to insert the following
module into the kernel (2.6.22.1).
BUG: unable to handle kernel paging request at virtual address 6814ec83
On Wed, 19 Dec 2007, Jan Engelhardt wrote:
On Dec 19 2007 15:10, linux-os (Dick Johnson) wrote:
I got rid of __init and anything else that I thought could cause the fault,
I anticipate the day removing __init causes a breakage, heh.
I mean, if all in-tree modules and LDD3 use
On Fri, 14 Dec 2007, David P. Reed wrote:
> Avi Kivity wrote:
>> kvm will forward a virtual machine's writes to port 0x80 to the real
>> port. The reason is that the write is much faster than exiting and
>> emulating it; the difference is measurable when compiling kernels.
>>
>> Now if the
On Fri, 14 Dec 2007, David P. Reed wrote:
Avi Kivity wrote:
kvm will forward a virtual machine's writes to port 0x80 to the real
port. The reason is that the write is much faster than exiting and
emulating it; the difference is measurable when compiling kernels.
Now if the cause is simply
On Wed, 12 Dec 2007, linux-os (Dick Johnson) wrote:
>
> On Wed, 12 Dec 2007, David P. Reed wrote:
>
>> Who has attitude problems here? I have indeed learned a lot about assholes.
I hastily responded to this with some invective of my own.
I wish to publicly apologize because I
On Wed, 12 Dec 2007, linux-os (Dick Johnson) wrote:
On Wed, 12 Dec 2007, David P. Reed wrote:
Who has attitude problems here? I have indeed learned a lot about assholes.
I hastily responded to this with some invective of my own.
I wish to publicly apologize because I was just a bit hasty
On Wed, 12 Dec 2007, David P. Reed wrote:
> Who has attitude problems here? I have indeed learned a lot about assholes.
>
> linux-os (Dick Johnson) wrote:
>> Yep. We are all wrong. You come out of nowhere and claim to
>> be right. Goodbye.
>>
Hmmm, I gave you every o
On Wed, 12 Dec 2007, Rene Herman wrote:
> Hi everyone.
>
> That was a succesful request, thanks to all who responded. This message also
> just now went out with all the respondents in CC but I believe that copy
> isn't making the list, so here's one without...
>
> In total you provided 60
On Wed, 12 Dec 2007, Rene Herman wrote:
> On 12-12-07 13:59, linux-os (Dick Johnson) wrote:
>
>> On Tue, 11 Dec 2007, [utf-8] Alejandro Riveira Fern?ndez wrote:
>
>>> On my AMD 3800 X2 (2000MHz) ULi M1697 2.6.24-rc5 i get:
>>>
>>> cycles:
On Tue, 11 Dec 2007, David P. Reed wrote:
> 1) I found in a book, the Undocumented PC, that I have lying around that
> the "pause" recommended for some old adapter chips on the ISA bus was 1
> usec. The book carefully points out on various models of PCs how many
> short jumps are required to
On Wed, 12 Dec 2007, Rene Herman wrote:
On 12-12-07 13:59, linux-os (Dick Johnson) wrote:
On Tue, 11 Dec 2007, [utf-8] Alejandro Riveira Fern?ndez wrote:
On my AMD 3800 X2 (2000MHz) ULi M1697 2.6.24-rc5 i get:
cycles: out 1844674407370808, in 1844674407369087
It is not constant
On Tue, 11 Dec 2007, David P. Reed wrote:
1) I found in a book, the Undocumented PC, that I have lying around that
the pause recommended for some old adapter chips on the ISA bus was 1
usec. The book carefully points out on various models of PCs how many
short jumps are required to
On Wed, 12 Dec 2007, Rene Herman wrote:
Hi everyone.
That was a succesful request, thanks to all who responded. This message also
just now went out with all the respondents in CC but I believe that copy
isn't making the list, so here's one without...
In total you provided 60 reports which
On Wed, 12 Dec 2007, David P. Reed wrote:
Who has attitude problems here? I have indeed learned a lot about assholes.
linux-os (Dick Johnson) wrote:
Yep. We are all wrong. You come out of nowhere and claim to
be right. Goodbye.
Hmmm, I gave you every opportunity to back off your pretense
On Tue, 11 Dec 2007, David P. Reed wrote:
>
>
> Alan Cox wrote:
>>
>> The vga driver is somewhat misnamed. In console mode we handle everything
>> back to MDA/HGA and some HGA adapters do need delays.
>>
>>
> No they don't. I really, really, really know this for a fact. I wrote
> ASM drivers
On Tue, 11 Dec 2007, David Newall wrote:
> Rene Herman wrote:
>> This particular discussion isn't about anything in general but solely
>> about the delay an outb_p gives you on x86 since what is under
>> discussion is not using an output to port 0x80 on that platform to
>> generate it.
>
> That
On Tue, 11 Dec 2007, David Newall wrote:
Rene Herman wrote:
This particular discussion isn't about anything in general but solely
about the delay an outb_p gives you on x86 since what is under
discussion is not using an output to port 0x80 on that platform to
generate it.
That could be
On Tue, 11 Dec 2007, David P. Reed wrote:
Alan Cox wrote:
The vga driver is somewhat misnamed. In console mode we handle everything
back to MDA/HGA and some HGA adapters do need delays.
No they don't. I really, really, really know this for a fact. I wrote
ASM drivers for every early
On Fri, 7 Dec 2007, Dave Jones wrote:
> On Fri, Dec 07, 2007 at 08:15:42AM -0500, linux-os (Dick Johnson) wrote:
>
> > Dec 7 04:05:55 chaos kernel: sd 0:0:1:0: [sdb] Add. Sense: Peripheral
> > device write fault
>
> This sounds more like a hardware
On linux-2.6.22.1, executing the following script
while the mailer is writing to /var/spool/mail/linux-os.
#!/bin/bash
while true ;
do
>/var/spool/mail/linux-os;
sleep 1;
done
...will cause the following errors to occur.
Dec 7 04:05:55 chaos kernel: sd 0:0:1:0: [sdb] Sense Key :
On linux-2.6.22.1, executing the following script
while the mailer is writing to /var/spool/mail/linux-os.
#!/bin/bash
while true ;
do
/var/spool/mail/linux-os;
sleep 1;
done
...will cause the following errors to occur.
Dec 7 04:05:55 chaos kernel: sd 0:0:1:0: [sdb] Sense Key :
On Fri, 7 Dec 2007, Dave Jones wrote:
On Fri, Dec 07, 2007 at 08:15:42AM -0500, linux-os (Dick Johnson) wrote:
Dec 7 04:05:55 chaos kernel: sd 0:0:1:0: [sdb] Add. Sense: Peripheral
device write fault
This sounds more like a hardware problem.
Dave
There was an attempt to write
On Tue, 4 Dec 2007, John Sigler wrote:
> Dick Johnson wrote:
>
>> You can't just touch a scope-probe to the PCI
>> clock pin and clip the scope-probe grounding
>> lead to a convenient "ground" to make these
>> measurements! You need a special fixture that
>> will make a low-inductance connection
On Tue, 4 Dec 2007, John Sigler wrote:
> Hello Sébastien,
>
> Sébastien Dugué wrote:
>
>> John Sigler wrote:
>>
>>> I have an x86 system, running Linux 2.6.22.1-rt9, in which I plug one
>>> or two PCI I/O boards. I had been experiencing complete system lock-ups
>>> until I sent the system to the
On Tue, 4 Dec 2007, John Sigler wrote:
Hello Sébastien,
Sébastien Dugué wrote:
John Sigler wrote:
I have an x86 system, running Linux 2.6.22.1-rt9, in which I plug one
or two PCI I/O boards. I had been experiencing complete system lock-ups
until I sent the system to the board
On Tue, 4 Dec 2007, John Sigler wrote:
Dick Johnson wrote:
You can't just touch a scope-probe to the PCI
clock pin and clip the scope-probe grounding
lead to a convenient ground to make these
measurements! You need a special fixture that
will make a low-inductance connection to the
PCI
On Tue, 20 Nov 2007, Richard B. Johnson wrote:
> On Tue, 20 Nov 2007, Herbert Xu wrote:
>
>> Hi:
>>
>> [KERNEL]: Avoid divide in IS_ALIGN
>>
>> I was happy to discover the brand new IS_ALIGN macro and quickly
>> used it in my code. To my dismay I found that the generated code
>> used division
On Tue, 20 Nov 2007, Richard B. Johnson wrote:
On Tue, 20 Nov 2007, Herbert Xu wrote:
Hi:
[KERNEL]: Avoid divide in IS_ALIGN
I was happy to discover the brand new IS_ALIGN macro and quickly
used it in my code. To my dismay I found that the generated code
used division to perform the
On Tue, 20 Nov 2007, Herbert Xu wrote:
> Hi:
>
> [KERNEL]: Avoid divide in IS_ALIGN
>
> I was happy to discover the brand new IS_ALIGN macro and quickly
> used it in my code. To my dismay I found that the generated code
> used division to perform the test.
>
> This patch fixes it by changing
On Tue, 20 Nov 2007, Herbert Xu wrote:
Hi:
[KERNEL]: Avoid divide in IS_ALIGN
I was happy to discover the brand new IS_ALIGN macro and quickly
used it in my code. To my dismay I found that the generated code
used division to perform the test.
This patch fixes it by changing the % test
On Mon, 29 Oct 2007, Tilman Schmidt wrote:
> Am 28.10.2007 20:25 schrieb Adrian Bunk:
>> On Sun, Oct 28, 2007 at 07:51:12PM +0100, Tilman Schmidt wrote:
>>> Am 28.10.2007 02:55 schrieb Adrian Bunk:
Justifying anything with code with not GPL compatible licences has zero
relevance here.
On Mon, 29 Oct 2007, Tilman Schmidt wrote:
Am 28.10.2007 20:25 schrieb Adrian Bunk:
On Sun, Oct 28, 2007 at 07:51:12PM +0100, Tilman Schmidt wrote:
Am 28.10.2007 02:55 schrieb Adrian Bunk:
Justifying anything with code with not GPL compatible licences has zero
relevance here.
And there's
On Thu, 25 Oct 2007, Andi Kleen wrote:
> On Thursday 25 October 2007 05:24, Nick Piggin wrote:
>
>> Basically, what the gcc developers are saying is that gcc is
>> free to load and store to any memory location, so long as it
>> behaves as if the instructions were executed in sequence.
>
> This
On Thu, 25 Oct 2007, Andi Kleen wrote:
On Thursday 25 October 2007 05:24, Nick Piggin wrote:
Basically, what the gcc developers are saying is that gcc is
free to load and store to any memory location, so long as it
behaves as if the instructions were executed in sequence.
This case is
On Wed, 24 Oct 2007, Bodo Eggert wrote:
> Miguel Botón <[EMAIL PROTECTED]> wrote:
>
>> This patch fixes the warnings "passing argument 1 of '__memcpy' discards
>> qualifiers from pointer target type" and "passing argument 2 of '__memcpy'
>> discards qualifiers from pointer target type" when
On Wed, 24 Oct 2007, Ram wrote:
> Hi,
>When i do ps -l. i see the following processes which are obviously
> started by kernel.
>
> Could any one tell me what each of these processes do and can
> anyone of them can be removed.?
>
> PID Uid VmSize Stat Command
>1 root584 S
On Wed, 24 Oct 2007, Ram wrote:
Hi,
When i do ps -l. i see the following processes which are obviously
started by kernel.
Could any one tell me what each of these processes do and can
anyone of them can be removed.?
PID Uid VmSize Stat Command
1 root584 S init
On Wed, 24 Oct 2007, Bodo Eggert wrote:
Miguel Botón [EMAIL PROTECTED] wrote:
This patch fixes the warnings passing argument 1 of '__memcpy' discards
qualifiers from pointer target type and passing argument 2 of '__memcpy'
discards qualifiers from pointer target type when compiling some
On Sun, 21 Oct 2007, Ravinandan Arakali (rarakali) wrote:
> Hi Vaidy,
> Thanks for clarifying several of my doubts.
>
> To answer your question about my intention, we currently have a
> system with 2 GB RAM and I need to find out the actual used and
> free memory so that we can decide if the
On Sun, 21 Oct 2007, Ravinandan Arakali (rarakali) wrote:
Hi Vaidy,
Thanks for clarifying several of my doubts.
To answer your question about my intention, we currently have a
system with 2 GB RAM and I need to find out the actual used and
free memory so that we can decide if the same
On Tue, 16 Oct 2007, veerasena reddy wrote:
> Hi,
>
> I have a board, which has two processors ( one is MIPS
> on which Linux-2.6.18 kernel runs and another is DSP
> based processor) and 32MB DDR.
>
> Out of 32MB of DDR 8MB is reserved for use by DSP
> processor. But the MIPS processor
On Tue, 16 Oct 2007, John Sigler wrote:
> John Sigler wrote:
>
>> Alexey Starikovskiy wrote:
>>
>>> Could you please open bug at bugzilla.kernel.org and put all these
>>> files there?
>>
>> http://bugzilla.kernel.org/show_bug.cgi?id=9148
>>
>> Writing 15361 (i.e. 0x3C01) to
On Tue, 16 Oct 2007, John Sigler wrote:
John Sigler wrote:
Alexey Starikovskiy wrote:
Could you please open bug at bugzilla.kernel.org and put all these
files there?
http://bugzilla.kernel.org/show_bug.cgi?id=9148
Writing 15361 (i.e. 0x3C01) to ACPI_REGISTER_PM1A_CONTROL appears to
On Tue, 16 Oct 2007, veerasena reddy wrote:
Hi,
I have a board, which has two processors ( one is MIPS
on which Linux-2.6.18 kernel runs and another is DSP
based processor) and 32MB DDR.
Out of 32MB of DDR 8MB is reserved for use by DSP
processor. But the MIPS processor downloads
On Wed, 10 Oct 2007, Jupe wrote:
> Hi,
>
> I have written an ethernet driver for an ARM based board.
> Linux version: 2.6.20.1
>
> Ping is working fine.
>
> I have written a test server/client application using socket programming
> (TCP).
> After the connection is setup the server sends a file
On Tue, 9 Oct 2007, Krzysztof Halasa wrote:
> Jeremy Fitzhardinge <[EMAIL PROTECTED]> writes:
>
>> but the gist is that IBM has
>> traditionally bit 0 for MSB and x for LSB. It's a pain to work with:
>> for one, bits in the same place in a word (say, control register) are
>> renumbered in 32 vs
On Tue, 9 Oct 2007, Krzysztof Halasa wrote:
Jeremy Fitzhardinge [EMAIL PROTECTED] writes:
but the gist is that IBM has
traditionally bit 0 for MSB and x for LSB. It's a pain to work with:
for one, bits in the same place in a word (say, control register) are
renumbered in 32 vs 64.
I
On Wed, 10 Oct 2007, Jupe wrote:
Hi,
I have written an ethernet driver for an ARM based board.
Linux version: 2.6.20.1
Ping is working fine.
I have written a test server/client application using socket programming
(TCP).
After the connection is setup the server sends a file to the
On Fri, 5 Oct 2007, Timur Tabi wrote:
> Andreas Schwab wrote:
>
>> The bit mapping on your device is strictly internal to the device and
>> has nothing to do with bit order on the C level.
>
> Then I don't understand that point of defining __LITTLE_ENDIAN_BITFIELD.
What does it mean for a
On Fri, 5 Oct 2007, Timur Tabi wrote:
Andreas Schwab wrote:
The bit mapping on your device is strictly internal to the device and
has nothing to do with bit order on the C level.
Then I don't understand that point of defining __LITTLE_ENDIAN_BITFIELD.
What does it mean for a C-level
On Tue, 2 Oct 2007, Jan Engelhardt wrote:
>
> On Oct 2 2007 23:49, Jimmy wrote:
>>
>> Anyway, I've been trying to figure out what purpose the gpl-only code serves.
>> What good comes out of disabling people from probing modules that do not
>> have a
>> gpl-compatible license?
>
> find
On Tue, 2 Oct 2007, Jan Engelhardt wrote:
On Oct 2 2007 23:49, Jimmy wrote:
Anyway, I've been trying to figure out what purpose the gpl-only code serves.
What good comes out of disabling people from probing modules that do not
have a
gpl-compatible license?
find /lib/modules/`uname -r`
On Tue, 2 Oct 2007, Ingo Molnar wrote:
>
> * David Schwartz <[EMAIL PROTECTED]> wrote:
>
>>> These are generic statements, but i'm _really_ interested in the
>>> specifics. Real, specific code that i can look at. The typical Linux
>>> distro consists of in execess of 500 millions of lines of
On Tue, 2 Oct 2007, Ingo Molnar wrote:
* David Schwartz [EMAIL PROTECTED] wrote:
These are generic statements, but i'm _really_ interested in the
specifics. Real, specific code that i can look at. The typical Linux
distro consists of in execess of 500 millions of lines of code, in
tens of
On Fri, 28 Sep 2007, [iso-8859-1] Daniel Spång wrote:
> On 9/28/07, linux-os (Dick Johnson) <[EMAIL PROTECTED]> wrote:
>>
>> On Fri, 28 Sep 2007, [iso-8859-1] Daniel Spång wrote:
>>
>>> On 9/28/07, linux-os (Dick Johnson) <[EMAIL PROTECTED]> wrote:
>
On Fri, 28 Sep 2007, [iso-8859-1] Daniel Spång wrote:
> On 9/28/07, linux-os (Dick Johnson) <[EMAIL PROTECTED]> wrote:
>>
>> On Fri, 28 Sep 2007, [iso-8859-1] Daniel Spång wrote:
>>
>>> Applications with dynamic input and dynamic memory usage have some
>&g
1 - 100 of 420 matches
Mail list logo
