init.goldfish.rc question

by Luca Belluccini » Fri, 30 Jan 2009 19:16:03 GMT


Sponsored Links
 For testing purposes (I'll use the emulator), I created a new target
(using vendor/manufact... structure) more or less equal to 'generic'
one.
I used make TARGET...=mydevice and all seems to work.
There's only a strange thing: init.goldfish.rc is still called at init-
time.
I would like to launch my init.mydevice.rc ...

Android.mk
================================
LOCAL_PATH := $(call my-dir)

# kernel pre-built binary
ifeq ($(TARGET_PREBUILT_KERNEL),)
TARGET_PREBUILT_KERNEL := $(LOCAL_PATH)/kernel
endif

file := $(INSTALLED_KERNEL_TARGET)
ALL_PREBUILT += $(file)
$(file): $(TARGET_PREBUILT_KERNEL) | $(ACP)
        $(transform-prebuilt-to-target)

# keyboard layouts
file := $(TARGET_OUT_KEYLAYOUT)/tuttle2.kl
ALL_PREBUILT += $(file)
$(file) : $(LOCAL_PATH)/tuttle2.kl | $(ACP)
        $(transform-prebuilt-to-target)

# keymap
include $(CLEAR_VARS)
LOCAL_SRC_FILES := tuttle2.kcm
include $(BUILD_KEY_CHAR_MAP)

# board specific init.rc
PRODUCT_COPY_FILES += \
        $(LOCAL_PATH)/init.osstbox.rc:root/init.mydevice.rc

# prebuilt drivers
PRODUCT_COPY_FILES += \
        $(LOCAL_PATH)/fake.ko:system/lib/fake.ko

BoardConfig.mk
=================================
# config.mk
#
# Product-specific compile-time definitions.
#

# The generic product target doesn't have any hardware-specific
pieces.
TARGET_NO_BOOTLOADER := true
TARGET_NO_KERNEL := true
TARGET_NO_RADIOIMAGE := true
HAVE_HTC_AUDIO_DRIVER := true
BOARD_USES_GENERIC_AUDIO := true
USE_CAMERA_STUB := true
TARGET_PROVIDES_INIT_RC := true

mydevice.mk
==================================
# Superclass
$(call inherit-product, build/target/product/generic.mk)

# Overrides
PRODUCT_BRAND := mydevice
PRODUCT_DEVICE := mydevice
PRODUCT_NAME := mydevice

--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



init.goldfish.rc question

by Andrew Green » Fri, 30 Jan 2009 20:12:08 GMT


 The name used to pick up the device-dependent init file is the name returned by 
/proc/cpuinfo under "Hardware" (it uses the first word only - as lowercase), 
which is set with the MACHINE_START() macro in your board file. You can change 
the name in that macro to "mydevice" to use init.mydevice.rc.

Andrew


_________________________________________________________________
Windows LiveHotmailore than just e-mail. 
 http://windowslive.com/howitworks?ocid=TXT_TAGLM_WL_t2_hm_justgotbetter_howitworks_012009 
--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---


Sponsored Links


init.goldfish.rc question

by Luca Belluccini » Sat, 31 Jan 2009 12:16:06 GMT


 Thank you.
For 'your board file' you are pointing to kernel goldfish board source
files?



--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



init.goldfish.rc question

by Luca Belluccini » Sat, 31 Jan 2009 14:46:08 GMT


  noticed that only the specific file called
init.goldfish.sh
can be executed. If you try to define your file and execute it at init
process, a permission denied error occurs.
My question is: this "problem" occurs due to my target is derived from
goldfish (emulator)?

On 31 Gen, 13:15, Luca Belluccini <lucabellucc...@gmail.com> wrote:
--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



init.goldfish.rc question

by Luca Belluccini » Sat, 31 Jan 2009 14:57:54 GMT


 here should be some permission restrictions defined by
system/core/include/private/android_filesystem_config.h (at line 147:
"{ 00550, AID_ROOT, AID_SHELL, "system/etc/
init.goldfish.sh" },")
Why only these names? This stuff is goldfish target only?

On 31 Gen, 15:45, Luca Belluccini <lucabellucc...@gmail.com> wrote:
--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



init.goldfish.rc question

by Andrew Green » Sun, 01 Feb 2009 00:35:46 GMT


 ep. 

I was under the impression that you were porting to a new device. I see from
your later questions that you may be sticking with the emulator. This
information probably won't help you much if you are not building your own
kernel. Perhaps others will jump in with better advice.

Best regards,
Andrew


_________________________________________________________________
Windows LiveHotmail:ore than just e-mail.
http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t2_hm_justgotbetter_explore_012009
--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Other Threads

1. Camera preview and sensor orientation values

Hi all,

I'm trying to use Camera preview in combination with Orientation
sensor. I got a serious problem with the sensor when using the
preview: values returned by the sensor are as (1.6893509E-9, -4.0,
0.0) instead of being in degrees (especially the former).

I tested that not creating the preview in which will reside the camera
output (class Preview extends SurfaceView implements
SurfaceHolder.Callback) , the sensor results are in range 0:360,
prefectly.

Is it possible that opening the camera could  generate errors in
sensor calculations ?

Does anyone has an idea ?


Thanx to anyone could help!
--~--~---------~--~----~------------~-------~--~----~

2. How drawing cache in View works

Can you please tell me how does android determine when View should
enable the drawing cache?

I try calling in my class (which inherits form LinearLayout)

Bitmap drawingCache = getDrawingCache();

I get a null in my drawingCache.

Thank you.








--~--~---------~--~----~------------~-------~--~----~

3. A question regarding Activities and Tasks.

4. error on booting android filesystem throughNFS

5. error on booting android filesystem through NFS

6. Connection between BpServiceManager and BServiceManager

7. SlidingDrawer issue #1?