2013/6/24 jonsm...@gmail.com jonsm...@gmail.com:
On Sun, Jun 23, 2013 at 5:50 PM, Flávio Silveira f...@terra.com.br wrote:
Good evening,
I'm trying to create a dts file for my router which is not supported yet
and I'm stuck on the definition of partitions.
Do I have to follow the same as
Thank you for your tip Florian,
I'm looking at DIR-645 DTS file, which seems to have the same flash layout
my router has.
On DIR-645 DTS file, it creates 6 partitions instead of 8: uboot,
uboot-env, factory, nvram, devdata and firmware.
I'm assuming I should need to do the same, so:
On Mon, Jun 24, 2013 at 4:53 AM, Florian Fainelli flor...@openwrt.org wrote:
2013/6/24 jonsm...@gmail.com jonsm...@gmail.com:
On Sun, Jun 23, 2013 at 5:50 PM, Flávio Silveira f...@terra.com.br wrote:
Good evening,
I'm trying to create a dts file for my router which is not supported yet
and
2013/6/24 jonsm...@gmail.com jonsm...@gmail.com:
On Mon, Jun 24, 2013 at 4:53 AM, Florian Fainelli flor...@openwrt.org wrote:
2013/6/24 jonsm...@gmail.com jonsm...@gmail.com:
On Sun, Jun 23, 2013 at 5:50 PM, Flávio Silveira f...@terra.com.br wrote:
Good evening,
I'm trying to create a dts
Is there a driver for Ralink I2S already in OpenWRT? I can't identify one.
If not, can someone with the Ralink SDK tell me if there is one in there?
I'd like to get Ralink I2S going if it can be done without a huge
amount of work.
--
Jon Smirl
jonsm...@gmail.com
I have enabled earlyprink and this not help. I think there is a
problem with toolchain or somethink else.
2013/6/23 Florian Fainelli flor...@openwrt.org:
Hi,
Le 23/06/2013 12:58, Jacek Kikiewicz a écrit :
I can see you are running kernel from memory.
I had similar problem when doing this.
2013/6/24 Artur Wronowski art...@gmail.com:
I have enabled earlyprink and this not help. I think there is a
problem with toolchain or somethink else.
Are you sure that you also enabled low-level debugging? I would rather
suspect a kernel configuration issue, or a memory configuration issue.
Thanks for reply.
Here is kernel configuration: http://pastebin.com/fbMAhi0k
I have enabled CONFIG_DEBUG_LL
2013/6/24 Florian Fainelli flor...@openwrt.org:
2013/6/24 Artur Wronowski art...@gmail.com:
I have enabled earlyprink and this not help. I think there is a
problem with toolchain or
I checked in the Ralink 3.3 SDK and don't see an I2S driver. Maybe no
one has written one?
On Mon, Jun 24, 2013 at 7:43 AM, jonsm...@gmail.com jonsm...@gmail.com wrote:
Is there a driver for Ralink I2S already in OpenWRT? I can't identify one.
If not, can someone with the Ralink SDK tell me if
I used a port for a similar board (cubieboard).
It works good for me with a external kernel tree.
You might want to look at this:
https://github.com/zioproto/openwrt-sunxi/tree/sunxi-rebased
It is pretty similar board, with ARM Cortex processor.
Saverio
2013/6/24 Artur Wronowski
This is not the way it works: the I2S bus only carries sound samples, the
command to control an I2S codec use a separate bus (I2C or SPI) to access the
codec registers, which in turn are not standardized in any way.
Thus, most codec chip require a specific driver: these are located into the
Also, I had initially thought that webcams were using the I2S
interface for their audio support. That doesn't appear to be the case,
most webcam have a controller chip that put both the video and audio
onto USB. That USB then carries the audio into the router chip.
Not sure how a phone based on a
Sorry, I thought it was simpler than that...
But I found a userland utility called i2scmd into the
RT288x_SDK/source/user/rt2880_app directory... So there should be something?
-- Michel
Le 24/06/2013 22:04, jonsm...@gmail.com a écrit :
Also, I had initially thought that webcams were using the
This may be it:
RT288x_SDK/source/linux-2.6.21.x/drivers/char/i2s
From README:
Ralink I2S Driver Release Note:
Version 1.0 : Initial version for this device driver.
This is for Ralink_ApSoC_SDK_3600_20110715.
-- Michel
Le 24/06/2013 22:11, Michel Stempin a écrit :
Sorry, I thought it was
On Mon, Jun 24, 2013 at 4:26 PM, Michel Stempin
michel.stem...@wanadoo.fr wrote:
This may be it:
RT288x_SDK/source/linux-2.6.21.x/drivers/char/i2s
That appears to be their I2S driver. That's sure not where I2S drivers
go in the kernel. They appear the have ignored ALSA. Looks like they
have
On the RT5350 the I2S pins and the full second UART are the same pins.
Use pinctl to swap their function - GPIO, I2S, UART. Pins are GPIO
7-10.
So if someone has a codec chip on a breadboard that they can easily
connect to those pins you can probably get I2S going in about a day. I
don't have a
Le 24/06/2013 22:52, jonsm...@gmail.com a écrit :
On the RT5350 the I2S pins and the full second UART are the same pins.
Use pinctl to swap their function - GPIO, I2S, UART. Pins are GPIO
7-10.
Yes, those pins are muxed.
So if someone has a codec chip on a breadboard that they can easily
Read some more about it, but I think this board should hook up to the
I2S pins on your AWM002-EVAL carrier board.
$30 I2S amp kit that you solder yourself. Dual inputs - I2S and USB.
There is some builroot for the beagle on github, you could use that source
as an external kernel tree. But it is 3.3 I think not 3.9.
On Monday, June 24, 2013, Saverio Proto ziopr...@gmail.com wrote:
I used a port for a similar board (cubieboard).
It works good for me with a external kernel
Thanks for your responses, but a few questions still remains.
1- I should keep partitions u-boot, u-boot env and devdata from stock
firmware, correct?
2- What the second parameter in reg means? Like 0x1 on the example
below:
partition@3 {
label = u-boot-env;
reg = 0x3
Can this be made to work on Ralink? When I have the adhoc0 interface
up bringing up ap0 says interface busy.
Does it work on Atheros?
root@OpenWrt:/etc/config#
root@OpenWrt:/etc/config# ifconfig ap0 up
ifconfig: SIOCSIFFLAGS: Device or resource busy
root@OpenWrt:/etc/config#
On 25.06.2013 00:15, Thomas Bächler wrote:
Am 18.06.2013 14:57, schrieb Steven Barth:
Allright fine, you guys have convinced me.
I just commited a modified version of that patch to trunk.
Please test it.
On AA, there's a missing line
proto_config_add_string ifaceid
in
22 matches
Mail list logo
