[kismac] Re: Atheros 5424 status
hm, I don't know a great deal about programming or coding drivers, but since os x and linux are both unix-based systems, it would just be a matter of porting it to a darwin kernel instead of a linux kernel.
Anyways, like Luke said, it looks like there is a lot of demand for this driver, so hopefully it will arrive soon enough. 

-David


From: "Michael Miller" <1337mail@xxxxxxxxx>
Reply-To: kismac@xxxxxxxxxxxxx
To: kismac@xxxxxxxxxxxxx
Subject: [kismac] Re: Atheros 5424 status
Date: Mon, 15 Jan 2007 13:39:58 -0500

How much work is it to port a linux driver to OSX? I know the
architectures are radically different, but is it easy to write a
driver once the specifications are reverse engineered?

Mike

On 1/15/07, Luke Turner <luketurner@xxxxxxxxx> wrote:

I'm almost positive the linux driver guys are working on it, but slowly...

Considering how much of a demand there is currently (you'd be surprised),
it's only a matter of time...

Curious to see if the "n" features will be addressed as well.


On 1/15/07, Michael Miller <1337mail@xxxxxxxxx> wrote:
> Yes, this is correct. The chipset featured in the Core 2 Duo Macbook
> Pros is the Atheros AR5008. Unfortunately no OSS driver exists for it,
> and this is where the problem lies. Basically, the only way to get
> passive wireless fully working with injection is to write a driver
> from scratch. I don't know if anyone has undertaken this project as of
> now, but it would be really cool if someone has.
>
> Mike
>
> On 1/15/07, Luke Turner <luketurner@xxxxxxxxx > wrote:
> > I'm pretty sure any intel mac with the core2duo refresh has the atheros, 
am
> > I mistaken?
> >
> >
> > On 1/14/07, Daniel <dbr42@xxxxxxx > wrote:
> > >
> > > Le 12 janv. 07 à 21:04, David Kitts a écrit :
> > >
> > > >
> > > > Is this just a problem with macbooks, or all intel based airport
> > > > extreme's? I can't seem to get the one on my iMac purchased just
> > > > last  month to work, even after trying all steps in the wki.
> > >
> > > I think iMac have Broadcom based airport (ioreg -l to check it),
> > > while macbook (at least recents) have Atheros based airport.
> > >
> > > I finaly managed to make it work - I had (have to check if it is the 
> > > only thing) to launch a tcpdump after starting capture :
> > > the tcpdump turns en1 into promisc mode, which was missing
> > >
> > >
> > > >> I actually understand this is exactly ticket #191(New MacBook
> > > >> capturing Packets but no Data), where it is said
> > > >> "Known issue. Not caused by anything we can help with a few lines 
> > > >> of  code, but we're working on it."
> > > >>
> > > >> anyway to help ?
> > > >>
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
>
>

Other related posts: