Ian Darwin schrieb:
On Nov 23 Roland Dreir sent a patch for interrupt handling, but it
doesn't apply on -current since the file rt2661.c changed slightly
a few weeks earlier (1.51, date: 2009/11/01).
This patch just changes Roland's patch to update against rt2661.c
r1.51 from the OpenBSD
On Nov 23 Roland Dreir sent a patch for interrupt handling, but it
doesn't apply on -current since the file rt2661.c changed slightly
a few weeks earlier (1.51, date: 2009/11/01).
two es in Dreier :)
This patch just changes Roland's patch to update against rt2661.c
r1.51 from the
On Nov 23 Roland Dreir sent a patch for interrupt handling, but it
doesn't apply on -current since the file rt2661.c changed slightly
a few weeks earlier (1.51, date: 2009/11/01).
This patch just changes Roland's patch to update against rt2661.c
r1.51 from the OpenBSD repository instead of
I've applied Roland's patch and it works for my ral(4) device:
l0 at pci0 dev 14 function 0 Ralink RT2661 rev 0x00: irq 10, address
00:14:85:d5:39:bb
ral0: MAC/BBP RT2661D, RF RT2529 (MIMO XR)
On my Soekris Net5501, ral0 in ap mode would hang after a while and be
useless. Now it happily passes
On Sun, Nov 22, 2009 at 08:31:07PM -0800, Roland Dreier wrote:
The interrupt handling in ral(4) for RT2661 has a couple of problems,
which causes the interface to get stuck under heavy load with OACTIVE
set (the problems are likely especially severe on slow systems such as
my 600MHz VIA
Mind sharing your hostname.ral0 and the tools you use to trigger this
situation? I've tried hping, tcpbench, ping -f, rsync, etc to no avail.
max ~8000 intr/s with hping
2.5MB/s with scp
hostname.ral0 is:
inet 10.2.0.1 255.255.0.0 NONE \
mode 11g \
mediaopt
Hi Damien / OpenBSD devs,
Did anyone get a chance to look at this diff? These fixes are the
difference for me between ral being usable as an AP and getting stuck
almost immediately under heavy load. Is there anything I need to do
to get this committed?
Thanks,
Roland
On Mon, Nov 30, 2009 at 10:56:29AM -0800, Roland Dreier wrote:
Hi Damien / OpenBSD devs,
Did anyone get a chance to look at this diff? These fixes are the
difference for me between ral being usable as an AP and getting stuck
almost immediately under heavy load. Is there anything I need to
On 2009/11/30 20:33, viq wrote:
On Mon, Nov 30, 2009 at 10:56:29AM -0800, Roland Dreier wrote:
Hi Damien / OpenBSD devs,
Did anyone get a chance to look at this diff? These fixes are the
difference for me between ral being usable as an AP and getting stuck
almost immediately under
Does it do anything for 2860? I have that as an AP now and every once in
a while it stops working, I need to restart the interface.
No, the driver code is a completely different C file. It's possible
there are analogous bugs for 2860 though, since the hardware and
driver are both closely
The interrupt handling in ral(4) for RT2661 has a couple of problems,
which causes the interface to get stuck under heavy load with OACTIVE
set (the problems are likely especially severe on slow systems such as
my 600MHz VIA system); bouncing the interface down and back up fixes
things. As I
By the way, I forgot to mention that even with this patch applied, I
do have one odd problem with ral on my system -- after some time
(hours it appears), the ral interface stops being able to send
multicasts/broadcasts. All other traffic works fine, including
receiving multicasts, but no
12 matches
Mail list logo
