LunaVorax has quit [Remote host closed the connection]
wej has quit [Ping timeout: 264 seconds]
dandon has quit [Quit: .]
<K0D3R>
hello
dandon has joined #qi-hardware
<K0D3R>
where can I buy a Milkymist
<K0D3R>
?
<K0D3R>
sharism.cc is down
<K0D3R>
the links to hackabe-devices returns 404
<whitequark>
maybe you should ask wolfspraul
<K0D3R>
whitequark: who is wolfspraul
<K0D3R>
?
wolfspraul has joined #qi-hardware
porchao has quit [Ping timeout: 260 seconds]
porchao has joined #qi-hardware
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined #qi-hardware
<whitequark>
wolfspraul: K0D3R wants to buy an M1
<wolfspraul>
wow nice!
<whitequark>
but sharism.cc is down
<wolfspraul>
there were some hickups but it should be back up
<K0D3R>
wolfspraul: hey!
<whitequark>
wolfspraul: oh. some folks here decided that you've had "enough of it"
<whitequark>
I'm glad that's not true
<K0D3R>
wolfspraul: whitequark said that I should talk to you
<wolfspraul>
sure that's nice
<K0D3R>
how can I buy a Milkymist?
<wolfspraul>
just at sharism.cc
<wolfspraul>
we ship from Taipei and it should be with you in 3-4 days or so, depending on where you are
<wolfspraul>
we have shipped a lot to US, Australia, Europe
<K0D3R>
but it is down
<K0D3R>
I meant: sharism.cc is down
<whitequark>
K0D3R: up for me already
<K0D3R>
whitequark: oh! it's up now! thanks!
<K0D3R>
someone turned the switch on! :)
<K0D3R>
wolfspraul: do you ship it yourself?
K0D3R has quit [Quit: leaving]
<wolfspraul>
whitequark: thanks, I think I answered all his questions
<wolfspraul>
thanks for making the connection...
<whitequark>
wolfspraul: you're welcome :)
pcercuei has quit [Quit: Bye]
xiangfu has joined #qi-hardware
xiangfu has quit [Ping timeout: 245 seconds]
<Fallenou>
hi wolfspraul , good that sharism.cc is back on :)
wolfspraul has quit [Quit: leaving]
xiangfu has joined #qi-hardware
xiangfu has quit [Ping timeout: 240 seconds]
bzb has joined #qi-hardware
BenH685 has joined #qi-hardware
BenH685 has quit [Client Quit]
xiangfu has joined #qi-hardware
jekhor has joined #qi-hardware
xiangfu has quit [Quit: Reconnecting]
xiangfu has joined #qi-hardware
gbraad has quit [Ping timeout: 245 seconds]
bzb has quit [Quit: I hate to quit but my bladder's full. :-(]
jluis has joined #qi-hardware
fire has joined #qi-hardware
fire has quit [Ping timeout: 255 seconds]
fire has joined #qi-hardware
xiangfu has quit [Ping timeout: 255 seconds]
rz2k has quit []
apelete has joined #qi-hardware
eintopf_ is now known as eintopf
jekhor has quit [Read error: Operation timed out]
fire has quit [Quit: WeeChat 0.4.0]
LunaVorax has joined #qi-hardware
zear has quit [Ping timeout: 245 seconds]
wolfspraul has joined #qi-hardware
xiangfu has joined #qi-hardware
gbraad has joined #qi-hardware
fire has joined #qi-hardware
LunaVorax has quit [Ping timeout: 260 seconds]
porchao has quit [Ping timeout: 240 seconds]
porchaso0 has joined #qi-hardware
<wpwrak>
kristianpaul: not sure what you mean with moving things between application and kernel. i think an fpga should probably be assigned to a single task (process or group of cooperating processes), at least for now.
<wpwrak>
if someone can figure out a way to actually multitask with them, even better. so that's another item for the research topic list :)
<wpwrak>
(multitask) in this case, have independent tasks using them, e.g., a video game and a bitcoin miner
jekhor has joined #qi-hardware
xiangfu has quit [Ping timeout: 250 seconds]
xiangfu has joined #qi-hardware
xiangfu has quit [Remote host closed the connection]
jekhor has quit [Ping timeout: 252 seconds]
paul_boddie has joined #qi-hardware
<paul_boddie>
wpwrak: How did you do the video for http://en.qi-hardware.com/wiki/UBB-VGA (hint: not very descriptive page)? Is it all generated in the CPU's "spare moments" or is there some kind of backing store?
<wpwrak>
and it's unfortunately not in "spare moments". the cpu is working on it full-time. well, most of it is spent waiting for DMA, but it wouldn't be easy to let it do useful work instead of waiting.
<paul_boddie>
I guess the aim is to do live screen updates, rather than just push out still images, or am I wrong?
<paul_boddie>
The reason why I ask is because you were discussing FPGAs and the whole thing reminds me of some ULA-like circuitry from the microcomputer era that I've become interested in over the past year or so.
<wpwrak>
the initial aim was just a proof of concept. see how far i can take it in terms of image quality/resolution. that works pretty well now. but it only does still images.
<wpwrak>
for live updates, you'd have to move the DMA control and hsync processing into an interrupt handler and then time interrupts such that you never miss the time for the next line. (the cpu needs to intervene for each line, because the operation stalls the mmc controller)
<paul_boddie>
It's a shame that the 8:10 slot isn't like the expansion bus on various computers (or Firewire, maybe).
<wpwrak>
(and the mmc controller also spits out some "noise" that you don't want in the image. maybe you could work around this, though)
<wpwrak>
well, it's quite flexible
<paul_boddie>
In the sense that with various microcomputers, you could make peripherals that can access memory and stuff like that.
<paul_boddie>
I guess all that is formalised in various standard interfaces, though, but not for the 8:10 port.
<wpwrak>
way too complex :) and you don't want to expose a memory bus. not since 1990 or so, when they just started to get too fast for such things
<paul_boddie>
I was just thinking of the DMA aspect, but as I noted, I imagine that various standard interfaces provide that, and Firewire is notorious for doing so.
<paul_boddie>
A kind of slow-motion access to memory would be cool, but I agree that it would complicate things.
<wpwrak>
yeah, but that also means that you need a firewire controller on your boards. i prefer the simplicity of ubb :)
<wpwrak>
what would be nice is to have a cpld or small fpga between cpu and 8:10 card(s). that way, you could implement your own protocols.
<paul_boddie>
I guess you continuously drive the display instead of transferring a bitmap for output, then.
<wpwrak>
well, you have to continuously generate the video signal. even though the screen would probably have an internal frame buffer, it's not used in that way. and of course, even less so with vga.
<paul_boddie>
Yes, I have a small LCD panel for use with Arduino that probably has a more powerful CPU and more internal memory than the ATmega.
<paul_boddie>
For the video signal, I'd have thought we would be in FPGA territory.
<wpwrak>
what ubb-vga does is that it precomputes the bit pattern for the image. then it sends this pattern in an MMC block transfer. at the beginning of a line, the cpu needs to generate a start bit for MMC and mask the output for the mmc command (which would look like noise in the image).
gbraad has quit [Ping timeout: 245 seconds]
rz2k has joined #qi-hardware
<wpwrak>
(look like noise. or, worse, throw off the image position detection in the screen)
Jay7x is now known as Jay7
fire has quit [Quit: WeeChat 0.4.0]
emeb has joined #qi-hardware
<kristianpaul>
wpwrak: yes basically what you said i meant
Jay7 has quit [Read error: Operation timed out]
Jay7 has joined #qi-hardware
Jay7 has quit [Quit: Conversation terminated]
jow_laptop has quit [Quit: leaving]
jow_laptop has joined #qi-hardware
LunaVorax has quit [Ping timeout: 260 seconds]
rz2k has quit []
jekhor has quit [Ping timeout: 245 seconds]
Jay7 has joined #qi-hardware
LunaVorax has joined #qi-hardware
erikkugel has joined #qi-hardware
LunaVorax has quit [Ping timeout: 260 seconds]
fire has joined #qi-hardware
pcercuei has quit [Read error: Connection reset by peer]