seuros @seuros@mastodon.bsd.cafe
Public

Yesterday some news websites picked on ChaosBSD.
I did read the comments, and created a WIKI : github.com/seuros/ChaosBSD-src

I'm learning Driver building, that a sandbox of a full working system.

Some people raised the concern that FREEBSD -CURRENT should be the sandbox.

That not how operate.

For example, if i get a WIFI driver to scan 2.4gh, and dont have knowledge to do 5GH. That driver land. Someone else could add 5gh or WPA1/2/3 .

This ChaosBSD, the driver should at least do something useful.

I have Broadcom drivers that kernel panic if you stop the scan.

Other usb driver refuse reattach after a suspend mode.

These are the drivers that will not make it in mainline because Freebsd cannot tell it used : `BTW if you have BCM94321MC and close the lid, you lose wifi`

Also this is not a joke project. I'm trying to setup a work flow so we keep in sync with upstream.

Where FreeBSD drivers go to get beaten into shape before upstream. - seuros/ChaosBSD-src

Home

Where FreeBSD drivers go to get beaten into shape before upstream. - seuros/ChaosBSD-src

github.com · GitHub

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://mastodon.bsd.cafe/ap/users/115831158931920733/statuses/115921465132594191 on your instance and quote it. (Note that quoting is not supported in Mastodon.)