Hi All
I'm working for Freescale Semiconductor on the i.MX series linux BSP.
Now we have android running well on i.MX515 platform, and hope to push
android kernel repo into android.git.kernel.org.
Then what's the process need us to follow? How reviews will be done?
And what we should provide?
Ca
Hi, does any one ever compile 2.6.29 kernel and boot succ on HTC
magic?? Can you provide the config for kernel?? thanks a lot...
--~--~-~--~~~---~--~~
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel
-~
> So it seems that errno.h is not copyrightable, thus I can just go on
> the kernel sources and get whatever constants are there without
> worrying about licensing. However, I don't expect to do this in an
> automated way, I would just copy the constants and reorganize the code
> my own way. I do
On Mon, Jul 13, 2009 at 6:34 AM, Henrique Almeida wrote:
>
> (This message is partially offtopic. I need help with relicensing of
> a certain file derived from the kernel source.)
Then ask the lawyers and developers of the Linux kernel, not the Android
team, as they do not hold the copyright/lic
FreeBSD, Gnome, and X are completely unrelated to Android.
On Mon, Jul 13, 2009 at 7:10 AM, basteon wrote:
>
> hi there,
> I seems you must be use mongolian keymaps for your kdb, it's kind of
> userland adjustment. like there...
> http://www.mnbsd.org/article.php?story=20050930163834630
> On 13/
hi there,
I seems you must be use mongolian keymaps for your kdb, it's kind of
userland adjustment. like there...
http://www.mnbsd.org/article.php?story=20050930163834630
On 13/07/2009, Ulzii wrote:
>
> I am a Mongolian developer and I need to create a Mongolian crylic
> letter keyboard driver fo
(This message is partially offtopic. I need help with relicensing of
a certain file derived from the kernel source.)
I'm currently writing a standard C library for Unix systems and I'll
need many errno.h versions from different Unix vendors. The constants
in there must match what the kernel use
Hi Ashutosh,
I think the problem is that the gadget support is broken in our 2.6.27
kernel. However, I do know it is working in 2.6.29. I believe if you
do the following:
- backport the latest drivers/usb/gadget/android.c from 2.6.29 back to 2.6.27
- backport the following commit from 2.6.29
(especially to Mike Lockwood)
If I want to have gadgetfs support at ADP1 and have adb working, how
do I need to to configure kernel and compile?
I have tried many things including using 'CONFIG_USB_ANDROID=y' and
'CONFIG_USB_FUNCTION is not set' but nothing worked. To compile this
configuration
