On 22/01/12 02:45, Roman Yeryomin wrote:
On 17 January 2012 11:42, Helmut Schaa helmut.sc...@googlemail.com wrote:
@@ -313,6 +312,7 @@ ramips_eth_tx_housekeeping(unsigned long ptr)
struct net_device *dev = (struct net_device*)ptr;
struct raeth_priv *priv = netdev_priv(dev);
+
Hello,
22.01.2012 1:40, I wrote:
[...]
if matters). Without that, controller starts raising IN Token Received
with EP mismatch instead of normal Transfer complete bit. If I
understand it correctly, this means that Tx FIFO happened to be filled
in some particular order that controller disliked
On Wed, Jan 18, 2012 at 10:24 AM, Florian Fainelli flor...@openwrt.org wrote:
Hello,
On 01/18/12 08:47, Dave Taht wrote:
On Wed, Jan 18, 2012 at 4:42 AM, Otto Solares Cabreraso...@guug.org
wrote:
On Thu, Dec 08, 2011 at 11:57:46PM +0100, Hartmut Knaack wrote:
juhosg was working quite
On Sat, Jan 21, 2012 at 6:36 PM, Roman Yeryomin leroi.li...@gmail.com wrote:
On 21 January 2012 00:53, Marco Antonio Mauro marcu...@gmail.com wrote:
This patch adds support for the Sitecom WL-341 v3 and other Sercomm
IP1006RRv2 based boards for sysupgrade support and for the initial
flash
Hello,
On Sunday 22 January 2012 13:19:28 Álvaro Fernández Rojas wrote:
Hi guys,
There are some open tickets that contain patches which add support for
new brcm63xx boards. These tickets are #10732
https://dev.openwrt.org/ticket/10732 and #10764
https://dev.openwrt.org/ticket/10764.
In
Hi Aaron,
On 01/22/2012 04:54 AM, Aaron Z wrote:
Resending as I used the wrong from address last time and it bounced.
hmm at least I got your mails.
It loaded and booted, but I am seeing some oddities. Not sure if these are
related to being bleeding edge or what, but they are noticeable:
This adds support for Comtrend 5365. Open commits are
https://dev.openwrt.org/ticket/10732 and https://dev.openwrt.org/ticket/10717.
Also modifies increases the number of buttons supported by brcm63xx boards.
Directory to apply patch is: target/linux/brcm63xx
Signed-off-by: Álvaro Fernández
On Sunday 22 January 2012 14:45:45 Álvaro Fernández Rojas wrote:
This adds support for Comtrend 5365. Open commits are
https://dev.openwrt.org/ticket/10732 and
https://dev.openwrt.org/ticket/10717. Also modifies increases the number
of buttons supported by brcm63xx boards. Directory to apply
On Sunday 22 January 2012 14:45:45 Álvaro Fernández Rojas wrote:
This adds support for Comtrend 5365. Open commits are
https://dev.openwrt.org/ticket/10732 and
https://dev.openwrt.org/ticket/10717. Also modifies increases the number
of buttons supported by brcm63xx boards. Directory to apply
Ok, with a bit of further investigation, netlink doesn't actually seem too
difficult … is there a process for registering new support (i.e. NETLINK_DSL)
or is there some other way to do this? Could something else be re-used?
I'm happy to have a go at a sample implementation, but I'm completely
Hello,
I'm trying to add a new processor type (lexra), but having
trouble patching the config.sub, that checks for recognizable
cpu-os-kernel identifier, used in some packages.
More specifically, I want the config.sub in iptables-1.4.10 to
recognize the 'lexra-openwrt-linux'.
I'm working on the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
I need a same kind of magic to overcome this problem.
Is there any?
Yes, patch scripts/config.sub - that is whats fored upon each package.
Is the behavior of Modifying a generic build tool during a build
process for a single target
Got the wireless to work today. I followed the directions at
http://wiki.openwrt.org/doc/devel/debugging and ran killall -9 hostapd;
/usr/sbin/hostapd -dd /var/run/hostapd-phy0.conf /tmp/hostapd.log from a SSH
session, then tried to connect.
Before I ran it, I would get a connection failed
Jow,
Yes, patch scripts/config.sub - that is whats fored upon each package.
Yikes!!!
Thanks a billion!!! I've been caught in this trap for half a day.
Packages were built flawlessly.
Is the behavior of Modifying a generic build tool during a build
process for a single target considered
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Modifying the generic build tool to accept a new platform is certainly
legitimate, nobody wants to patch a new CPU definition into each single
package.
In general yes, in practice it should be unneeded though since we're
forced to replace
On 22 January 2012 14:13, Marco Antonio Mauro marcu...@gmail.com wrote:
On Sat, Jan 21, 2012 at 6:36 PM, Roman Yeryomin leroi.li...@gmail.com wrote:
On 21 January 2012 00:53, Marco Antonio Mauro marcu...@gmail.com wrote:
This patch adds support for the Sitecom WL-341 v3 and other Sercomm
In this patch:
* rename Argus leds to avoid underscores
* rename Belkin F5D8235 v1 leds from f5d8234 to f5d8235
* remove Belkin F5D8235 v1 status led defined as storage led (it was
defined as usb led earlier, just in wrong place) - it should have
router led as in v2
* add Argus, Sparklan and
On 1/21/12 1:18 AM, Lee Essen wrote:
On 20 Jan 2012, at 23:47, Philip Prindeville wrote:
I'd sure like to see netlink being used to communicate speed/carrier changes
up into userspace.
Unfortunately there's absolutely no netlink support in the lantiq driver and
I don't think any of
You probably want to go through 'netdev' (net...@vger.kernel.org) for changes
to Netlink.
On 1/22/12 10:35 AM, Lee Essen wrote:
Ok, with a bit of further investigation, netlink doesn't actually seem too
difficult … is there a process for registering new support (i.e. NETLINK_DSL)
or is
2012/1/22 Hauke Mehrtens ha...@hauke-m.de:
6. The Wireless LED on the WAP does not turn on
Probably something is wrong in the wireless driver.
There is a know issue with the wireless chip used in your device, but I
do not know, if you are seeing this issue or if it is already fixed:
BCM4321:
For those of us using x86-based platforms we'd like to have a way to do
in-place upgrades without losing configuration state.
I understand that (a) we are a smaller community, and (b) the sizing
constraints of x86 platforms is very different than (say) a WRT54G-L... memory
on a Alix or Geos is
On 22/01/12 02:04 AM, cptsp...@gmx.de wrote:
Hi!
Maybe you want to look at the ALIX boards by PC Engines. They fulfill
most of your requirements, but they one have 100 Mbit/s LAN.
Ingwer
On 2012-01-18 19:24, Weedy wrote:
Requirements:
- 500mhz or more
- 128mb ram+, DDR+
- 32mb
22 matches
Mail list logo
