Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for tag 'ral'

This is an experimental report containing PRs for tag 'ral' as of 4-16-2014. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.

This report is generated statically.

Please give feedback on this report to linimon@FreeBSD.org. Thanks.


PRs for tag 'ral':
SSubmittedTrackerResp.Description
o2013/11/19kern/184084net[ral] kernel crash by ral (RT3090)
o2013/05/08kern/178411wireless[ral] [panic] FreeBSD kernel crash in rt2860
o2012/07/22kern/170066wireless[ral] ral(4) rt61pci Linksys freezes the machine as soon as wpa_supplicant is started
o2011/03/12kern/155498wireless[ral] ral(4) needs to be resynced with OpenBSD's to gain RT2860/2870 support.
o2011/01/12kern/153937net[ral] ralink panics the system (amd64 freeBSDD 8.X) when in hostap or adhoc.
f2010/08/25kern/149969net[wlan] [ral] ralink rt2661 fails to maintain connection
o2010/02/05kern/143591net[ral] RT2561C-based DLink card (DWL-510) fails to work with ral0 in FreeBSD 8 Release [regression]
o2009/08/02kern/137372net[ral] FreeBSD doesn't support wireless interface from Asus Eee PC 1000H
o2009/05/16kern/134591[ral] ral(4) driver frequently loses carrier (on RT2560)
f2009/05/02kern/134168gavin[ral] ral driver problem on RT2525 2.4GHz transceiver + RT2560 MAC/BBP wireless
o2009/03/02kern/132238[ral] ral driver does not support RT2860
o2008/08/27kern/126895net[patch] [ral] Add antenna selection (marked as TBD)
o2008/06/06kern/124341net[ral] promiscuous mode for wireless device ral0 looses signal after ~30 mins (airodump-ng loses all stations after ~30 minutes)
o2008/03/24kern/122033net[ral] [lor] Lock order reversal in ral0 at bootup ieee80211com/ral0 [regression]
o2008/02/28kern/121174[ral] if_ral loses performance in FreeBSD 7 (RELENG_7)
o2008/01/15kern/119696[irq] [ral] ral device causes massive interrupt storm sometimes
o2007/04/10kern/111457net[ral] ral(4) freeze
o2007/02/16kern/109227[ral] ral(4) driver doesn't handle correctly RT2561C PCI chipsets - didn't work
o2006/04/08kern/95519net[ral] ral0 could not map mbuf
o2006/01/05kern/91364net[ral] [wep] WF-511 RT2500 Card PCI and WEP
f2005/06/20kern/82456gavin[ral] WITNESS warning/backtrace in if_ral
21 problems total.

Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.