Hi,
You can ignore that message, if your Kernel is enabled by default, you
can disable the "Rely on OTG ..."
Device Drivers --->
[*] USB support --->
[ ] Rely on OTG Targeted Peripherals List
This enumerates your USB device.
Regarding CAIF protocol, you need to enab
Your boot logs?
On Mar 23, 9:15 pm, stanly wrote:
> hi all,
>
> when I booting my kernel 2.6.35,
> the LOGO can't show up,
> but actually I do something really,
>
> ***
> i)
> in my default config
> CONFIG_LOGO=y
> CONFIG_LOGO_LINUX_CLUT264=y
> and other config
Mark means you've commented that part of the code.
With that you may not get the console prompt.
On Mar 23, 9:04 pm, tstanly wrote:
> hi Srikant,
>
> thanks for your reply,
> I tried to mark this code, and it pass to continue,
> but stuck in executing /init,
> so is it po
The new Android version to work properly with the required Kernel
version,
1. There may be some changes/new drivers in Kernel drivers/staging/
android/
2. If there is any driver version dependency between Kernel & Android,
for example if any Graphics driver version mismatch
Might be this the reas
That means it is trying to open UART driver, you need to debug the
UART driver with putting some prints.
The reason for the hang may be some feature/function of UART doesn't
support.
Which board are you using?
On Mar 21, 12:33 pm, stanly wrote:
> hi all,
>
> when my kernel booting,
> it will be
You can execute the following test cases to validate your porting:
1. Validating Booting - Use Boot chart
http://elinux.org/Using_Bootchart_on_Android
2. Validating Kernel, File System, I/O & Storage, Performance/Bench
Marking, Memory etc. - Use LTP (Linux Test Project)
http://ltp.sourceforge.net
You might need to call notification function (like kill_fasync) from
your driver ISR/Work Queue.
Also you have to pass the FASYNC flag from your application.
-
On Feb 25, 9:24 pm, Durgadoss R wrote:
> Hi All,
>
> I am writing a Thermal Sensor Driver for Android-Froyo.
> The hardware supports pr
You can use IOzone for measuring file system performance.
http://www.iozone.org/
On Feb 9, 12:09 am, Dani Levi wrote:
> Hi
> I would like to compare performance betweenr I/O operation SD Card vs
> Nand .
> (For examplehttp://www.iometer.org/)
> I would like to compare read/write Random/sequential
My be you're using a wrong config file.
Which CPU/board you're using?
On Jan 27, 9:51 am, 杨竹 wrote:
> I'm git clone get the android samsung kernel 2.6.35 ,build the
> s3c6400config but get the error:
>
> arch/arm/plat-samsung/pm.c:33:33: error: plat/irq-eint-group.h: No
> such file or director
You can refer the android.git.kernel.org kernel/common.git
Documentation/android.txt for details.
Also compare this code with your 2.6.29 android kernel to see the
changes.
On Jan 24, 11:51 pm, A Curtis wrote:
> Hello,
>
> Is there a document which describes the kernel support requirements
> for
Load your driver using insmod or modprobe
Build your test application with arm compiler statically or use some
Android Make file to compile it.
copy this application binary to your SD card and then test it.
On Jan 11, 2:33 pm, Matthias Leblanc
wrote:
> hello,
> I want to use a Linux driver with a
I agree with you, if the requirement is porting to a new h/w platform.
But the requirement here is to just porting to a new Linux Kernel
version, hence it may not be required to do assembly level debugging.
On Jan 4, 3:55 pm, Chris Stratton wrote:
> > Instead of this, you can enable Kernel Low L
Enable adb logcat messages, so that you will get error if there is
driver version mismatch.
On Dec 25 2010, 9:06 pm, Ultra wrote:
> HI,
>
> I am a new android user. I m using Atom netbook. I install android x86
> in my HDD. But, I face a serious problem of my wifi card failed to
> connect to in
download the android kernel version 2.6.35 for Gingerbread.
On Nov 17 2010, 11:53 pm, TitCowboy wrote:
> Gingerbread is based on which kernel version, please ? (2.6.35 ?)
--
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel
> If you don't see anything, hardcode a character or two of output from
> the very start of the kernel startup routine, that sets all necessary
> registers explicitly. You could for example set it up to count '0'
> '1' '2' '3' etc with each digit added after another block of the
> startup code, up
Android "Alarm Clock" is the test application for the alarm.c, with
which you can test by setting the date & time for alarm and snooze.
Before testing that, you can enable the Alarm driver and RTC driver
debug prints and also enable adb logcat messages, and capture the logs
of the test.
It gives c
16 matches
Mail list logo
