- User Since
- May 11 2014, 1:02 PM (350 w, 2 d)
Dec 16 2020
Dec 12 2020
A few last minor tweaks to the test program.
Nov 30 2020
This update adds the option to choose between detailed (the default) and summary reporting, and removes the restriction that only one pin-change event can occur between each call to read(2) without losing data. It also adds a new test/demo program, based on the test code written by Christian for the gsoc project.
Nov 28 2020
Nov 27 2020
Allow only edge-triggered interrupts, and only if they are supported on that pin according to the capabilities flags from the hardware driver.
Primarily style fixes, mostly reformating block comments to the freebsd standard.
Locking fixes. The original code had several places where an error-handling path would exit a function with a mutex unlocked that would be re-locked on a normal exit. There was also a place where an SLIST was traversed without holding the mutex that protects additions and deletions on that list.
Just a note to mention that the initial diff is the exact code from https://github.com/ckraemer/freebsd/tree/gsoc2018, with a couple small tweaks to resolve conflicts due to the freebsd base code having changed a bit over the past two years.
Nov 26 2020
Nov 25 2020
Nov 18 2020
Nov 15 2020
Oct 12 2020
Sep 22 2020
Sep 14 2020
Applied patch to freebsd 8 (which we use at $work but it has the icee.c source from -current) and freebsd 11 and it behaves as expected on our products.
Sep 3 2020
Sep 2 2020
So, what prevents "kldunload icee" while someone has the cdev open?
Sep 1 2020
Jul 26 2020
Jul 19 2020
Jun 18 2020
The argument that we have around a hundred places where the rule is already broken in fact confirms that most of our code confirms to the style(9) in this regard, since hundred places for several MLoCs of our own code is quite good ratio.
Apr 2 2020
Mar 29 2020
Mar 6 2020
Feb 29 2020
Feb 10 2020
Feb 1 2020
I believe 0750 is an ideal mode for the /root dir; it adds some security, and it seems unlikely that existing scripts or other automation people have in use will fail due to the change.
Jan 17 2020
Jan 16 2020
After some discussion on irc we realized we don't need a get-capabilities interface between gpio and pinctrl, because both are soc-specific drivers, and the gpio driver already "knows" what capabilities the soc has.
Jan 15 2020
Jan 14 2020
What kind of flags go into the flags arg? I suspect the quick answer is GPIO flags. The more complete answer is probably "some subset of gpio flags which differs from one device to another". That leads to the question of what to do on an attempt to set multiple flags where some are supported and some aren't.
Jan 9 2020
When replacing objdump with llvm-objdump came up on a mailing list, there was some opinion expressed that most users don't need objdump at all and should have to install a package to get it. But I find llvm-objdump to be a completely-usable replacement for gnu objdump that we've had in base for years. That leads me to think a knob such as WITH[OUT]_LLVM_OBJDUMP that defaults to WITHOUT might be a good solution for this.
Jan 8 2020
Jan 7 2020
Jan 2 2020
Committed (forgot to link to phab) as r356278.
Jan 1 2020
Remove the bus_select callback pointer and instead create an iicmux_if.m to define a bus_select method.
Dec 31 2019
Dec 30 2019
Dec 29 2019
Committed as r356180
Dec 26 2019
Doh! I totally missed that, thanks.
Uploaded a new diff with proper context.
Dec 25 2019
Add arm64; the changes needed are almost identical to armv6/7.
Just an update to note that the commit for this was reverted in r356078 due to CI build failures. I'm unable to install a working riscv toolchain for building and testing myself, apparently at least in part because I'm still running 12.0-stable (and if I try to upgrade from that my video card turns into a pumpkin).
Since we don't generate ldscript files anymore, remove the generated files from the CLEAN+= list.
Dec 24 2019
Does anyone know why riscv needs writable text segments? Or if it really does?