Haiku Beginner. Sound and Wifi Programs Support

[areeb]

This seems nice.
My driver files for FreeBSD are located here. Because my device is recognised as ath0.

@PulkoMandy

2. Import the sources in Haiku. They have slightly more readable name and are sorted by device type: network « drivers « kernel « add-ons « src - haiku - Haiku's main repository
3. Adjust jamfiles for your driver. If you updated an existing driver, make sure all sources are listed, if you added a new driver, you need to write a Jamfile for it, add it to the parent dir Jamfile, and write a “glue.c” to plug it to our network driver system.
4. Try to build your driver (“jam -q atheros” or whatever name it has). This will fail, because the FreeBSD code uses some functions we don’t implement yet (or if it works, you are lucky, no updates to the compatibility layer were actually needed)

Can you please elaborate a little more on how to adjust the jamfile and recompile the OS on Haiku ? what IDE will I need and the compiling process ?

[PulkoMandy]

For adjusting the jamfiles:

• You need to add your driver in the list at http://cgit.haiku-os.org/haiku/tree/src/add-ons/kernel/drivers/network/Jamfile
• You need a forwarding jamfile in the directory of your driver, something like this: http://cgit.haiku-os.org/haiku/tree/src/add-ons/kernel/drivers/network/atheros813x/Jamfile
• You need the FreeBSD sources + a “glue” file which you will have to write: http://cgit.haiku-os.org/haiku/tree/src/add-ons/kernel/drivers/network/atheros813x/dev/alc
• And a Jamfile to build it all: http://cgit.haiku-os.org/haiku/tree/src/add-ons/kernel/drivers/network/atheros813x/dev/alc/Jamfile

For compiling, see https://www.haiku-os.org/guides/building. No particular IDE required, only command line tools. (you can still use an IDE to edit the files, of course).

You only need to recompile your driver, not the complete system. You can do this with “jam -q atheros813x” for the example I used.

[areeb]

I tried the option of Ethernet too. But my Ethernet is Atheros AR817x and that is also unsupported.
Seems like I have to wait for the compatibility layer to be updated.