Thanks to Imre Vadasz, your Haswell, Atom SoCs, Skylake, and Kaby Lake CPUs will now recognize the ig4 device on the associated motherboard. I think it does something with ACPI? I have always been hazy on smbus device functions.
14 Replies to “ig4 support for newer CPUs on DragonFly”
Comments are closed.
Since the dragonfly man page is light on details, the OpenBSS man page provide more context
http://man.openbsd.org/ichiic.4
Give it to OpenBSD for having solid documentation.
what details? dflybsd is derived from freebsd and the freebsd page for ig4(4) is http://mdoc.su/f/ig4.4
More than light details would contain: DESCRIPTION
The ig4 driver provides access to peripherals attached to an I2C SMB controller. ig4 supports the SMBus controller found in fourth generation Intel(R) Core(TM) processors based on the mobile U-processor line for intelligent systems. This includes the i7-4650U, i5-4300U, i3-4010U, and 2980U.
Dfly didn’t add such a description because there are many 4th gen intel cpus, that use it, as justin mentions, Haswell, Atom SoCs, Skylake, and Kaby Lake beside the U-line.
But the part worth mentioned and it is mentioned in http://mdoc.su/d/ig4.4 because the users of dflybsd will have to actually use it if they have the hardware, is this phrase:
to load the driver as a module at boot time, place the following line in loader.conf(5):
ig4_load=”YES”
Obligatory reminder: this is open source. If there’s a man page that you would want to have more details, you can add it. Not that it’s really necessary in this case, but it bears repeating.
Justin
Someone can’t just copy and paste content from one bsd man page to another bsd.
You have to hold copyright to do that.
That would be not what I am suggesting.
Justin
Even if I don’t copy line by line the OpenBSD man page to update the DragonflyBSD man page … doesn’t the very fact that I *read* the OpenBSD man page constitute a derived work and not allowed since I don’t hold copyright.
Said another way, if I want to update a Dfly man page I need to do that in a black box type of way so that I don’t infringe on copyright of OpenBSD (or any other man page from another distro)
Copyright is on implementations, not concept. Using the word “orange” in a copyrighted text does not mean you own the word “orange”, for example.
This topic has been explored a lot in other places, so it would be better to go look online for answers from actual lawyers than here.
Doesn’t ISC/BSD license also cover documentation? I’ve read plenty of manpages that say XYZ first appeared in ABC.
Based on USA copyright law, Anonymous is correct (and Justin is wrong)
https://www.copyright.gov/circs/circ14.pdf
You can’t use a portion of anything written to create a new work. That’s derived and this copyright still applies.
Travis – I don’t think you understand my example. Copyright protects verbatim text. You can have copyright on instructions on how to swing an axe, for instance. However, that doesn’t mean nobody else can write axe-swinging instructions again – even if they have read your copyrighted text.
Reading a text does not poison you from ever making work on the same topic again, which is the original question from Anonymous.
Splitting hairs further, you can use written text to create new work – either with the permission of the original copyright holder – which is automatically granted with some forms of licensing, like Creative Commons – or if it has been released into the public domain by the original copyright owner or through expiration. That wasn’t the original question, though.
So why do people copyright their BSD licensed code?
I’m confused.
Copyright is an assertion of ownership. BSD licenses, GPL, Creative Commons, and so on, are structures to explain how the work can be used by others, without releasing ownership.
@Anon
sure you can copy it as long as you keep the copyright notice
https://github.com/openbsd/src/blob/5271000b44abe23907b73bbb3aa38ddf4a0bce08/share/man/man4/ichiic.4