On 16/02/2015 01:17, Michaël Zweers wrote:
> It builds oke now,
>
> but its doesn't boot on my device. i don't get to see any (informative)
> boot error's (see log).
>
>
>
> John Crispin schreef op 15-2-2015 om 22:16:
>>
>>
>> On 15/02/2015 21:44, Michaël Zweers wrote:
>>>
>>> Hello,
>>>
>>>
What does that "sleep 60" do for you here? It doesn't look very sane to me.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Hi!
Tested on OM2P and TP-Link WDR3600, looks good: boots, nothing obviously
broken, wifi works, eth works, but I have not ran it more than 10
minutes each.
Greetings,
bruno
On 02/15/2015 07:49 PM, John Crispin wrote:
> Hi,
>
> i just pushed the v3.18 support for ar71xx. i have tested this on
>
I can confirm that it does work, i don't no where or why it didn't the
previous time. I did a clean clone and used a clean config and now
everything looks to be oké.
Bootlog is attached:
confirmed working:
Boot: Yes
Ethernet: Yes
WiFI: Yes
Luci: Yes (used to sc
John Crispin openwrt.org> writes:
>
> Hi,
>
> does anyone have one of these ->
> http://www.atmel.com/tools/ATSAMA5D3-XPLD.aspx
> that he wants to donate so that i have something to test at91 images on
Hi Josh,
Of course, I can surely do something for you ;-)
Let's arrange the shipment in pr
On 16/02/2015 11:52, Nicolas FERRE wrote:
> John Crispin openwrt.org> writes:
>
>>
>> Hi,
>>
>> does anyone have one of these ->
>> http://www.atmel.com/tools/ATSAMA5D3-XPLD.aspx
>> that he wants to donate so that i have something to test at91 images on
>
> Hi Josh,
>
> Of course, I can surel
On 16/02/2015 11:05, Michaël Zweers wrote:
> I can confirm that it does work, i don't no where or why it didn't the
> previous time. I did a clean clone and used a clean config and now
> everything looks to be oké.
>
> Bootlog is attached:
> confirmed working:
>
> Boot: Yes
> Ethernet:
To choose whether bulid or not RT288x PCIe bus driver, CONFIG_SOC_RT2880 is
wrong.
Here is its fix, and enables PCIe bus driver for some targets which have 2nd
WiFi chipset via PCIe bus.
signed-off-by: n...@ff.iij4u.or.jp
---
a/target/linux/ramips/patches-3.14/0031-PCI-MIPS-adds-rt2880-pci
I got work with this patch.
Ethernet switch (includes VLAN), WiFi connected via PCIe, LEDs, buttons.
In mtd partion map of DTS file, I renamed Linux firmware regions (kernel + root
squashfs) to “firmware”because it allows kernel to split kernel and roots and
rootfsdata.
signed-off-by: n...@ff.
On Mon, Feb 16, 2015 at 07:49:54AM +0100, Dirk Neukirchen wrote:
> - according to imx6 Makefile and u-Boot documentation is itb
> and probably should not be changed
> - this fixes build error if CONFIG_TARGET_ROOTFS_INCLUDE_FIT is set
> (missing .itb file)
> - use DTS_DIR (like in imx6 Makefil
A couple of Ubiquiti RouterStation Pros running custom build from r44462.
One is wifi bridge other is full-router.
So far all is OK (<1hr operation).
/ted
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/
Add the diag.sh file for failsafe LEDs.
Cleanup uci-defaults for network and LEDs.
Sets the "fault" LEDs in uci-defaults to off
Add the GoFlex Net "Board Name"
Remove kmod-rtc-marvell from default packages, as the GoFlex net does not have
a Real Time Clock.
V2 adds led "name" in uci-defaults mi
John,
I have been working with the AT91 target with a few boards, one of which
is our own custom Q70 board (http://www.exegin.com/pdf/q70_v01.pdf - if
you will pardon the crummy datasheet), and I have also been testing the
generic AT91 images on the Atmel AT91SAM9G20-EK.
We don't have any bo
I'm writing a driver for a family of 24 port gigabit switches, with a
wide array of interesting hardware features. Creating basic VLAN
membership and tagging functionality under the swconfig framework has
been quite easy, and this framework has been excellent for this.
However, I would like to su
On Mon, 2015-02-16 at 08:10 +0100, John Crispin wrote:
>
> On 16/02/2015 00:15, Paul Blazejowski wrote:
> > 00 KHz AUTO), (N/A, 2000 mBm), (0 s)
> > [ 21.73] cfg80211: (549 KHz - 573 KHz @ 16 KHz),
> > (N/A, 2000 mBm), (0 s)
> > [ 21.74] cfg80211: (5735000 KHz - 5835000
On Mon, 16 Feb 2015, Charlie Smurthwaite wrote:
I'm writing a driver for a family of 24 port gigabit switches, with a
wide array of interesting hardware features. Creating basic VLAN
membership and tagging functionality under the swconfig framework has
been quite easy, and this framework has bee
On 16/02/2015 21:47, Paul Blazejowski wrote:
> On Mon, 2015-02-16 at 08:10 +0100, John Crispin wrote:
>>
>> On 16/02/2015 00:15, Paul Blazejowski wrote:
>>> 00 KHz AUTO), (N/A, 2000 mBm), (0 s)
>>> [ 21.73] cfg80211: (549 KHz - 573 KHz @ 16 KHz),
>>> (N/A, 2000 mBm), (0 s)
>>>
Dear Fernando,
You should have posted this question to OpenWrt-User, but I will answer it here.
I haven't personally deployed such a configuration, yet. I don't think
you can do much besides enabling RTS/CTS at every CPE (client). Much
fewer connected clients will be supported compared to a TDMA
Hi David,
On 16/02/15 21:03, David Lang wrote:
A work-around for many of the items other than the basic VLAN
membership and tagging is to force the traffic between the different
switch ports to go through the CPU by putting the different ports on
different VLANs and then using the kernel bridg
On 16.02.2015 22:03, David Lang wrote:
> On Mon, 16 Feb 2015, Charlie Smurthwaite wrote:
>
>> Specifically I am looking for opinion on whether the swconfig framework
>> is suitable for more advanced functionality, or whether there was likely
>> to be a move to any other upstream framework for swit
On 16/02/15 21:34, Dirk Neukirchen wrote:
There might be 2 interesting posts regarding current/future state and
development direction of In-Kernel drivers:
1) rejected in 2013: "net: phy: add Generic Netlink switch configuration API"
link: http://lwn.net/Articles/571390/
The thread might be of (
First, there are a lot of discussions and papers at netdev01.org about the
various hardware switch management systems. I point specifically to a talk
this morning:
https://www.netdev01.org/sessions/19
I have stumbed my toe on 3800 with trying to build tagged switch ports where
I have a few
I for one would love to see brctl and vconfig disappear completely in
favour of ovs-* based standard toolchain for all switch interaction.
Certainly in the Bigger iron area, and things like core and cumulus coupled
with SDN approaches and Openstack this is fast becoming defacto. I don't
see why wi
On Mon, 16 Feb 2015, Charlie Smurthwaite wrote:
Hi David,
On 16/02/15 21:03, David Lang wrote:
A work-around for many of the items other than the basic VLAN membership
and tagging is to force the traffic between the different switch ports to
go through the CPU by putting the different ports o
On Mon, 16 Feb 2015, Michael Richardson wrote:
I have stumbed my toe on 3800 with trying to build tagged switch ports where
I have a few ports with explicit VLAN tagging, joined together in the switch,
and also exposed to the host. I think it should work, but I mostly just wound
up screwing up
Having a more abstract way of managing this available is a nice option to have,
but I would hate to loose the ability to set things explicitly.
Keeping in mind that we are primarily dealing with low-end devices, anything
that requires more advanced chipsets just isn't going to happen. The chips
Hello bkil,
Many thanks for your detailed response.
I would gladly post it to openwrt-users if that worked, which doesn't
seem to be the case as far as I know.
But also taking the opportunity in this devel list to ask if anyone
worked of ever saw any work to develop a open TDMA implementation
Hi Toke, hi Alan,
On Feb 15, 2015, at 17:18 , Toke Høiland-Jørgensen wrote:
> Sebastian Moeller writes:
>
>> Not that I have shown great taste in the past, but I think it
>> would be somewhat cleaner to put the logic into the hot plug script
>> and keep run.sh “simple” (in the past I had
This is needed by many services to function properly and as
all modern distributions got it enabled, it starts to be a
de-facto standard.
The kernel binary size increases only a little:
On ARM systems comes down to 800 bytes uncompressed and about
200 bytes compressed size.
On MIPS systems it's abo
29 matches
Mail list logo
