James Carlson wrote:
> Caua Siqueira Carulli - Sun Microsystems writes:
>
>> Sep 5 10:47:11 yasmin genunix: [ID 903071 kern.notice] ath:
>> ath_attach(): unable to attach hw: 'Hardware didn't respond as expected'
>> (HAL status 3)
>>
>
> That means that the Atheros proprietary (binary only) HAL layer is
> returning an error. There's not much we can debug past that point.
> It either doesn't support this device, or the device itself is
> damaged. (If this same device works with other OSes, then that likely
> means the HAL layer we have in our driver is out of date.)
>
> Unless the folks who maintain the driver can get you a new HAL, I
> think you're out of luck. (One of those folks was in this discussion
> at some point, but with all of the top-posting and context loss, I'm
> no longer sure who that is.)
>
>
New HALs can usually be extracted from the FreeBSD tree ... Sam Leffler
historically maintains the Atheros driver and HAL layer, and it used to
be the case that FreeBSD was his first port of choice.
Sometimes the HAL update requires other driver changes as well -- the
HAL and the driver are fairly tightly bound at the interface layer,
although the interfaces themselves are versioned. Any saavy kernel
engineer could probably figure out how to update the HAL.... I've done
it once or twice myself. (Actually, I helped Sam debug an update to
his HAL code for an embedded NetBSD port a while back.)
-- Garrett
_______________________________________________
networking-discuss mailing list
[email protected]
