Hi all,
I'd like to use gdb in Android x86. Is there a toolchain I can use?
Thanks!
-Brian
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
Thanks! I tried it.
I ran gdbserver and gdbclient, and got the following.
I'd like to pinpoint the code causing the problem, but I can't.
Any suggestion?
- Brian
# ./gdbserver localhost:1234 --attach 2154
Attached; pid = 2154
Listening on port 1234
Remote debugging from host 127.0.
Hi All:
I found the signal level will be dropped about -14dB after applied the
PresetReverb with "small room" while playing mp3 file.
So, I enabled the LVM_PCM @ EffercReverb.h to record input/output pcm
data into SD card and compared the singal level of input and output.
After studying the sour
Dear Eric:
I can't get your explanation for "the attenuation on the reverb tail"
Because according the source code, the 12dB headroom is reserved on
the reverb "head", not the tail
And the LVREV_OUTPUTGAIN_SHIFT is on the reverb tail to compensate the
gain back.
Could you help to descirbe more de
I am looking to convert the HTC Dream (G1) to CDMA. would any rebuild
of Android be needed, or would only certain drivers have to be
replaced to adapt for new parts?
Thanks,
Brian
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
prompt.
I cannot find an editor to modify init.rc on the shell.
How should I edit the file?
Ultimately, I'd like to start a GUI. If everything works fine,
does the android x86 eeepc (built following the howto posted
in the discussion group) start a GUI?
Thanks,
Brian
On Mar 5, 9:03 am, Sea
I'm trying to copy my dalvik application package to android x86 eeepc
running in vmware.
adb does not detect any device. I cannot use adb push.
How can I copy my dalvik application package located in my os to
android x86 running in vmware?
Thanks,
Hi Midhun,
I'm having the same problem when I ran android eeepc (I created
installer.img by following the how-to posted in the discussion group)
on vmware. How did you solve the problem?
Thanks,
Brian
On Jan 8, 5:10 am, Midhun wrote:
> Hi,
>
> I have built Android for ee
Thanks, Chen.
I'm trying to do option 1 shown below.
I'm getting the following error
"Error 1: Filename must be either an absolute pathname or blocklist".
How can I solve this problem?
Also, I have been using vmware fusion. I'm also trying vmware
workstation on windows.
bin/mountd', disabling 'mountd'
sh : can't access tty: job control turned off
[time] warning: 'app_process' uses 32-bit capabilities (legacy support
in use)
How can I fix it? It's hard to pinpoint what to do.
Thanks,
Brian
On Dec 28 2008, 1:40 am, &quo
A VGA and Framebuffer Console support when I
compiled bzImage.
dmesg output keeps printing out the following.
<6> [timestamp] SurfaceFlinger[2956]: segfault at 38 ip 80111049 sp
b5b56fec error 4 in libc.so [8010+4b000]
Thanks for your help.
Brian
On Mar 27, 5:11 am, Chen Yang wrote:
Hi Yi,
I tried to boot with or without vga=788. Both attempts are successful.
When you mention "changing the framebuffer to vga", do you mean
compiling the kernel with VESA VGA support and Framebuffer Console
support?
Thanks,
Brian
On Mar 27, 9:08 am, Yi Sun wrote:
> Have you
I've been trying to run android x86, but had no luck (black screen).
So, I got a fresh code using repo, and tried to build from the
scratch.
Now it does not even compile. I am getting the following error.
Does anyone have a similar problem? How can I fix this?
Thanks,
Brian
Copy: out/t
Thanks, Chen.
On Mar 28, 10:40 pm, Chen Yang wrote:
> Brian:
> I cannot see the clear problem from your description. The segfault
> issue seems to be common where the there is no framebuffer devices
> activated.
> For connection over adb, you may need to enabled the pcne
Hi Chen,
I managed to use adb.
I'm attaching /proc/devices. From the list, you can see "29 fb".
Is this what you're looking for?
Thanks,
Brian
Character devices:
1 mem
2 pty
3 ttyp
4 /dev/vc/0
4 tty
4 ttyS
5 /dev/tty
5 /dev/console
5 /dev/ptmx
7 vcs
1
Thanks, Yi !
I think init.rc is not correctly executed. It probably exits before it
starts adb.
I manually started adbd, and connected android using adb successfully.
What problems did you have in init.rc?
Thanks,
Brian
On Mar 29, 2:21 pm, Yi Sun wrote:
> In your ps, I did not see adbd.
Thanks, Yi.
Now I can use adb to browse the android vm directories. Also, I
installed busybox. :)
I noticed that mine does not show either mountd or zygote. Maybe
init.rc is different?
Could you kindly post your init.rc so that I can do further debugging?
Thanks,
Brian
On Mar 29, 4:07 pm, Yi
Thanks, Yi.
I have all the following in my init.rc.
servicemanager, mediaserver, installd are running.
But adbd, mountd, and zygote are not launched. Any suggestion?
Thanks,
Brian
# adbd is controlled by the persist.service.adb.enable system property
service adbd /sbin/adbd
disabled
on
I found out that there is no mountd under /system/bin.
It must be that mountd is not copied into system.img.
Which code should I look at to ensure that system.img contains mountd?
Thanks,
Brian
On Mar 29, 6:26 pm, Yi Sun wrote:
> Here is the part of the init.rc that I think is important
ystem/bin, and mountd starts but
I'm not sure it's using some configuration file correctly.
The problem of app_process is still there. It does not start probably
because of framebuffer issues.
I'm attaching my dmesg. How can I start app_process correctly?
Thanks,
Brian
<6>
Thanks, Jerry!
(I'm very sorry. I somehow got a wrong name.)
Please see the previous email.
Thanks,
Brian
On Mar 30, 8:14 am, Brian wrote:
> Thanks, Jeff.
>
> It seems like that the modules are copied from vendor/asus/eee_701/
> modules
> How can I check magic number
Thanks, Jeff.
It seems like that the modules are copied from vendor/asus/eee_701/
modules
How can I check magic numbers?
I'm attaching files in the directory. There is the module.versions
file and drm-patches. Maybe you can pinpoint what's going on with
these files better.
Tha
Thanks, Jerry!
I'm using kernel 2.6.27, and the modules have version 2.6.25 as you
can see below.
There are inconsistencies in the cupcake branch.
I will either get kernel 2.6.25 or try to compile 2.6.27 modules.
Thanks,
Brian
./kernel/include/config/kernel.release:2.6.27-00120-g45
Hi JBQ,
Have you also tested the compilation of cupcake x86 eee pc?
The repository I downloaded about a week ago compiles, but the latest
ones (I downloaded a few days ago and today) do not compile.
I'm getting the following error.
What can be a quick fix?
Thanks,
Brian
Copy: out/t
Thanks, JBQ.
For now, I'd like to get some old android repository.
For example, I want to get the March-23-2009 snapshot of the git
repository.
How can I do it with repo/git?
Thanks,
Brian
On Mar 30, 6:01 pm, Jean-Baptiste Queru wrote:
> I most definitely haven't tested it.
>
ith vga=788.
This time I'm getting a kernel panic, which I'm attaching.
Has anyone seen this problem? What's a proper approach to address this
problem?
Thanks,
Brian
Process netcfg (pid: 2031, ti=cf17c000 task=cf3001b0 task.ti=cf17c000)
Stack: ...
Call Trace:
[] ? cursor_timer
suggestion?
Thanks,
Brian
On Mar 30, 10:54 pm, Brian wrote:
> Hi Chen,
>
> I managed to compile kernel 2.6.25.
> When I ran it without vga=788, I see a shell prompt.
> The screen does not go to black one.
> But I keep getting the following message.
> [timestamp] android_power: wake
...
...
Kernel panic - not syncing: Fatal except in interrupt
Thanks,
Brian
On Mar 31, 8:02 am, Brian wrote:
> I tried vmware 6.5 workstation on windows 32 bit, vmware 6.5
> workstation on fedora core 8 64bit.
> Both did not work.
>
> I got where the kernel panic's happen
on in this case, which I'm attaching.
Do these warnings matter?
Thanks,
Brian
<6>[2.597463] EXT3-fs: mounted filesystem with ordered data mode.
<6>[2.608793] Atheros(R) L2 Ethernet Driver - version 2.0.5
<6>[2.609952] Copyright (c) 2007 Atheros Corporation.
<
font.o softcursor.o
By default, the kernel .config has
CONFIG_FB_FILLRECT=y
CONFIG_FB_COPYAREA=y
CONFIG_FB_IMAGEBLIT=y
I'm gonna change them to CONFIG_FB_=m, and see what will happen.
There are several inconsistencies in the repository...
What's your kernel .config look like?
Thanks,
Bria
'd like to install this application with GUI and to start it. How can
I do it?
Thanks,
Brian
On Mar 30, 10:54 pm, Brian wrote:
> Hi Chen,
>
> I managed to compile kernel 2.6.25.
> When I ran it without vga=788, I see a shell prompt.
> The screen does not go to black one.
&
ds to
exit
D/dalvikvm( 2126): DestroyJavaVM shutting VM down
D/dalvikvm( 2126): VM cleaning up
D/dalvikvm( 2126): LinearAlloc 0x0 used 2087468 of 4194304 (49%)
D/skia( 2126): purging 6K from font cache [1 entries]
Any suggestion?
Thanks,
Brian
On Apr 1, 5:13 pm, Chen Yang wrote:
> Cool.
H
Is AC_ONLINE_PATH the one we care about?
Thanks,
Brian
On Apr 1, 2:15 am, Androidphan wrote:
> This is why Android is not booting:
>
> I/SystemServer( 6925): Starting Battery Service.
> E/BatteryService( 6925): Could not open '/sys/class/power_supply/ac/
> online'
&g
Hi Chen,
Finally, Android booted successfully !
Thanks for all the help.
I need to connect to it using adb, but I don't know its ip address.
In my phone, I'm using an terminal emulator I downloaded from the
market...
Thanks,
Brian
On Apr 1, 9:13 pm, Chen Yang wrote:
> hi Brian
I'm playing with x86 android in the vmware.
The mouse does not work. Is this the case?
I'm using keyboard. What's the keyboard button that's corresponding to
the menu button on the phone?
Thanks,
Brian
On Apr 1, 9:13 pm, Chen Yang wrote:
> hi Brian:
> You may ne
Hi Shlee,
In the end, I used 2.6.27. But 2.6.25 should also work.
The way I addressed the fb problem is to build and use the latest
intel drm driver modules.
Afterwards, you need to modify init.rc and some service files as
posted in this mailing list.
-Brian
On Apr 9, 7:58 am, shleeforandroid
I'm working with USB mass storage on an omapzoom target with android 1.5. The
android-developers list suggested that android-porting would be a more suitable
place for my question. So here it is: When I plug in the USB, press the MENU
button, and select "Notifications," the "USB connected" optio
PPP is not mandatory for data connection. That's depend on the modem
you use. In fact, ro.radio.use-ppp is default as "no".
Even using PPP, you don't need set ro.radio.use-ppp to "yes". You can
launch pppd to setup data connection when PDP context is successfully
activated (i.e. RIL_REQUEST_DEFAU
I set up the ac and usb power supply drivers, it
worked as expected.
Ciao,
Brian
On Wed, May 20, 2009 at 11:54 AM, Brian Cavagnolo wrote:
> I'm working with USB mass storage on an omapzoom target with android 1.5. The
> android-developers list suggested that android-porting woul
The command socket (s_fdCommand) will be closed only when there is any
exception like EINTR or end of stream (e.g. service layer close this
socket).
The sequence is like this:
1. Bootup
1.1 Init process create UNIX domain socket on /dev/socket/rild and
then fork RILD according to init.rc
1.2 RILD
It's vold (or mountd if you are using an old version) to mount your SD
card for you according to configuration defined in /etc/vold.conf.
Take a look in /sys to see whether your SD card is correctly
recognized in kernel (/sys/class/mmc_host/mmc0/mmc0:/block/
mmcblk0/..., mmc0 assuming you ar
>From log, it seems that it was caused by "exception" when launching
ActivityManager Service:
> W/dalvikvm( 1541): threadid=17: thread exiting with uncaught exception
> (group=0x4000fe70)
> E/AndroidRuntime( 1541): Uncaught handler: thread ActivityManager
> exiting due to uncaught exception
> E/An
Maybe you can trial to change your driver to generate input events
like below:
(EV_ABS, 0x, 0x0189) - 0x means "ABS_X" (X axes), 0x0189 the
absolute X value of pen point
(EV_ABS, 0x0001, 0x001c) - 0x0001 means "ABS_Y" (Y axes), 0x001c the
absolute Y value of pen point
(EV_KEY, 0x014a, 0x00
Looks like your RIL HAL (libreferen-ril.so) was loaded but didn't open
the serial connection with modem successfully.
Check mainLoop() in reference-ril.c, make sure you successfully open
the serial port (i.e. fd >= 0). If that's true, put some log in
initializeCallback() which will do some initia
Make sure ALSA is enabled in your kernel configure. If yes, check your
kernel boot log. If you get your audio working in ALSA level, then
there should be:
ALSA device list:
#0:
On Jun 17, 12:57 pm, muneendra kumar wrote:
> Hi all,
>
> Iam using imx31 on my custom board.
>
> Iam using the
Check /etc/vold.conf or /etc/mountd.conf (depend on how old your
Android code are) to correctly setup media volume in case you want to
mount the vfat partition to /sdcard
On Jun 16, 8:56 pm, xro wrote:
> hello,
>
> i have android's files on my sdcard. I boot with the initial file
> system and af
ent SIM_STATE_CHANGED_ACTION
> NOT_READY reason null
> D/RILJ( 756): WAKE_LOCK_TIMEOUT mReqPending=0 mRequestList=1
> D/RILJ( 756): 0: [0] GET_CURRENT_CALLS
> D/STK ( 756): StkAppService$ServiceHandler: OP_BOOT_COMPLETED
>
> As if there is something wrong with the data c
119
120 on property:wlan.driver.action=load
121 write /sys/bus/platform/drivers/s3c2440-sdi/bind s3c2440-sdi
122 setprop wlan.driver.action -1
123
124 on property:wlan.driver.action=unload
125 write /sys/bus/platform/drivers/s3c2440-sdi/unbind s3c2440-sdi
126 setprop wlan.driver.action -1
I got the same problem when working with HuaWei E180 USB dongle. With
some debugging, it seems that it stuck in kernel code "tty_set_ldisc",
i.e. when pushing PPP line discipline.
No root cause identified yet. But I workaround this by using ttyUSB1
for AT and ttyUSB0 for PPP. In most case, modem
You can find an ARMv4T compatible build on http://git.koolu.org . It's
a build that's targeted for the Openmoko Freerunner.
Regards,
Brian Code
On 28-Jul-09, at 3:49 AM, age ice iv wrote:
>
> can someone have some advi
dded since then).
Thanks,
- Brian Gupta
New York City user groups calendar:
http://nyc.brandorr.com/
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
Hi Nate:
I tried to porting Android from Froyo to Gingerbread and had the same
issue here.
Could you give me more details about the rtc driver issue?
Thanks.
Best Regards,
Brian.
On 5月23日, 上午10時20分, Nate H wrote:
> It is a rtc driver issue. You'd better check your rtc drvier.
>
&g
Hi Nate:
Thanks for your information, it was really useful.
There was a bug on my rtc driver when hctosys try to read rtc time.
Best Regards,
Brian.
On 6月8日, 上午11時57分, Nate H wrote:
> Hi Subnike:
> I didn't port RTC driver to kernel, so I get this error. After I fix it, my
> bo
out of the questions right now.
Thanks for any help!
-Brian
On Wednesday, July 22, 2015 at 10:35:19 AM UTC-4, Raul Piper wrote:
>
> Hi Jaimin,
> Is your allwinner a20 processor listed under the list of Processors(Soc)
> mentioned in the list of AOSP(android Open Source kernel) ke
; section describe the major Hardware Abstraction Layer
> (HAL)
> interfaces that you will need to implement when you port to a new device.
>
> On Thursday, September 3, 2015 at 5:33:29 PM UTC-7, Brian Yee wrote:
>>
>> Hi Raul,
>>
>> So if I wanted to build for th
[DYChen <[EMAIL PROTECTED]>]
>
> Brian,
>
> You mentioned on Oct 21 that Google has done some native x86 port of
> Android. Do you know when the code related to the native x86 port will
> be released to the Android Open Source Project? We are interested in
> gettin
All source is available from http://source.android.com/
Please follow the download directions there.
The porting guide's reference to google contacts, rsa keys, etc is all
obsolete now. We will be updating that document to correct / remove
the incorrect / outdated bits at some point.
[dvyjones
s this at run time? TIA!
init contains a sort of "micro udev" that listens to the kernel UEVENTs
and populates /dev, manages permissions, etc.
Brian
--~--~-~--~~~---~--~~
unsubscribe: [EMAIL PROTECTED]
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
This should not be fatal -- libhgl is the hw openglES library for msm7k
and the system will happily fail over to the software gl implementation
if it can't load this library.
[Anson <[EMAIL PROTECTED]>]
> 639 E/GLLogger( 441): couldn't load library (Cannot find
> library)
>
> seems like a lib
e's a fix for this floating around that hasn't made it to the open
source tree yet. We're still dealing with the final transition of some
work in progress from our (legacy) p4 source control to the open tree
(where future work will be happening). More details about this soon.
David,
I'd need to check, but I'm not sure all the cortex/armv7 support is in
the gcc mainline yet, so we might well be looking at the codesourcery
based stuff in the near term. I'm sure anyone looking at OMAP3, MSM8K,
etc will want ARMv7 support.
[David Turner <[EMAIL PROTECTED]>]
> On Fri, N
over time we can reduce the footprint of the
core platform (by a combination of putting various modules on a diet
and also making the core build more configurable so unneeded components
may be more easily omitted).
Brian
[David Turner <[EMAIL PROTECTED]>]
> There is absolutely zero cha
eded devices or it should provide libraries to
provide shims for emulator-specific stuff.
Brian
--~--~-~--~~~---~--~~
unsubscribe: [EMAIL PROTECTED]
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
Shankar <[EMAIL PROTECTED]>]
>
> Where I will get Android toolchain source? Does it have some howto for
> rebuild??
>
> Is it possible to get patches from code sourcery and apply it to
> Android toolchain?
>
> Shankar
>
> On Nov 14, 8:20 pm, Brian Swetland <[EMAIL PROT
> On Nov 14, 9:18 pm, Brian Swetland <[EMAIL PROTECTED]> wrote:
> > http://android.git.kernel.org/pub/android-toolchain-20081019.tar.bz2
> >
> > A README and configure script at the top level should guide you through
^^^
> > rebuildi
pmem is only needed for certain devices requiring large physically
contiguous memory on the msm7k (gpu, dsp, etc). It's not currently
used by any other SoCs and its absence is not a fatal error.
libhgl.so is the (proprietary) library for openglES on the msm7k
GPU. It also is not required for c
y the
greater public can start building, testing and submitting patches there,
which can be further refined and pushed to Google (if sufficiently generic).
Hopefully Gerrit2 will alleviate having to do this in the future.
Regards,
Brian Code
On Tue, Dec 2, 2008 at 11:28 AM, Sean McNeil <[EMAIL P
the adb gadget driver to allow adb to work over usb?
The writeup (very nice) implies that's not done yet.
Brian
[Peter McDermott <[EMAIL PROTECTED]>]
>
> Hi, all,
>
> We ported the Android open-source release to the Nokia N810. This
> involved patching the 2.6.25 Linux k
robably hunt down and work around those issues).
It'd be nice to get the n8x0 patches updated for 2.6.27 as that's where
our current kernel development is happening at the moment, but currently
there's no requirement for .27 specific features or major chang
This is a bug. That code should be adjusted to fail gracefully instead
of throwing a fatal exception, if there is no battery info. Also, it
probably should not hardcode the "battery" part of the path, but rather
observe any power_supply entities that exist.
[borhe <[EMAIL PROTECTED]>]
>
> Hi!
You will need to either download them separately using a git-clone
operation, or by editing the platform/manifest.git default.xml file. We have
added the ALSA stuff to the Openmoko Freerunner port at
http://git.koolu.org. The example manifest git can be found there.
Regards,
Brian Code
On Mon
[Brian Code <[EMAIL PROTECTED]>]
> You will need to either download them separately using a git-clone
> operation, or by editing the platform/manifest.git default.xml file. We have
> added the ALSA stuff to the Openmoko Freerunner port at
> http://git.koolu.org. The example m
rd library for the particular hardware, which is not actually
here, but in the vendor/qcom/surf repository.
Brian
[clem ]
>
> Hi
>
> I am interested in the bootloader code in android,but meet some
> problems.Could anybody give me some help?
> My questions are as follows:
>
not
copy the various proprietary bits (or to copy the proprietary bits for
the other target, as the case may be).
Brian
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
back to the Android mainline.
Hope that helps.
Cheers,
Brian Code
On Wed, Dec 31, 2008 at 9:06 AM, twebb wrote:
>
> >> Is something broken or did I miss a step?
> >
> > 5. in vendor/htc/dream/ there is a script that must be run (from that
> directory) to extract som
There is a successful port that builds for the Openmoko Freerunner ARM4T
platform and can be found at http://git.koolu.org
Regards,
Brian
On Tue, Jan 6, 2009 at 7:44 AM, David Turner wrote:
> The sources on the cupcake branch on the open source repository already
> include support for
/ac
> /sys/class/power/usb
>
> Use logcat and see what is going on when it tries to read the initial
> battery values and starts watching for uevents.
Android *really* should scan /sys/class/power to see what's there and
not hardcode the power supply names. This is a bug but
The emulator only implements the "goldfish" platform. If you want to
test a kernel that targets a specific SoC, you'd need an emulator that
actually emulates that specific hardware or to test it on the actual
board.
Brian
[Abhishek Jain ]
> Hi all
>
> I have gen
adding
more properties.
It might not be unreasonable to have the generic power code check for
/sys/class/backlight/... (scan, not look for hardcoded names like eeepc)
and if it doesn't find something there, see if there's a
/sys/class/leds/lcd-backlight/...
Picking up the max v
r to libhardware_legacy last week. Over time these
APIs will migrate to the new libhardware, eventually leaving
libhardware_legacy empty.
Brian
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
I think David is confusing the transport-over-IP feature which adbd on
the device will fail back to if it can't open the usb device driver with
the local adb control socket on the device which was disabled to avoid
possible security issues (potentially giving untrusted apps debugging
access to th
nt the connection manager to use GPRS.
Currently the connection manager is only really prepared to deal with a
single active network interface. Obviously this is too limited for a
number of situations and there are plans to make it much more flexible
in the future, but
The 1.0/cupcake sources do not have specific tethering support included,
but in general this could be done by using any number of transports
(ethernet over usb, ethernet over bluetooth, ppp over bluetooth,
wifi, etc) and the usual facilities in the linux kernel for routing/
NATing/etc.
The conn
sources
to verify this).
It's expected that the init process started from initramfs will know how
to get everything else going. In the android world, this involves
/init.rc scripting what to mount where, etc.
Brian
[ebmajor ]
>
> Dear all,
>
> I'm trying to understand how init
sam
I build the img for EPC904HD and got blackscreen too. but chen said build
the kernel with additional configuration can help. But looks my kernel
source from google is not match with prebuild driver from eeepc_701 source
tree.
Best Regards,
Brian
2009/2/11 bo wang
> hi ,
>
> you
But my i915 driver doesn't have modeset param. Besides, all the drivers in
vendor/asus/eee_701 are inconsistent with my kernel. Is your kernel version
2.6.25?I checked android.git.kernel common.git, i915 driver doesn't declare
any PARAMs.
Best Regards,
Brian
2009/2/11 Jackie Wu
&g
7; option for android is?
Nothing special really. I used "mem=101M console=ttyMSM2" on 7201A
SURF, for example.
> Really my best regards.
> Peter Oh
>
> -Original Message-
> From: android-porting@googlegroups.com
> [mailto:android-port...@googlegroups.com] On
You can also pass the initramfs location and size to the kernel via
ATAGs in ARM builds. Please see my previous replies to this thread and
the arm booting documentation in the kernel docs directory.
[Peter Oh ]
>
> Thanks! Brian,
>
> This is my knowledge so far about initram
its current implementation) the recovery
code is going to be one-size-fits-all. I think customizing it for your
specific situation is reasonable. In many environments it might not be
used at all (some OEMs may prefer to handle recovery/fota
Regards,
Brian Code
On 6-Apr-09, at 12:07 AM, Saffron Labs wrote:
> Thanks Ben. We have a 920T based hardware and have commenced the
> porting. Just wanted to ensure that we don't encounter any "obvious
> surprises"!
>
> On Mon, Apr 6, 2009 at 11:29 AM, Ben Leslie
he way to go.
Also, bionic really should look as much as possibly like a "standard"
libc -- we should be careful not to expose internal-only headers or
implementation details needlessly and avoid depending on the same.
Brian
--~--~-~--~~~---~--~~
unsubs
There is an ARMv4 toolchain that can be found at: git.koolu.org in the
Prebuilt git. We currently use it for the Android on Freerunner
project with good success.
Regards,
Brian Code
On 20-Apr-09, at 2:06 AM, huymq85 wrote:
>
> Hi all, I'm compiling linux kernel android version
liblog in Android doesn't support "%I" format string for IP address.
I use below workaround:
notice("local IP address %I", go->ouraddr);
CHANGE TO
notice("local IP address %s", ip_ntoa(go_outaddr);
On May 16, 3:58 am, John Michelau wrote:
> A little more digging shows that the error, notice, et
93 matches
Mail list logo
