In Linux PPC, the MSR[FP] bit (that is floating point available bit) is off
(atleast for non-SMP).
Due to this, whenever some floating point instruction is executed in 'user
mode', it leads to a exception 'FPUnavailable'. The exception handler for
this exception apart from setting the MSR[FP]
In Linux PPC, the MSR[FP] bit (that is floating point available bit) is off
(atleast for non-SMP).
Due to this, whenever some floating point instruction is executed in 'user
mode', it leads to a exception 'FPUnavailable'. The exception handler for
this exception apart from setting the MSR[FP]
I am running linux 2.4.2 on Apple G4 machine. I think the 'PCI bus
addresses' and 'physical addresses' are same on this architecture. I
expected the two be different but according to asm/io.h 'virt_to_bus(addr)
= virt_to_phys(addr) + PCI_DRAM_OFFSET'. I printed the value of
'PCI_DRAM_OFFSET' and
I use the 'map_user_kiobuf' and 'lock_kiovec' kernel routines in a module
for 'user space memory'. After that if I pass the
'(iobuf->maplist[0])-mem_map) << PAGE_SHIFT)' to the hardware for DMA
operations and it works fine for Intel platforms. Now how can I use the
'iobuf' struct obtained after
I use the 'map_user_kiobuf' and 'lock_kiovec' kernel routines in a module
for 'user space memory'. After that if I pass the
'(iobuf-maplist[0])-mem_map) PAGE_SHIFT)' to the hardware for DMA
operations and it works fine for Intel platforms. Now how can I use the
'iobuf' struct obtained after
I am running linux 2.4.2 on Apple G4 machine. I think the 'PCI bus
addresses' and 'physical addresses' are same on this architecture. I
expected the two be different but according to asm/io.h 'virt_to_bus(addr)
= virt_to_phys(addr) + PCI_DRAM_OFFSET'. I printed the value of
'PCI_DRAM_OFFSET' and
I am experiencing a strange problem.
I am doing a continuous DMA for long hours using a card on my system. In my
code I enable interrupts and clear the interrupts in the interrupt handler
which is called on completion of every DMA cycle. Now, the program works
fine for say 16-20 hours but I think
I am experiencing a strange problem.
I am doing a continuous DMA for long hours using a card on my system. In my
code I enable interrupts and clear the interrupts in the interrupt handler
which is called on completion of every DMA cycle. Now, the program works
fine for say 16-20 hours but I think
Hi,
I do not know whether I should ask this question on this mailing list, but
it definitely has to do either with the kernel confiuration or kernel
support.
In the '/dev' tree, the device file entries for SCSI harddisks ranges from
'/dev/sda' to '/dev/sdp'. If I attach 17 scsi harddisks to a
Hi,
I do not know whether I should ask this question on this mailing list, but
it definitely has to do either with the kernel confiuration or kernel
support.
In the '/dev' tree, the device file entries for SCSI harddisks ranges from
'/dev/sda' to '/dev/sdp'. If I attach 17 scsi harddisks to a
I am doing a DMA from a card to system memory. The system memory "physical
address" is '0x104000'. I am doing this on x86 with kernel version 2.4.2.
Can this address be the address of a user space buffer?
Regards,
Daljeet.
|+--->
|| Ingo Molnar |
|
I am doing a DMA from a card to system memory. The system memory physical
address is '0x104000'. I am doing this on x86 with kernel version 2.4.2.
Can this address be the address of a user space buffer?
Regards,
Daljeet.
|+---
|| Ingo Molnar |
|
I use the 'pgt_offset', 'pmd_offset', 'pte_offset' and 'pte_page' inside a
module to get the physical address of a user space virtual address. The
physical address returned by 'pte_page' is not page aligned whereas the
virtual address was page aligned. Can somebody tell me the reason?
Also, can
I use the 'pgt_offset', 'pmd_offset', 'pte_offset' and 'pte_page' inside a
module to get the physical address of a user space virtual address. The
physical address returned by 'pte_page' is not page aligned whereas the
virtual address was page aligned. Can somebody tell me the reason?
Also, can
I am using linux kernel version 2.4.2 on Intel PC.
I have been trying my luck for over a week regarding usage of
'map_user_kiobuf' for doing a DMA into a memory area that belongs to user
space.
Actually my requirement is that I want to do DMA into a user space memory
area. What I have done
I am using linux kernel version 2.4.2 on Intel PC.
I have been trying my luck for over a week regarding usage of
'map_user_kiobuf' for doing a DMA into a memory area that belongs to user
space.
Actually my requirement is that I want to do DMA into a user space memory
area. What I have done
How can I bind a user space process to a particular processor in a SMP
environment?
thanks,
Daljeet Maini
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
How can I bind a user space process to a particular processor in a SMP
environment?
thanks,
Daljeet Maini
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
When is the 'CONFIG_APUS' flag used ?
Daljeet Maini
IBM Global Services Ltd. - Bangalore
Ph. No. - 5267117 Extn 2954
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
When is the 'CONFIG_APUS' flag used ?
Daljeet Maini
IBM Global Services Ltd. - Bangalore
Ph. No. - 5267117 Extn 2954
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
When I malloc the memory in user space, the memory may be discontinuous for
large chunks of memory say 16k or 32k. Does the 'kiobuf' interface take
care of this or it assumes it to be continuous?
regards,
Daljeet Maini
IBM Global Services Ltd. - Bangalore
Ph. No. - 5267117 Extn 2954
I am doing the following:
malloc some memory is user space
pass its pointer to some kernel module
in the kernel module...do a pci_alloc_consistent so that i get a memory
region for PCI DMA operations
now the problem is that i want to remap the address range pointed by the
user space
I am doing the following:
malloc some memory is user space
pass its pointer to some kernel module
in the kernel module...do a pci_alloc_consistent so that i get a memory
region for PCI DMA operations
now the problem is that i want to remap the address range pointed by the
user space
When I malloc the memory in user space, the memory may be discontinuous for
large chunks of memory say 16k or 32k. Does the 'kiobuf' interface take
care of this or it assumes it to be continuous?
regards,
Daljeet Maini
IBM Global Services Ltd. - Bangalore
Ph. No. - 5267117 Extn 2954
Hi,
Was there any change in the PCI initialization code between versions
2.4.0-test8 and 2.4.2.?
I am working on a card and for the same register settings of the card, DMA
from host memory to card memory is successfull for the 2.4.0-test8 but on
2.4.2 kernel, the data transfer is successfull
Hi,
Was there any change in the PCI initialization code between versions
2.4.0-test8 and 2.4.2.?
I am working on a card and for the same register settings of the card, DMA
from host memory to card memory is successfull for the 2.4.0-test8 but on
2.4.2 kernel, the data transfer is successfull
Hi,
If I compile the 2.4.0-test8 kernel on uniprocessor intel machine with SMP
support, I get no compilation problems. But when I compile on a 'netfinity'
machine with 3 intel processors with SMP support, the telnet session in
which I do this gets hung during 'make bzImage'. Though the 'bzImage'
Hi,
If I compile the 2.4.0-test8 kernel on uniprocessor intel machine with SMP
support, I get no compilation problems. But when I compile on a 'netfinity'
machine with 3 intel processors with SMP support, the telnet session in
which I do this gets hung during 'make bzImage'. Though the 'bzImage'
Hi,
By looking into the structure of GDT as used by linux kernel(file
include/asm/desc.c, kernel ver 2.4), it appears as if linux kernel does not
use the "call gate descriptors" for system call handling. Is this correct?
If it is correct then how does the system calls are handled by the kernel
hi,
i am allocating some 1000 bytes of memory as folows
f_malloc()
{
.
for (i=1 to 10)
{
size = 1000;
pAddr[i] = (unsigned long) kmalloc(size, GFP_DMA | GFP_BUFFER);
}
...
}
and freeing the allocated memory as follows
f_free()
{
.
for (i=1
hi,
i am allocating some 1000 bytes of memory as folows
f_malloc()
{
.
for (i=1 to 10)
{
size = 1000;
pAddr[i] = (unsigned long) kmalloc(size, GFP_DMA | GFP_BUFFER);
}
...
}
and freeing the allocated memory as follows
f_free()
{
.
for (i=1
can anyone tell the subsitute for MAP_NR in version 2.4?
or is MAP_NR still there?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
can anyone tell the subsitute for MAP_NR in version 2.4?
or is MAP_NR still there?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Hi,
If I have two identical network cards on my machine and I unregister the
driver of one
of them (say eth0) using the call "pci_unregister_driver(pdev->driver)"
where pdev is
the 'pci_dev' structure for eth0, does the device 'eth1' i.e. the other one
gets effected by
this.
Regards,
daljeet.
Hi,
I have a user buffer and i want to map it to kernel address space
can anyone tell how to do this like in AIX we have xmattach
thanks
daljeet
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at
Hi,
I have a user buffer and i want to map it to kernel address space
can anyone tell how to do this like in AIX we have xmattach
thanks
daljeet
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at
>I find out that doing the following command:
>cp toto titi/toto
>where toto is a file and titi is a directory do >not change the date stamp
of
>`titi'.
i checked this out with 2.4-0test9.
timestmap of directory is getting modified. you must be using very old
kernel
-
To unsubscribe from
Hi,
struct t{
int (*x)(int);
}fstruct;
main()
{
.
.
fstruct.x = f;
./*write fstruct to a device file*/
.
}
int f(int i)
{
printf("got %d\n",i);
return i;
}
i pass this structure to kernel module by writting to device file.
the write function of module is like
..
..
char *kbuf;
Hi,
struct t{
int (*x)(int);
}fstruct;
main()
{
.
.
fstruct.x = f;
./*write fstruct to a device file*/
.
}
int f(int i)
{
printf("got %d\n",i);
return i;
}
i pass this structure to kernel module by writting to device file.
the write function of module is like
..
..
char *kbuf;
I find out that doing the following command:
cp toto titi/toto
where toto is a file and titi is a directory do not change the date stamp
of
`titi'.
i checked this out with 2.4-0test9.
timestmap of directory is getting modified. you must be using very old
kernel
-
To unsubscribe from this
40 matches
Mail list logo