HELLO

HELLO

[Rudolph Moseley]

After the Bell News to Send HXPN Flying!!!

ENCINO, CA--(MARKET WIRE)--Jan 5, 2007 (4:05pm) -- Harris
Exploration, Inc. (Other OTC:HXPN.PK - News) advises shareholders it
has authorized a Letter of Intent with Minera Cristal of Ecuador, regarding
the opportunity to acquire up to a 100% position in their Balsapamba
property, located in the Bolivar Province, Ecuador, South America.

Harris Exploration

Symbol: HXPN
Current Price:     $1.50 (+20%)
Short Term Target:  $5.00

With the price of precious medals continuing to skyrocket, mining
companies had another year of record profits.  With limited supply and
high demand, experts agree that the mining boom shows no signs of
abating.

Harris Exploration is in the right place at the right time and has just begun
a major PR campaign to let everyone know about it!  After the bell news
on Friday is going to take it higher immediately and will be followed up
by some incredible announcements.  We give this one a STRONG BUY!

Get in while there is still time!!!


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

Hello

[l9jj]

Hello guys, i am debuging the alsa. After I insmoding the codec.ko pcm.ko i2s.ko into the kernel I can get the device node : /dev/pcmC0D0p and /dev/pcmC0D0c and /dev/controlC0 and /dev/timer .i create the link
Ln -s /dev/pcmC0D0c /dev/snd/pcmC0D0c
Ln –s /dev/pcmC0D0p /dev/snd/pcmC0D0p
Ln –s /dev/controlC0 /dev/snd/controlC0
Ln –s /dev/timer /dev/snd/timer
but it failed when I executed
aplay Noise.wav.
I use the shell cmd strace to follow it and found the Segmentation Fault will take place when call the open(“/dev/snd/controlC0”,O_RDONLY|O_CLOEXEC),so my question is how should I check the node /dev/snd/controlC0 is correct?
Thanks for any suggestion.
Best Regards

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Hello

[Michael Jordan]

Hello all,

I am involved in a university project using a TI OMAPL138 EXPKIT
(Logic PD Zoom Board) to create a sound processing box. I am tasked with
developing the code to replace the TLV320AIC3106 with a PCM3168A due to
the greater ADC/DAC count. We have already accomplished the hardware
end, and I have been exercising my linux skills at trying
to put this together. I found this list and subscribed, and I am glad I
sat and listened for a bit before I said anything. 457 patches in the
last 10 days! My fingers would fall off!

I will get together what I have been working on (2 files
pcm3168a.c and pcm3168a.h) and post them. I have some questions,
obviously, but I will follow up with them in a bit. If someone could
help me along it would be greatly appreciated. Or if I can just provide
some relevant information, I would be happy to do that as well.

Thanks,

Michael

Hello

[Michael Jordan]

Hello Gururaja,

If I am trying to ask some questions about the alsa system, do I need
to copy somebody directly to get a response? I have posted about 4
questions on the group in the last few months, and I have not even
gotten a slap on the hand.

The reason I am contacting you is you have mentioned working on the
TLV320AIC3X which is the chip used on the OMAPL138 board that we have.
I am attempting to write a driver for a PCM3168A which we have already
constructed a board for, and plugs into the 100 pin audio expander
connecter. I have the basic draft of a driver, but everything in the
code seems to be fairly strongly coded for the DA850 boards to use the
TLV320AIC. I can prevent it loading, and my module will load, but
things are not "connecting" internally. I assumed that I would need to
make some changes in the arch/arm/mach-davinci/board-da850-evm.c.

However what I am running into is chasing me up a trail that eventually
has me modifying mach-types.h and creating a whole new board
configuration. I said ok, so I copied board-da850-evm.c to
board-da850-evm-mod.c which made it necessary for me to begin modifying
some Kconfig's, etc., and I still cannot get the kernel to compile with
the new kernel driver.

I just need to know, am I heading down the wrong path with this? I have
a pcm3168a.c and pcm3168a.h which have a basic structure for the new
codec, but I cannot figure out how to get the system to actually use it
because it basically appears that the TLV320AIC3X is "hard-wired" into
the system.

Help please,

Michael

Re: Hello

[Daniel Mack]

On 12.09.2013 05:12, Michael Jordan wrote:
> If I am trying to ask some questions about the alsa system, do I need
> to copy somebody directly to get a response? I have posted about 4
> questions on the group in the last few months, and I have not even
> gotten a slap on the hand.
> 
> The reason I am contacting you is you have mentioned working on the
> TLV320AIC3X which is the chip used on the OMAPL138 board that we have.
> I am attempting to write a driver for a PCM3168A which we have already
> constructed a board for, and plugs into the 100 pin audio expander
> connecter. I have the basic draft of a driver, but everything in the
> code seems to be fairly strongly coded for the DA850 boards to use the
> TLV320AIC. I can prevent it loading, and my module will load, but
> things are not "connecting" internally. I assumed that I would need to
> make some changes in the arch/arm/mach-davinci/board-da850-evm.c.

In general, you shouldn't have any audio specific code in
arch/arm/mach-davinci/*.

> However what I am running into is chasing me up a trail that eventually
> has me modifying mach-types.h and creating a whole new board
> configuration. I said ok, so I copied board-da850-evm.c to
> board-da850-evm-mod.c which made it necessary for me to begin modifying
> some Kconfig's, etc., and I still cannot get the kernel to compile with
> the new kernel driver.
> 
> I just need to know, am I heading down the wrong path with this? I have
> a pcm3168a.c and pcm3168a.h which have a basic structure for the new
> codec, 

For reviews, please post patches against the current mainline linux git
tree to this list.

> but I cannot figure out how to get the system to actually use it
> because it basically appears that the TLV320AIC3X is "hard-wired" into
> the system.

Consider the following basics:

- board files in arch/arm/ should only contain basic machine-specific
hardware setup (including i2c/spi device matching)
- in ALSA, things are structured in machine, platform and codec parts,
which are separated from each other in order to make them system and
platform generic. Make sure to read Documentation/sound/alsa/soc/* for this.

Also note that traditional board files are going away. If you want your
platform to be future-proof, start using device-tree files to describe
your board. As a starting point, have a look at
arch/arm/boot/dts/da850-evm.dts in the current mainline kernel git.

With the upcoming simple-card DT support, you might even be able to
avoid writing an ASoC maschine driver altogether.


Daniel