Re: Interrupt routing and friends ...

[Bill Hacker <wbh@xxxxxxxxxxxxx>]

9a9@mail.gmail.com>	 <4917cc5c$0$881$415eb37d@crater_reader.dragonflybsd.org> <ea7b9c170811092210p6f69b085n51c0fe0964c75eae@mail.gmail.com>
In-Reply-To: <ea7b9c170811092210p6f69b085n51c0fe0964c75eae@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 34
Message-ID: <4917d992$0$883$415eb37d@crater_reader.dragonflybsd.org>
NNTP-Posting-Host: 61.18.24.7
X-Trace: 1226299795 crater_reader.dragonflybsd.org 883 61.18.24.7
Xref: crater_reader.dragonflybsd.org dragonfly.kernel:13247

Sepherosa Ziehau wrote:
> On Mon, Nov 10, 2008 at 1:53 PM, Bill Hacker <wbh@conducive.org> wrote:
>> Sepherosa Ziehau wrote:
>>> On Mon, Nov 10, 2008 at 1:09 PM, Bill Hacker <wbh@conducive.org> wrote:
>>>> Sepherosa Ziehau wrote:
>>>>
>>>> *trimmed*   (good news in re 'head' having the missing stuff...)
> 
> We actually have bwi(4) one year ago, so it should be in 1.12/2.0
> release.  Since it is based on reverse engineered spec, I don't want
> to add it into GENERIC.  The missing of 5906 support in 2.0 release is
> mainly because that I goofily forgot to ask the user to try without
> ACPI :P

OK - Seems enough has changed or is already in-hand that I'll try HEAD 
before chasing this one any further in 2.0.X REL.

- did try w/o ACPI, BTW. Copious kvetching, but no real joy.

OTOH, there is no WiFi service where I am testing, so it was only the 
bge I cared about.

> I assume it is serializer assertion?  If not, please post the
> backtrace.  Thanks.
>

Pass.

Will do so if HEAD shows a problem in the same area. I should at least 
have off-box I/O in that one...

;-)

Bill