Thanks greg & pavan for your valuable insights.
I was not able to directly make use of uinput, since my hid reports
had to be parsed first by the HID Parser driver, before giving it to
the input subsystem.
Anyways, thanks a ton to the maintainer of HID-CORE module, Jiri
Kosina.
I'm just quoting
Hi,
I'm looking at a specific IOCTL SET_CONTEXT_MANAGER of binder driver
initiated by service manager.
int binder_become_context_manager(struct binder_state *bs)
{
return ioctl(bs->fd, BINDER_SET_CONTEXT_MGR, 0);
}
control flows from the ioctl call to the following function.
static long b
I think
www.android-x86.org will help you.
Thanks,
Jeffrey
2010/5/18 fubared
> Hi,
>
> I'm trying to build Donut. The command I'm using is 'make CC=gcc-4.3'
> but it seems that gcc 4.3 can't find a compatible version of libgcc.
> Anyone know how I can get one?
>
> I'm running on an x64 archite
Hi,
I was looking at the implemenation of current_thread_info and
couldn't figure it out. What exactly is being done here? and is the
thread information always stored in the stack (in linux os)?
register unsigned long sp asm ("sp");
return (struct thread_info *)(sp & ~(THREAD_SI
Hi Andrew,
I wanted to give a try to your latest patach and have come across this
error during kernel link:
LD vmlinux.o
drivers/built-in.o: In function `msm_hsusb_set_vbus_state':
/kernel-hero/drivers/usb/function/msm_hsusb.c:1685: multiple
definition of `msm_hsusb_set_vbus_state'
arch/arm
