This looks a bit like SEO spam. All of the articles barely have any content and are only accessible via key words.
1,568 karma · joined January 3, 2013
Btw - already EDO DRAM favours reading entire memory blocks/lines. My suspicion is that the trick in increausing memory bandwidth is not only based on interleaving, but also on block transfers with on-chip caching. Especially critical for texture reads.
The Voodoo is a nice example of how much execution matters. They were not the only ones to follow this path back then, but by only concentrating on the core functionality they managed to beat all others to the market without compromise. (Compare to S3 Virge, Matrox Mystique, Nvidia NV1, Tseng, NEC and many others)
This is called "jamming" and was a real problem for early radar solutions.
Curiously you well rarely see anyone mention this in the LIDAR space. For many of startups adressing this issue seems to be an afterthough.
One proper way to solve this is to use orthogonal codes in the scanning scheme. There are different ways to implement this. The complexity depends a lot on the used LIDAR architecture. It would not be surprising to see some of the startup being weeded out by that during real-world tests.
Unfortunately there are no standards (yet) to benchmark different LIDAR solutions, but most of their competitors stick to more realistic assumptions.
Then, in general, the website is light of any tangible information:
- Company information: Management, History, Size, Investments, strategic partners, location of company
- Concrete working principle of their LIDAR: Detector principle, wavelengths, laser type used, means of scanning, optical aperture
- Images of actual hardware
- Does their price-tag still apply after they have managed to implement proper functional safety processes and measures?
Very weak, especially considering how much competition is out there. There seems to be a new LIDAR start up every other weak.
A 100% seconded. Check out their new line of ATtiny devices. They start at 0.30USD/pc, but come with every peripheral one could imagine.
Most lower end Cortexes only come with bare bone peripherals and are encumbered with poor glue logic like multi cycle GPIO access or flash waitstates.
That's an interesting thought. But where would this lead us?
https://www.youtube.com/watch?v=u4ZoJKF_VuA
Is the book worth reading, in addition? I see very mixed reviews.
- Each pixel represents one bit.
- Hence, we should try to increase information entropy.
That's all there is to it? Certainly not, since we are creating something for human consumption. There are a couple of other factors:
- The way the eye processes patterns: lateral inhibition [1]
- The way the eye processes colours: photopic vision [2]
- The way the brain interprets patterns
- The way the brain can actually interpret ingoing information.
I don't have an answer to all of these. But is pretty certain that maximizing entropy of a binary pattern is not equivalent to optimiziung reading speed.
The Eda industry is ripe for disruption, and it seems the incumbent Chinese semi players may become the catalyst. See also, how they embraced RISC-V.
http://www.tcl.fr/var/tcl/storage/original/application/b8cb6...
It surely looks to me as if they are using patents in their originally intended way. The downside is that they are hitting vendors with a C&D instead of going to the source. But that could rooted in the difficulties surrounding the ability of a taiwanese company to sue a china mainland one...
But for everything else, like IoT, Sensors, Power, you can find plenty of companies and subsidiaries in Germany: Infineon, Bosch, GlobalFoundries, NXP, Dialog, Elmos, Melexis, Xfab, AMS, IDT (ZMDi), TI, Intel, TDK (Micronas) and many smaller ones.
Note that there are many instructions that simply don't map to high level language features, such as bit rotation (not shift!), BCD mode and indirectly indexed adressing.
One thing that it very popular in highly optimized 6502 assembler code is self-manipulating code or even run-time generated code. This allows to work around a lot of limitations with indexed adressing or parameter loading.
The 6502 was designed at a time when CPUs were not limited by memory speed. I imagine that has only been the case right after the emergence of the first MOS-Memory (Intel, late 60ies)
Edit: For those interested in state of the art optimized 6502 arithmetic, this is a very good source:
"Spinoff" by Charlie Sporck - early Silicon Valley history on Semi companies
"Commodore - a company on the edge" by Brian Bagnall
"Only the paranoid survive" by Andy Grove - Intels switch to Microprocessors. (Interestingly you can see in the book that he realized the power of the internet, but failed to act on it to some extend)
News article from the US (Texas): https://www.texasmonthly.com/the-culture/dr-pepper-keurig/ "The Yanks Have Bought Dr Pepper"
News article from Germany: http://www.handelsblatt.com/unternehmen/handel-konsumgueter/... "German billionaire family Reimann buys Dr. Pepper"
I guess both are true, since Keurig is still a US run company, although its majority is owned by JAB holding.
Are you serious? Groceries in the US are surprisingly expensive compared to Europe.
Senior technical expert and management positions are usually paid above tariff, starting at around 100k€.
There are plenty of positions in the big tech companies and software that are paid above 100k€. It's just very unlikely to get there if you are straight from school. Also, you won't have much luck finding >100k€ positions in the eastern part of Germany.
A general issue I see, however, is that the real world need for flexible displays is far more limited than earlier projections suggested. If you switch to a rigid display, there is no reason to use an organic transistor back plane - that's where things start to unravel. PL were not even the first company in that space. There also were Polymervision and a couple of others.
Basically the entire organic transistor community has a solution in search of a problem. Not really an issue limited to Plastic Logic.