On Mon, Nov 19, 2007 at 03:32:15PM -0600, jakllsch@kollasch.net wrote:
> On Mon, Nov 19, 2007 at 10:05:49AM +0100, Quentin Garnier wrote:
> > As for the Ethernet device, I now have a working driver.  It's not
> > complete yet and needs some clean up, but the real trouble is that the
> > only documentation I had was a Linux GPL driver.  I'll try to reach
> > Atheros about it, but in the meantime I won't publish it.
> 
> You should compare to src/sys/arch/mips/atheros/dev/if_ae.c.

Oh it's a different chip.  I started there.

I don't think it will be a problem in the end anyway.

> Also, if you do release what you have, I'd suggest a shorter name.
> 'atltwo' is as long as the 'xennet' I keep being annoyed with.

I've switched to atlii already, which is slightly shorter.

lii maybe?  I like the "ii" thing considering it's for the Eee :)

> > David Young told me that an update of net80211 and ath(4) from FreeBSD
> > should allow the wireless device to be used.  If anyone wishes to work
> > on it, please be my guest.  I will probably have a try at it, but I was
> > lucky enough to have this week-end almost completely free, that might
> > not reproduce before long.
> 
> I have a AR5006EG working with a simple replacement of the HAL
> package (hw.ath.hal.version = 0.9.18.0). Sticker on the case
> says AR5BXB61. (Toshiba A135-S4527.)
> 
> I don't know if vendor/product/rev means anything for these chips,
> but mine's 0x168c 0x001c 0x01.

I'll try.

-- 
Quentin Garnier.