<puddingpimp>
could also squat a USBID of a company you know to be out of business
<puddingpimp>
*VID
<puddingpimp>
the problem with assuming you can use something because it's in silicon you bought is, that's not always the case
<puddingpimp>
for HDMI, in particular, and with a lot of connectors in general, but not for USB AFAIK, the connector does not include a patent license
<puddingpimp>
neither does the silicon
<puddingpimp>
HDMI is the opposite of USB, you have to pay a $5 license fee for every HDMI device if you DON'T put the HDMI logo on your product and packaging
<puddingpimp>
*unit shipped
<puddingpimp>
and buying an AD9713 or similar and a reputable brand HDMI connector does not exempt you from separately complying with the HDMI patent licenses
<puddingpimp>
similarly, I know of companies being sued for implementing CAN bus by using the CAN bus functionality included in their microcontroller
<puddingpimp>
the issue can sometimes be that the silicon on it's own does not constitute an infringing article, for example it may only include the drivers and SERDES required, but leave it up to software to implement some patented handshake or so on
<puddingpimp>
or in other cases, that the licensing authority only issues licenses for enduser devices or subsystems and has other grants or licensing terms in place for component manufacturers
waylon531 has quit [Ping timeout: 250 seconds]
<puddingpimp>
but always pays to consult an actual lawyer before or after you get sued (as your policy may be)
waylon531 has joined #yosys
waylon531 has quit [Ping timeout: 248 seconds]
waylon531 has joined #yosys
waylon531 has quit [Ping timeout: 248 seconds]
waylon531 has joined #yosys
ZipCPU|Laptop has quit [Ping timeout: 255 seconds]
digshadow has quit [Ping timeout: 252 seconds]
digshadow has joined #yosys
seldridge has quit [Ping timeout: 260 seconds]
seldridge has joined #yosys
seldridge has quit [Ping timeout: 255 seconds]
digshadow1 has joined #yosys
aw- has joined #yosys
digshadow has quit [Ping timeout: 255 seconds]
pie_ has quit [Ping timeout: 240 seconds]
pie_ has joined #yosys
mbuf has joined #yosys
aw-1 has joined #yosys
aw- has quit [Ping timeout: 268 seconds]
aw-1 is now known as aw-
dys has joined #yosys
cr1901_modern has quit [Read error: Connection reset by peer]
proteus-guy has joined #yosys
nrossi has joined #yosys
pie_ has quit [Read error: Connection reset by peer]
AlexDaniel has quit [Ping timeout: 240 seconds]
pie_ has joined #yosys
m_t has joined #yosys
cr1901_modern has joined #yosys
aw- has quit [Quit: Leaving.]
pie_ has quit [Ping timeout: 240 seconds]
AlexDaniel has joined #yosys
AlexDaniel has quit [Ping timeout: 255 seconds]
aw- has joined #yosys
aw- has quit [Quit: Leaving.]
mbuf has quit [Quit: Leaving]
seldridge has joined #yosys
pie_ has joined #yosys
cr1901_modern has quit [Ping timeout: 248 seconds]
cr1901_modern has joined #yosys
seldridge has quit [Ping timeout: 250 seconds]
mbuf has joined #yosys
FabM has quit [Quit: ChatZilla 0.9.93 [Firefox 52.3.0/20170811091919]]
dys has quit [Ping timeout: 250 seconds]
mbuf has quit [Quit: Leaving]
digshadow1 has quit [Ping timeout: 248 seconds]
eduardo has joined #yosys
dys has joined #yosys
digshadow has joined #yosys
ravenexp has quit [Ping timeout: 240 seconds]
ravenexp has joined #yosys
nrossi has quit [Quit: Connection closed for inactivity]
AlexDaniel has joined #yosys
marbler has quit [Ping timeout: 276 seconds]
marbler has joined #yosys
m_t has quit [Quit: Leaving]
sklv has quit [Remote host closed the connection]
sklv has joined #yosys
<cr1901_modern>
ZipCPU: What happens if ZipCPU faults in the interrupt handler, considering there are no nested exceptions. Is all existence denied?
<ZipCPU>
:D
<ZipCPU>
"all existence denied?"
<ZipCPU>
Yes, the ZipCPU can fault in the interrupt state. What happens next is configurable.
<cr1901_modern>
i.e. unstoppable force vs immovable object
<cr1901_modern>
you interrupted something which could not be interrupted
<ZipCPU>
The ZipCPU can either be made to wait for a debugger to come and rescue it (takes a bunch of logic, hard to do on small architectures ...)
<ZipCPU>
Or the CPU can be configured to reset itself. A clever reset routine will give you the error codes you then need to debug it.
<cr1901_modern>
Ahhh I like that idea
<cr1901_modern>
I'm reading about ancient ARM tonight. It reminds me of ZipCPU a bit (26-bit ARM). It recommends something similar on reset vector
<shapr>
twenty six?!
<cr1901_modern>
26-bit program counter*
<cr1901_modern>
the rest of the arch is 32-bits
<shapr>
I knew there were 36 bit CPUs
<shapr>
and I don't even know what to call the russian trinary systems
<cr1901_modern>
the upper 6 bits hide the status bits
<ZipCPU>
The ZipCPU actually has a variable length program counter (variable at configuration time)
<ZipCPU>
That way you can size it to the size of the exterior bus.
<shapr>
coworker introduced me to industrialalchemy.org and several hours vanished
<rqou>
navre avr also has a variable length PC
<rqou>
it's not _that_ unusual
digshadow has quit [Ping timeout: 255 seconds]
<cr1901_modern>
Time for 26-bit ZipCPU?
<ZipCPU>
If you've only got 26-bits (64MB) of info on your bus? Sure!
<cr1901_modern>
I started reading about ancient ARM due to AMBER CPU core. It is an open core of ARMv2, which is not patented
<cr1901_modern>
And ARMv2 is the second most minimal ISA I've seen.