<rqou>
azonenberg: so i herd u liek floating point :P
<cr1901_modern>
Needs more parallel universes
_whitelogger has joined ##openfpga
<awygle>
This person has a lot of really cool sm64 videos
MrY has joined ##openfpga
<cr1901_modern>
I'm blown away that ppl can look at 8MB of MIPS code for long enough to extract all the game behavior :P
<cr1901_modern>
Of course, if I were used to reading MIPS code I'd say something different
<awygle>
I wouldn't. 8MB of any assembly == no thanks
<cr1901_modern>
(it's not actually 8MB of .text of course)
test123456 has quit [Ping timeout: 240 seconds]
<awygle>
The hacking tools they have for SM64 blow my mind
<awygle>
(my mind is easily blown in this direction)
<Bike>
i thought n64 was like, super underspecified compared to most consoles
<cr1901_modern>
Bike: Well, there's a manual if you know where to look. And based on an interview, the n64 was made to be deliberately difficult to program effectively
<cr1901_modern>
to weed out shoddy third party content in theory (not sure it worked!)
<Bike>
wow, that sucks
<Bike>
i also heard that if you want to emulate n64 games the best way to do it is to get Dolphin and use Virtual Console on it
<cr1901_modern>
That's probably true. The n64 reality display processor's verilog code was leaked some time ago tho- it's n64 emu dev's dirty secret
<Bike>
oh! huh
<rqou>
cr1901_modern: last time this was brought up didn't we establish that that dump is missing the code for the mips core inside the RSP?
<rqou>
(as well as the rambus interface, but that's boring)
* cr1901_modern
shrugs... easier to make a MIPS core w/ the right signals than it is a custom ASIC
<cr1901_modern>
Not sure if this true, but I heard the person- Oman- who leaked it went to jail for this (cc: X-Scale is this true?)
<rqou>
uh, except that somebody mentioned that that core has suuper secret mpeg-related instructions
<rqou>
that apparently nobody bothered to RE properly?
digshadow has joined ##openfpga
<cr1901_modern>
I don't know if my copy is the entire thing. AFAIK, there exists a larger archive that most ppl don't have access to.
<rqou>
i thought the mips/rambus parts are speculated to be hard macros?
<rqou>
or maybe there's models of them in the large archive
<cr1901_modern>
Idk what a hard macro is (precompiled verilog IP?)
<rqou>
essentially it's like "a .o file"
<cr1901_modern>
Oh, WDC offers that for their 6502 cores
<rqou>
yes
<rqou>
but i'd rather have hdl for a 6502 core
<rqou>
or i'd rather just have a not-shit core :P
<rqou>
like j-core/lm32/mor1kx/picorv32/whatever
<cr1901_modern>
Do your own (and piss off everyone who'd rather you do another not-MIPS)
<cr1901_modern>
/bait
Patater has quit [Ping timeout: 255 seconds]
Patater has joined ##openfpga
azonenberg_work has joined ##openfpga
_whitelogger has joined ##openfpga
pie_ has quit [Remote host closed the connection]
pie_ has joined ##openfpga
pie_ has quit [Read error: Connection reset by peer]
pie_ has joined ##openfpga
Patater has quit [Ping timeout: 252 seconds]
theMagnumOrange has quit [Ping timeout: 264 seconds]
<azonenberg>
you can't give someone verilog source for, say, a PLL
<azonenberg>
Or an ADC
<azonenberg>
that all has to be hand drawn
<azonenberg>
High-performance digital stuff is often hand optimized and then supplied as layout as well
<azonenberg>
although they may give licensees the HDL for reference as well
<awygle>
What's the deal with Verilog-AMS?
<awygle>
Is that like, a thing? That's relevant here?
<azonenberg>
It's an analog modeling langauge that is AFAIK mostly used for sim models of analog IP
<azonenberg>
i dont know if you can actually do design entry with it
<azonenberg>
i've considered using it for some greenpak stuff but have not had the time to actually learn it / implement support in free tools that largely lack it :p
m_t has joined ##openfpga
pie_ has quit [Ping timeout: 240 seconds]
_whitelogger has joined ##openfpga
knielsen has quit [Quit: leaving]
knielsen has joined ##openfpga
pie_ has joined ##openfpga
digshadow has quit [Quit: Leaving.]
qu1j0t3 has quit [Ping timeout: 240 seconds]
_whitelogger has joined ##openfpga
indy has quit [Ping timeout: 240 seconds]
pie_ has quit [Ping timeout: 252 seconds]
qu1j0t3 has joined ##openfpga
indy has joined ##openfpga
indy has quit [Ping timeout: 248 seconds]
indy has joined ##openfpga
finsternis has quit [Remote host closed the connection]
finsternis has joined ##openfpga
xdeller has joined ##openfpga
Bike has joined ##openfpga
flaviusb has quit [Quit: Leaving.]
flaviusb has joined ##openfpga
pie_ has joined ##openfpga
pie_ has quit [Ping timeout: 258 seconds]
ZipCPU|Laptop has joined ##openfpga
ZipCPU|Laptop has quit [Ping timeout: 252 seconds]
cr1901_modern has quit [Ping timeout: 248 seconds]
<awygle>
pointfree: those Wikipedia pages are the total sum of my knowledge on the topic. Are they actually used? Can you use them for design or just simulation?
theMagnumOrange has joined ##openfpga
m_t has quit [Ping timeout: 258 seconds]
lexano has quit [Remote host closed the connection]
digshadow has joined ##openfpga
pie_ has joined ##openfpga
digshadow has quit [Ping timeout: 252 seconds]
digshadow has joined ##openfpga
GenTooMan has joined ##openfpga
Xark has quit [Ping timeout: 264 seconds]
Xark has joined ##openfpga
Xark has joined ##openfpga
Xark has quit [Changing host]
digshadow has quit [Quit: Leaving.]
MrY has quit [Quit: Leaving]
lexano has joined ##openfpga
digshadow has joined ##openfpga
Xark has quit [Ping timeout: 248 seconds]
Xark has joined ##openfpga
eduardo has joined ##openfpga
ZipCPU|Laptop has quit [Ping timeout: 246 seconds]
xdeller has quit [Quit: Leaving]
<azonenberg>
pointfree, awygle: i have a ticket filed for verilog-ams support