Has anyone used OpenWRT Linux 3.3.8 kernel, and the included FTDI serial port
interface driver with the Power PC.
I suspect there are byte swapping issues, and would like to know if anyone else
has 'used' the driver and 1) had no problem... or 2) had and fixed a problem.
Thanks
John Clark.
___
ARM Linux PCI/PCIe hardware intialization needs to occur before device_init
as it does not support hotplug. I have modeled the cns3xxx PCIe init after
other ARM platforms. Registering it early resolves resource issues occuring
during bus enumeration that occur when a device driver is linked stati
On Wed, Oct 10, 2012 at 4:25 AM, Felix Fietkau wrote:
> On 2012-10-09 3:00 AM, Tim Harvey wrote:
> > Moving the PCIe hw initialization to an early init call allows PCI based
> > devices to be used when built as static. An example of where this is
> needed
> > is when using PCI based UARTs such a
On 30 October 2012 23:00, Hannu Nyman wrote:
> The bug tracker is again down, so I am sending this here.
>
> Looks like a change introduced yesterday has broken libubox compilation for
> buildbots & some users. Forum discussion here:
> https://forum.openwrt.org/viewtopic.php?id=40213
>
it depends
The bug tracker is again down, so I am sending this here.
Looks like a change introduced yesterday has broken libubox compilation for
buildbots & some users. Forum discussion here:
https://forum.openwrt.org/viewtopic.php?id=40213
My diagnosis in a forum message:
It is coming from libubox rel
On Tue, Oct 30, 2012 at 09:03:29AM -0700, Tim Harvey wrote:
> I'm not finding documentation but it looks to me like the return 1
> signifies that you have consumed that param and it shouldn't be sent to
> other init functions. Like you I looked at other code and found them to
> all return 1 so did
Dne 23.10.2012 16:45, Stefan Hellermann napsal(a):
> Hi,
>
> zabbix_agentd will not start because the initscript checks an old
> path to the configfile and then zabbix_agentd uses the new path.
> (old /etc/zabbix/zabbix_agentd.conf new /etc/zabbix_agentd.conf)
> I think the new path is better as
nbd,
It seems your patch is not compatible with EGLIBC :
cp: cannot stat
'/var/www/LOG/openwrt/tpl703n/trunk/staging_dir/toolchain-mips_r2_gcc-4.7-linaro_eglibc-2.16/lib/libthread_db-2.16.so':
No such file or directory
and the following file is created : libthread_db-1.0.so
22-Oct-2012 12:30 39
On 30 October 2012 02:27, Catalin Patulea wrote:
> On Mon, Oct 29, 2012 at 5:30 AM, Roman Yeryomin wrote:
>> Bump dropbear version.
>> 400-CVE-2012-0920.patch is now in upstream.
> Beat you to it ;-) And with more Makefile cleanup goodness:
> https://lists.openwrt.org/pipermail/openwrt-devel/2012
FYI
-- Forwarded message --
From: Justin Vallon
Date: 2012/10/29
Subject: [OpenWrt-Users] Wifi trouble
To: openwrt-us...@lists.openwrt.org
Found this in system log, wifi stopped working:
Oct 29 04:03:43 kiwi kern.err kernel: [14858.50] ath: phy0: Failed
to stop TX DMA, que
Luka,
I'm not finding documentation but it looks to me like the return 1
signifies that you have consumed that param and it shouldn't be sent to
other init functions. Like you I looked at other code and found them to
all return 1 so did the same.
Personally the right way to disable L2X0 is to ju
On Mon, Oct 29, 2012 at 03:03:55PM -0700, Tim Harvey wrote:
> L2 cache via L2X0 cache controller available on some ARM boards can
> provide a performance boost in some situations but decrease performance
> in others. This adds a kernel cmdline to disable L2X0 for the Laguna
> product family.
>
>
12 matches
Mail list logo
