Contribute
Register

FakePCllD an AR9271 to get recognized as an AR9380/AR9280?

Status
Not open for further replies.
Joined
Aug 7, 2013
Messages
3
Mac
  1. 0
Classic Mac
  1. 0
Mobile Phone
  1. 0
the readme of the ath9k-htc git hub page (linux kext for this chipset) says that the AR9271 is an OFFSHOOT of the AR9825. As we know we can inject the AirPortAtheros40.kext to get an AR9285 recognized as an AR9380/AR9280 for OS X driver support, so would this eventually be possible with the AR9271 too?

Maybe this is a good opportunity to solve the whole AR9271 questions since there are many people who looking forward to an kext support for this chipset.



resources
https://github.com/qca/open-ath9k-htc-firmware
http://www.tonymacx86.com/network/104850-guide-airport-pcie-half-mini-v2.html
 
the readme of the ath9k-htc git hub page (linux kext for this chipset) says that the AR9271 is an OFFSHOOT of the AR9825. As we know we can inject the AirPortAtheros40.kext to get an AR9285 recognized as an AR9380/AR9280 for OS X driver support, so would this eventually be possible with the AR9271 too?

Maybe this is a good opportunity to solve the whole AR9271 questions since there are many people who looking forward to an kext support for this chipset.



resources
https://github.com/qca/open-ath9k-htc-firmware
http://www.tonymacx86.com/network/104850-guide-airport-pcie-half-mini-v2.html

You could try it and see what happens...
 
its for me somehow the first time learning about kext, I am a little bit lost around here but I will try my best.

But does PCI ID Injection mean that it only interacts with PCI Interfaces? Or asking it in another way; Is it possible to FakeID an AR9271 USB Wireless Device with this method? Maybe changing IOProviderClass to IOUSBDevice in the plist file?



I read your guideline on your FakePCIID repository, this is so far what I understand:

- read out IO RegistryProperties from the AR9271 Device: how, on a windows machine ?
(Wiki is also providing vendor and device id)

  • vendor-id
  • device-id
  • subsystem-vendor-id
  • subsystem-id

- define FakeProperties in plist using RM Prefix with those Values ?

- define the class we want to fake at IONameMatch, in this case for AR9380/AR9280 (168c:002a or 168c:0030) ?

- generating a kext out of the plist and install it plus FakePCIID.kext ?





resources for people to follow up

https://github.com/RehabMan/OS-X-Fake-PCI-ID

https://developer.apple.com/library...f.html#//apple_ref/doc/uid/TP0000021-BABCCBIJ

https://wikidevi.com/wiki/Atheros_AR9271


p.s. in my case it would be the TP-LINK TL-WN722N
The Wiki is giving Vendor ID 0cf3 Device ID 9271
 
its for me somehow the first time learning about kext, I am a little bit lost around here but I will try my best.

But does PCI ID Injection mean that it only interacts with PCI Interfaces? Or asking it in another way; Is it possible to FakeID an AR9271 USB Wireless Device with this method? Maybe changing IOProviderClass to IOUSBDevice in the plist file?

FakePCIID is only for PCI devices.

If your device is USB, there is no chance of getting it to work with the native drivers.
 
Status
Not open for further replies.
Back
Top