Hi, There could be many reasons it hasn't been awknoledged, perhaps the developer is trying to find the optimal way to fix it? or maybe it effects multiple chipsets?
It's also quite possible that he hasn't had a chance to review the patch yet, try reporting the bug via sendbug (..so it gets tracked). If you cannot use sendbug(1), it's possible to generate a template using the '-P' argument.. which you can then paste into your prefered MTA and mail it to 'gn...@openbsd.org', just use a blank subject line. Or, look at the "AUTHORS" section in ral(4). -Bryan.
