Hi Andrew...
On Thu, Sep 6, 2012 at 2:56 AM, Andrew Case wrote:
> So far I have identified:
>
> 1) smp_locks
> 2) .alt_instructions - although from writing a script to parse the
> alt_instr structures, it seems these may not affect .text, any
> clarification on this would be greatly appreciated.
Hello,
I am trying to determine all the ways/methods in which the kernel will
modify its own .text section after the machine has booted. I am
working with the latest Fedora kernel (3.5.2-3.fc17.x86_64).
So far I have identified:
1) smp_locks
2) .alt_instructions - although from writing a script
On Wed, Sep 5, 2012 at 7:04 PM, Kshemendra KP wrote:
> Is there a way to generate build environment in such a situation as
> the manufacture source is bit deviated from source he has posted on the
> net.
a friend of mine said, you should just use Android SDK. But I am not
sure whether that a
Hi
As the kernel source not available for running kernel code of an
Andodiod tablet,
I could not able to match module_layout address of my loadable module with
the
android tablet running kernel even the kernel versions are same.
Is there a way to generate build environment in such a sit
Hello,
In the course of reviewing a new framebuffer driver [1], I discovered
the following bit of code:
+ dst = (void __force *) (info->screen_base + p);
+
+ if (copy_from_user(dst, buf, count))
+ err = -EFAULT;
Where info->screen_base is a vmalloc'ed memory area. Many
On Tue, Sep 4, 2012 at 5:55 PM, Dan Carpenter wrote:
> On Tue, Sep 04, 2012 at 03:58:20PM +0530, Manavendra Nath Manav wrote:
>> Is the above a genuine kernel bug, or i am missing something out here. Pls
>> help.
>>
>
> When you declare something as const then the compiler assumes it
> really is