twa(4) update to support 9550SXU/9590SE controllers
mike at sentex.net
Wed Apr 11 22:03:10 UTC 2007
At 06:44 PM 10/11/2006, adam radford wrote:
>'vkashyap' is no longer maintaining the 3ware 'twa' driver.
>'twa' driver in RELENG_6 and CURRENT both support 9550SXU and
>9590SE controllers at this time. They both have the 0x1003 device ID.
>I will be sending an update in the near future to support the new series of
>9650SE controllers, remove bundled firmware (we have a FreeBSD specific
>userspace firmware update utility), and remove lots of non FreeBSD specific
We are just in the process of evaluating the new 9650se
cards, and RELENG_6 does not actually recognize them.
none1 at pci2:0:0: class=0x010400 card=0x100413c1 chip=0x100413c1
vendor = '3ware Inc.'
class = mass storage
subclass = RAID
cap 01 = powerspec 2 supports D0 D1 D2 D3 current D0
cap 05 = MSI supports 32 messages, 64 bit
cap 10 = PCI-Express 1 legacy endpoint
Are there still plans to integrate support for the newer generation
of cards into the FreeBSD src tree ? Using the driver off the
website, it seems to work OK but doing installs this way is bit of a pain
twa0: <3ware 9000 series Storage Controller> port 0x3000-0x30ff mem
0x88000000-0x89ffffff,0x8a200000-0x8a200fff irq 16 at device 0.0 on pci2
twa0: INFO: (0x15: 0x1300): Controller details:: Model 9650SE-2LP, 2
ports, Firmware FE9X 3.06.00.005, BIOS BE9X 3.06.00.002
da0 at twa0 bus 0 target 0 lun 0
da0: <AMCC 9650SE-2LP DISK 3.06> Fixed Direct Access SCSI-5 device
da0: 100.000MB/s transfers
da0: 76283MB (156227584 512 byte sectors: 255H 63S/T 9724C)
>On 10/11/06, freebsd at bitfreak.org <freebsd at bitfreak.org> wrote:
>>I just noticed that, based on the commit logs, the twa(4) driver is
>>still the driver from the 22.214.171.124 release from 3ware. That version
>>doesn't support the new 9550SXU and 9590SE controllers, the later being
>>3ware's new PCI Express card. Is anyone currently planning/testing an
>>update to the 126.96.36.199 release? I tried emailing the only address listed
>>(vkashyap) in the logs and source, but it bounced. So I'm not sure who
>>contact. Should this wait until after the 6.2 release?
>>freebsd-current at freebsd.org mailing list
>>To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>freebsd-current at freebsd.org mailing list
>To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
More information about the freebsd-current