Hi Weber,
>> > I now want to porting alsa to eclair.My board are smdk6410,the audio
>> > module are wm8987.
Do you have ALSA drivers for your board? I see it's a s3c6410 based
board, but I don't see any ASoC machine driver for s3c6410+wm8987 in
android kernel tree (at least 2.6.29).
> 1399 mmap
> I tried to make a hook in alsa.conf. Is this the right place for it?
It should be 'asound.conf', you can check below link for reference:
http://git.omapzoom.org/?p=platform/vendor/ti/zoom2.git;a=blob;f=asound.conf;h=6b3d6c1742559e3af1bac47e59b4d0bde6f9f839;hb=4ab009e3790922961d4bf3f8b4fd90f0e3ad8
you have any idea of how to go about in
> enabling ASOC for OMAP3EVM board?
> Thanks & Regards
> Aney
> On Tue, Nov 24, 2009 at 12:28 PM, Misael Lopez wrote:
>>
>> >> Q1.when i give : #alsa_amixer contents i see a lot of interfaces with
>> >> different
>> Q1.when i give : #alsa_amixer contents i see a lot of interfaces with
>> different values set as default.So before capturing audio do i need to
>> select a particular interface as capture source?Say for example i have
>> something like:
>>
>> numid=17,iface=MIXER,name='Analog Left Capture Route'
Ubuntu 9.10 doesn't include jdk5, but you can add the source list
entry from 9.04 (Jaunty).
1. Append the two lines shown below to your /etc/apt/source.list:
deb http://us.archive.ubuntu.com/ubuntu/ jaunty multiverse
deb http://us.archive.ubuntu.com/ubuntu/ jaunty-updates multiverse
2. Retrieve n
mixer controls are dependent of your hardware (not mentioned). You
should have some controls to specify active output path (like a mux)
or to enable speaker output (when hardware can route same audio to
different outputs). Do 'amixer controls', names are usually
self-descriptive.
-Misa
2009/10/1
2009/9/15 sunee :
>
> I am working on android for omap zoom2 target.
>
> When I play audio clips, playback is fine and audio is coming via
> headset connected.
> But I can only hear the audio from left channel, nothing is audible
> from right channel.
Plug and jack pinout should match. At first g
Rajesh,
The asound.conf you are using contains information of controls for
TWL4030 chip, and I think that´s not the one in your system. You need
to create a new asound.conf for your codec.
-Misa
2009/5/21 Rajesh N :
> Thanks,
>
> I appriciate if any relevent pointers given w.r.t my problem with
> I removed "WAKE_DROPPED" from all such key maps and was able to browse the
> android desktop, select and launch the applications. It was just a hit and
> try. Is this a right way? And what for this "WAKE_DROPPED"/"WAKE" used for?
>From
>http://android.git.kernel.org/?p=platform/development.git
Enrique,
> set bootargs console=ttyS2,115200n8 noinitrd mem=112M root=/dev/nfs rw
> nfsroot=10.87.230.178:/home/enrique/mydroid/out/target/product/
> ldp1,nolock,wsize=1024,rsize=1024 ip=dhcp init=/init
The path of your NFS filesystem seems incomplete. Please ensure you are
creating the filesyste
>[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 manifest git can b
I did a 'repo init ...' and 'repo sync' but neither alsa-lib nor
libaudio-alsa code is downloaded but they are showed in gitweb interface of
android code. Why arent they downloaded with default manifest? Did you add
entries for those projects in manifest file?
-Misa
2008/12/5 mvniekerk <[EMAIL PRO
> does this means that we need not
> requires inheriting from and modifying AudioHardwareInterface to
> support the driver-specific implementation.
No, ALSA userspace library contains the functions that you may need to
create your own AudioHardwareInterface implementation.
But if your driver is
Expanding comments... "mkimage" binary comes from u-boot compilation.
So first, compile u-boot and in /tools/ (not sure if this
is the exact path, but it's in tools dir) you will find this
"mkimage". Then just copy it to a directory you have exported in your
PATH.
Misa
2008/11/20 Rupesh Gujare <
> 2. I want to make a complete filesystem in a single directory which i
> can directly mount via nfs
> so assume "root" is the directory so shall i copy the contents of
> system to root/system & data to root/data
> & what about "symbols" ?
data directory is created by init.rc and populated the fir
You can take a look at:
https://omapzoom.org/gf/project/omapandroid/wiki/
There you can find a kernel tree plus some platform specific code.
Misa
2008/11/18 ganesh <[EMAIL PROTECTED]>:
>
> hai ,PLease give me a guidence to port android to ZOOM MDK (omap 3430
> board)
> >
>
--~--~-~--
Don't you think the enum problem is more related to "short enums"?
Have you tried to compile your code also with -fno-short-enums cflag?
Misa
2008/11/13 jyukon <[EMAIL PROTECTED]>:
>
> Hi,
>
> I had the same issues when I implemented UVC camera support. In my
> case,
> struct v4l2_requestbuffers
I have been working in that audio interface for ALSA in OMAP
processor, you can find our tree at:
http://git.omapzoom.org/?p=android/hardware/ti/omap3.git;a=summary
We have been successfully played and capture audio using TWL4030 chip
in OmapZoom board with that current version of the interface.
> What I did for that is
> to split the sdcard into 2 partitions: fat for user data like music,
> videos, etc, and ext3 for the /data partition.
Did you do something else apart from creating/formatting the
partitions? I tried the
same but Music application never accepted the card (even it the fat
I don't know how safe is this, but searching and removing the entry of
whatever you want to recompile in the following path:
out/target/product/NAME_OF_YOUR_PRODUCT/obj/
will force compilation next time you do 'make' in root directory.
Misa
2008/11/9 Anson <[EMAIL PROTECTED]>:
> make clean ; m
20 matches
Mail list logo
