I fully agree with Adil.
It would be great to see this in the form of article on
kernelnewbies.orgwebsite.
--
Regards,
Denis
On Sat, 15 Mar 2008, Thomas Petazzoni wrote:
Le Fri, 14 Mar 2008 12:30:53 -0400 (EDT),
Robert P. J. Day [EMAIL PROTECTED] a écrit :
yes, i think we've established what's happening. as long as a
module parameter is defined with access rights of zero, it can be
tagged as __initdata.
No,
Hi,
I want to have maximum debugging symbols in my kernel image and
currently I have changed the build flags in my top level Makefile so
that they look like below.
HOSTCFLAGS = -Wall -Wstrict-prototypes #-O2 -fomit-frame-pointer
#HOSTCXXFLAGS = -O2
ifdef CONFIG_CC_OPTIMIZE_FOR_SIZE
CFLAGS +=
hello
On Mon, Mar 17, 2008 at 5:44 PM, Manish Katiyar [EMAIL PROTECTED] wrote:
Hi,
I want to have maximum debugging symbols in my kernel image and
currently I have changed the build flags in my top level Makefile so
that they look like below.
uhm, prevents inlining at all cost? And no
On Sat, Mar 15, 2008 at 03:59:36PM +0800, vichy wrote:
I found there is number at the end of SCSI commands like below:
Command document
WRITE(6) SBC
WRITE(10)SBC
WRITE(12)SBC
Could someone tell me what the number, (6), (10) and (12) mean?
The length of the command in bytes.
On Mon, Mar 17, 2008 at 12:52:20AM +0530, Manish Katiyar wrote:
I was reading about the lost-write problem in filesystems (see link
below) and wanted to know how traditional linux systems like
ext{2,3,4} or other popular ones handle this case, since most/all of
them don't have any control over
On Mon, Mar 17, 2008 at 12:02:12PM +0800, vichy wrote:
I try to modify the content of ehci registers directly by mmap, but I have
some trouble about it.
Changing registers from a device managed by a driver is very dangerous.
In the best case nothing happens, worst case you may see massive
On Mon, Mar 17, 2008 at 07:15:37PM +0700, Mulyadi Santosa wrote:
hello
On Mon, Mar 17, 2008 at 5:44 PM, Manish Katiyar [EMAIL PROTECTED] wrote:
Hi,
I want to have maximum debugging symbols in my kernel image and
currently I have changed the build flags in my top level Makefile so
Le Mon, 17 Mar 2008 02:20:53 -0300,
Rafael C. de Almeida [EMAIL PROTECTED] a écrit :
I'm trying to understand how the bytes I get from recv(2) comes
through the nic to the sockets interface. I tried following it from
sys_recv (net/socket.c) to the driver functions being used. But I got
stuck
Looking at schedule_work() below:
fs/file.c:
fddef = get_cpu_var(fdtable_defer_list);
spin_lock(fddef-lock);
fdt-next = fddef-next;
fddef-next = fdt;
/* vmallocs are handled from the workqueue context */
On Mon, Mar 17, 2008 at 8:47 PM, Erik Mouw [EMAIL PROTECTED] wrote:
On Mon, Mar 17, 2008 at 12:52:20AM +0530, Manish Katiyar wrote:
I was reading about the lost-write problem in filesystems (see link
below) and wanted to know how traditional linux systems like
ext{2,3,4} or other popular
Thomas Petazzoni [EMAIL PROTECTED] wrote:You can start by exploring the
implementation of datagram sockets
(relying on the UDP protocol) at
http://lxr.free-electrons.com/source/net/ipv4/af_inet.c#847.
You'll find many very precise documentations about the implementation
of the Linux network
Hello
How are you today? I hope you are fine.If so thank be to God almigthy.My name
is Farja Ali, 26 years from Liberia in West Africa. I am single girl looking
for honest and nice person.
Somebody who care and fear God whom i can partner with .I don't care about
your colour or
13 matches
Mail list logo
