* Michael Smith <[EMAIL PROTECTED]> [020330 22:25] wrote:
> > Is there a way that we can "fix" this without blindly allowing bad
> > bus_alloc_resources ?  I'm a bit confused as to wheather our code is
> > behaving oddly or if it's just the device violating some spec...
> Yes, our code is busted; it should check both ranges and get the 
> arithmetic right.  I believe that Warner did something about this in 
> -current, but I'm not sure what or if it's backportable.

dude... duuuuuude... DUDE!

FreeBSD big.endian.org 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Sat Mar 30 13:52:36 PST 
2002     [EMAIL PROTECTED]:/usr/src/sys/i386/compile/smpng2  i386

(as of a couple of hours ago) heh.

If you have time and enough pity I'll take as much time as it takes
to get you the info to fix this.

> > > You should have bought a 3ware controller. 8)
> > 
> > 3ware should talk to Frys. :)
> 3ware don't feel like the bend-over-and-you-pay-for-the-crisco treatment, 
> I guess.

Yeah, they were a pretty nifty bunch of people when I saw them at BAFUG.

Anyhow, once the raid finishes building (in the background no less!)
I'll give it a whirl for perf testing, see how it stands, if the
driver continues to suck or perf does it's going to get one of Fry's
famous stickers. :)

-Alfred Perlstein [[EMAIL PROTECTED]]
'Instead of asking why a piece of software is using "1970s technology,"
 start asking why software is ignoring 30 years of accumulated wisdom.'
Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to