Re: pci powerstate related: aac(4) broken on Perc 3/Di on -CURRENT
From: Wilkinson, Alex (alex.wilkinson_at_dsto.defence.gov.au)
Date: 01/10/05
- Previous message: Ketrien I. Saihr-Kenchedra: "Re: do YOU have one of these USB devices?"
- In reply to: Scott Long: "Re: pci powerstate related: aac(4) broken on Perc 3/Di on -CURRENT"
- Next in thread: Scott Long: "Re: pci powerstate related: aac(4) broken on Perc 3/Di on -CURRENT"
- Reply: Scott Long: "Re: pci powerstate related: aac(4) broken on Perc 3/Di on -CURRENT"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 10 Jan 2005 12:30:15 +1030 To: freebsd-current@freebsd.org
0n Thu, Jan 06, 2005 at 03:58:39PM -0700, Scott Long wrote:
>It should be noted that WinXP tried to get fancy in a similar way with
>automatic powerdown of devices, and broke these PERC devices in a
>similar way. Due to restrictions of the MS driver framework, the only
>solution that Adaptec could use was to modify the firmware to make the
>bridge be opaque. This solved the issue of the OS seeing devices that
>belong to the firmware, but made it impossible to run the controller in
>split-channel mode, where one channel is for RAID and the other channel
>is pure SCSI.
Scott, what is meant by "...to make the bridge be opaque." ?
- aW
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: Ketrien I. Saihr-Kenchedra: "Re: do YOU have one of these USB devices?"
- In reply to: Scott Long: "Re: pci powerstate related: aac(4) broken on Perc 3/Di on -CURRENT"
- Next in thread: Scott Long: "Re: pci powerstate related: aac(4) broken on Perc 3/Di on -CURRENT"
- Reply: Scott Long: "Re: pci powerstate related: aac(4) broken on Perc 3/Di on -CURRENT"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|