Which BSD base with better Hardware Detection?

[mbzadegan]

Originally Posted by jggimi

If you don't know which OS supports that particular hardware, you must test them.

Yes, Ofcourse, I must test it and I'm in this state.
But If you will be in this state, You will be select which of the BSDs at first selection?

[jggimi]

Start with your preferred OS. If none of the BSDs support the device, consider other operating systems.

[mbzadegan]

Originally Posted by jggimi

• Recognition of vendor/device codes transmitted by a device in response to probe actions by the OS.
• Development, testing, and deployment of an operational device driver.

For the Recognition phase by OS I did not get a usefull answer yet.
And for the phase of Driver Development, What Is the usefull book to develop device drivers manually by myself?
For Example I want to develop my Notebook (ASUS S200E) NIC ethernet driver on the OpenBSD, How can I start step by step?

[sacerdos_daemonis]

Originally Posted by mbzadegan
For the Recognition phase by OS I did not get a usefull answer yet.

Yes, you have been given useful answers, but they are not the answers you want.

Originally Posted by ibara
These devices are not yet supported in OpenBSD. You would have to write drivers for them.

Originally Posted by LeFrettchen
Even Windows has a really bad driver for this LAN adapter...

The knowledgeable people on the board have informed you that your particular piece of hardware has little to no support on BSDs. And they also offered two solutions.

Originally Posted by ibara
Alternatively, purchase a supported USB Ethernet and/or USB WiFi module.

Originally Posted by jggimi
If you require the use of a particular hardware component at a particular point in time, you must choose an OS which can exploit that hardware at that point in time. Whether that OS is one of the BSDs or not.

Complaining that you do not like the answers will not change reality.

Originally Posted by mbzadegan
What Is the usefull book to develop device drivers manually by myself?

If you can do it that is great, both for you and other people who have that hardware, but I think ibrara's suggestion would be easier. (Unless your NoteBook does not have USB ports.)

[mbzadegan]

Thanks sacerdos_daemonis but I'm going to start BSD unknown network driver programming, in other words I want to eat that frog!

[ocicat]

Originally Posted by mbzadegan

What Is the usefull book to develop device drivers manually by myself?

The following title is very old, but it has been mentioned on a few lists as being helpful:

http://www.amazon.com/Writing-UNIX-D...device+drivers

...but the best answer is to download the source code of whatever operating system you choose, and study the source code of similar network drivers.

[sacerdos_daemonis]

Originally Posted by mbzadegan

... in other words I want to eat that frog!

Good luck and I hope you have both joy and success.

[mbzadegan]

I found my NIC add-in module to load ethernet card on FreeBSD.
Is that possible to port other UNIX Drivers (Such as FreeBSD or Linux) to OpenBSD?

[jggimi]

Here is a conversation on the OpenBSD misc@ mailing list discussing this specific issue, with this specific hardware.

Please read the posts from Stefan Sperling, an OpenBSD developer who previously attempted this exact task.

I perceive you have five choices. The first four require neither OS driver development skills nor engineering documentation from the hardware manufacturer.

1. Use FreeBSD.
2. Use Linux.
3. Use Windows.
4. Use other hardware.
5. Develop a driver for your preferred BSD.

[LeFrettchen]

Originally Posted by mbzadegan

Thanks sacerdos_daemonis but I'm going to start BSD unknown network driver programming

Originally Posted by jggimi

Here is a conversation on the OpenBSD misc@ mailing list discussing this specific issue, with this specific hardware.

Please read the posts from Stefan Sperling, an OpenBSD developer who previously attempted this exact task.

Yep, Stefan's result was predictable : with no access to the manufacturer's source code, hard to create any driver, this is a blind and aleatory dev...

Sounds like a full time job !

Originally Posted by sacerdos_daemonis

Good luck and I hope you have both joy and success.

Good luck and I hope you've got enough time for that.

[jggimi]

Originally Posted by LeFrettchen

...with no access to the manufacturer's source code...

I believe you meant hardware interface specifications.

Specifications are normally required to implement a driver. Some manufacturers release this information publicly. Some manufacturers hold specifications as trade secret, devising their own drivers for their markets. Some manufacturers are willing to provide access to specifications only under non-disclosure agreements ("NDAs"). NDAs executed with members of open source projects will include terms and conditions that either permit or disallow open source drivers to be developed.

Without interface specifications from hardware manufacturers, integration of device hardware can take place, but as we can see from the short discussion I referred to above, driver design becomes much more difficult. If there are open source drivers already available, they can be reviewed for adaptability to the OS. Often, reverse engineering must be performed. Mr. Sperling reviewed FreeBSD and Linux drivers, and conducted some reverse engineering, but was not successful integrating this particular chipset into an existing driver.

[LeFrettchen]

Originally Posted by jggimi

I believe you meant hardware interface specifications.

Yes, but you understood what I meant...

Originally Posted by jggimi

Often, reverse engineering must be performed.

This, I won't be able to do, I'm not so skilled.
So, for me, it would be a blind and hazardous dev

Thanks jggimi for clarifying my comments

[mbzadegan]

Unfortunately There is no any update instruction or first step tutorial about OpenBSD unknown hardware programming yet.
Is that possible to translate hardware windows drivers (*.inf, ...) to work and execute in BSD? (such as OpenBSD)

[ocicat]

Originally Posted by mbzadegan

Is that possible to translate hardware windows drivers (*.inf, ...) to work and execute in BSD? (such as OpenBSD)

No.

[aht0]

Originally Posted by LeFrettchen

Well, poorly supported, for sure !
Even Windows has a really bad driver for this LAN adapter...

The best thing to do is to forget this crap, and find an alternative solution.

Im using AR9485 in hostap mode without problems. pfSense 2.3.1 (based on FreeBSD 10.3-RELEASE). Seems that FreeBSD had it's wlan drivers updated meanwhile.

It's definitely not supported in OpenBSD at all (tried few weeks a go)

[jggimi]

FreeBSD's driver is a copyrighted contribution from Qualcomm Atheros, Inc.

The license to use the source code is generally open, but adaptation to OpenBSD was not previously successful, and the last patch addressing the AR9485 I have seen in commit logs occurred in 2013.

My recommended choices in post 29 above remain unchanged.