This is the next logical step for semiconductor companies like AD, TI, etc.
AD doesn't tend to compete on cost, so high quality open source drivers become a key differentiator compared to other companies with lower cost parts, especially as these parts become increasingly complex. A 9 axis IMU with 10 different acquisition and buffering modes, built in algorithms, etc. becomes a lot more tractable if you don't have to write the whole driver from a datasheet.
This looks just like some list of existing drivers, regardless of who wrote them.
It was done this way to try to make it easier for people to find the drivers, rather than rolling through kernel source. The Majority of the drivers are upstream (including the ones ADI writes), or are in process of going upstream, but some drivers - because of their development flow - will never meet upstream kernel coding guidelines.
[Disclaimer - I work at ADI].
Now if Broadcom starts to be opensource friendly then that would be a real change of heart.
The core SOC is a TI chip, but at least at the time while TI wasn't abhorrent, anything that might remotely help get the USB port working was a proprietary blob. I think they'd also sold the IP for that product to someone else by the time I was tinkering with it; I can't remember exactly but do recall it was either a nightmare or impossible to get a copy of the source code for the factory firmware.
This has turned me off to anything even using TI chips that I'm aware of. Maybe they've gotten better in the last decade. Probably they're fine if you're a hardware manufacturer paying for chips.
That's a pretty dated view of ADI's business.
These days they make most of their cheddar in their high speed data converter business. They have GSPS ADCs and DACs available that are hundreds of dollars per chip.
The Kuiper Linux support for Xilinx Zynq and MPSoC is telling. That's coded language for 5G physical layer and electronic warfare/SIGINT uses.
It also forms a big part of their business to sell associated components that complement the converters: clock sources, PLLs, some discrete RF, etc.
You missed the Intel SoC and Raspberry Pi support too. :)
According to the Annual Report [1] - ADI works with 125,000+ customers. That means diversity in application. The press release was focused on Linux, but there are a lot of other ecosystems that ADI also participates in - from Arduino to Pmod to No-OS to Mbed and more.
https://www.analog.com/media/en/news-marketing-collateral/so...
[Disclaimer - I work at ADI]
[1] https://investor.analog.com/static-files/ddc81d14-3ffe-4655-...
We are making a Pi HAT based on https://www.analog.com/ad9166 (no JESD204, NCO only) to demonstrate how to make a fast hopping CW ...
There are lots of things that Pi is a great answer for.
Devices with ARM A5 (like https://www.analog.com/adsp-sc589) are still supported.
Disclaimer - I work at ADI.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...
static bool ltc4306_is_volatile_reg(struct device *dev, unsigned int reg)
{
return (reg == LTC_REG_CONFIG) ? true : false;
}
Oh man, c'mon. That kind of thing bugs me. Just "return reg == LTC_REG_CONFIG" already, sheesh. (And maybe make it a preprocessor directive while you're at it?) void foo(bool bar)
{
}
int main(void)
{
foo("Whose bright idea was this?");
}
No error, not even a warning, perfectly legit code. If bar had been declared int or char, you'd get an error. Instead, your code ends up less safe because you used bool, thinking you were doing the right thing. Yes, they wanted to allow it anywhere a conditional expression would fit, but implicit conversion from anything other than int and char would have been a good place to draw the line.So I wouldn't be surprised if the GP example was prompted by a similar design flaw in either the language or a particular compiler.
> The == (equal to) and != (not equal to) operators are analogous to the relational operators except for their lower precedence. Each of the operators yields 1 if the specified relation is true and 0 if it is false. The result has type int. For any pair of operands, exactly one of the relations is true.
https://port70.net/~nsz/c/c11/n1570.html#6.5.9p3
Thanks for clearing that up. (Although I feel a bit foolish now.)
That ternary operator "?" is just an if-statement which should have the same "problem" with an int argument. It is a broken compiler that would complain about an if statement but an identical ?-statement.
If the int nature of equals-to was a problem, you'd have to use limit its use to switch statements.
The strict requirement in the standard is just a 'scalar type': every conditional expression in C, even `if (true)`, technically evaluates on unequal comparison to zero. See section 6.8.4.1 "The if statement" of the standard:
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2310.pdf
This applies to ternary operators, if statements, do/while loops, for loop termination conditions, etc.
However, when defining a function that returns boolean, you've asked the compiler to make your program more strict than just returning an integer that's zero or nonzero, you're not allowed to return anything but 'true' or 'false' - no, you're not allowed to pack in error codes after the fact!
There is nothing to understand. Sorry for being a bit dense.
Then there's living in C++ land, which is 1000 times worse.
Because giving away the source code to their simulator doesn't make any business sense in the way giving a Linux kernel driver does.
Giving away LTSPICE is an effort to commoditize their complements. The complement to an opamp is a high quality simulation model. The complement to a high speed data converter is a working Linux driver for JESD204B. Both decrease the effort involved for ADI's customer to use ADI's parts.
Giving away LTSpice source code doesn't achieve a similar aim.
Also, unless something has changed, ltspice is wholly written by one person.
The link above is a press release, the full list of devices is here:
https://wiki.analog.com/resources/tools-software/linux-drive...
Part numbers prefixed with "LTC" are from Linear Tech, part numbers prefixed with "MAX" are Maxim, part numbers prefixed with "AD" are Analog Devices. Part numbers prefixed with "DS" are from Dallas Semiconductor, which was bought by Maxim a long time ago.
As someone who typically uses these devices in much smaller embedded systems, it's nice to have these hardware abstraction layers listed in one place, instead of having to transcribe it from the datasheet.