> We are assuming that the kernel is completely booted, in 2.6.32
> kernel, without any issues as it entered into cpu_idle state. We are
> guessing that there is an error in the file system sources (i.e.
> sbin/init). Unfortunately, we do not have the sources for the
> available file system and we
> Here are the final debug statements which we are seeing in the hyper terminal.
Can you post the full logs WITHOUT your debug prints. What is the
toolchain you are using?
> If we load 2.6.10 kernel image, we are getting login prompt in the
> hyper terminal on the same Phytec board.
You can isol
> Using ARM926e-js processor with 128MB SDRAM., Clock-33Mhz
>
> SDRAM Size = 128M
>
>
>
> CONFIG_PAGE_OFFSET = 0xc000
>
> CONFIG_PHYS_OFFSET= 0x8000
>
>
>
> Loading the cramfs at 0x8200
>
> Start address for kernel is 0x80008000
>
> Commandline(atags address) is 0x8100
>
>
>
> Ke
> Using ARM926e-js processor with 128MB SDRAM., Clock-33Mhz
>
> SDRAM Size = 128M
>
>
>
> CONFIG_PAGE_OFFSET = 0xc000
>
> CONFIG_PHYS_OFFSET= 0x8000
>
>
>
> Kernel Lowmem = 32M including 8M for initramfs (starting from 24M to 32M).
>
If SDRAM is 128MB why only 32M for lowmem?
> This is d
> /vmlinux 2,629,659 bytes
> /vmlinux.o 2,889,050 bytes
> /arch/i386/boot/bzImage 1,104,864 bytes
> /arch/x86/boot/bzImage 1,104,864 bytes
>
> I am trying to understand the kernel page frame reclaiming
> mechanism, but one thing's bothering me:
> How does the kernel 'know' which anonymous pages to evict? In the LRU
> scheme, 'referenced/used' information for each page is required
> (AFAIK). But anonymous pages can be used by user proc
Post your questions(be specific) to
linux-fbdev-de...@lists.sourceforge.net they
will quickly respond. Based on my previous exp. with them :)
-syed
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/list
> The 2 lines above
> 1: orr r3, r7, r5, lsl #20 @ flags + kernel base ==> Correct
> str r3, [r4, r5, lsl #2] @ identity mapping ==> ??
>
> create a section entry using index based on physical address.
Lets say before mmu is turned on PC is at physical address XXX, also
sa
> struct page *page = virt_to_page(skb->data);
> int offset = (unsigned long) skb->data - (unsigned long) page_address(page);
> skb_add_rx_frag(master_skb, skb_shinfo(master_skb)->nr_frags, page, offset,
> skb->len)
> .
> .
> is this the right way to do ?
This will work if skb->len < PAGE_SIZE, oth
On Tue, Mar 29, 2011 at 5:30 PM, Venkatram Tummala
wrote:
> Hi,
> Why do we need both page_table_lock & mmap_sem in the kernel. Why isn't
See linux/Documentation/vm/locking
-syed
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lis
> .
> struct page *page = virt_to_page(skb->data);
If skb->data page aligned?
> .
> And can some one please tell what is the use of the functions like
> virt_to_page and kmap_atomic_to_page,
Generally to lock the page in memory(esp while doing dma) using get_page().
> i tried calling virt_to_page
>
> Is there any reason why this isn't a kconfig option?
The memory/RAM related defaults are present in
arch/arm/include/asm/memory.h. But you can override them by defining
them in
/arch/arm/mach-YOURMACHINE/include/mach/memory.h. I think the
developers intended to keep it this way so machine spec
> I have looked at the code for dma_alloc_coherent etc and it seems to me that
> it's returning null because there isn't the space available to allocate the
> requested memory.
You might have to increase the consistent(or dma) memory size. In
recent kernels its defined by CONSISTENT_DMA_SIZE
(ach/
> I'm currently trying to port a (currently for unreleased hardware and
> under nda) driver from x86 to arm and in doing so I've run into a
> problem with allocating memory using pci_alloc_consistent. Looking into
> it I can't allocate more than 1MB whereas I need to allocate at least
> 2MB of cont
> Linux (compiler actually) supports C99 fixed-width types such as 8,
> 16, 32, 64 bits.
> Just look through the include/linux/types.h
> and small example here:
> http://lxr.linux.no/#linux+v2.6.36/arch/powerpc/boot/types.h#L8
>>
while writing portable applications always remember that "unsigned
l
15 matches
Mail list logo
