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