<geist>
Yeah just checked, does basically the same thing. The difference is i also have an ASSERT_MSG version which also takes an additional printf style arg
<klange>
I just write assert(cond && "Some extra message") if I want something readable
<moon-child>
but what if you wanna say assert(x < 5, "x was %d :/", x)
<klange>
then you will suffer
fly_ has quit [Quit: Lost terminal]
<geist>
Right the latter is precisely what i use it for
<geist>
Very useful
sortie has quit [Quit: Leaving]
hmmmm has joined #osdev
elastic_dog has quit [Ping timeout: 245 seconds]
dutch has quit [Quit: WeeChat 3.2]
dutch has joined #osdev
elastic_dog has joined #osdev
moon-child has joined #osdev
<gorgonical>
Okay can anyone give me an idea about why I can't get u-boot to work on my pine64-lts? I have the u-boot SPL booting, and trustedfirmware's bl31 starting. But that sequence bootloops
<gorgonical>
Basically, my understanding is that the rest of u-boot should be at that address 0x4a000000, but what loads it there? I dd'd the u-boot-sunxi-with-spl.bin to where it said to put it, but this output over serial makes me think something is supposed to actually copy u-boot there.
gog has quit [Ping timeout: 240 seconds]
sts-q has quit [Ping timeout: 272 seconds]
ElectronApps has joined #osdev
Izem has joined #osdev
flx-- has joined #osdev
sts-q has joined #osdev
flx- has quit [Ping timeout: 258 seconds]
ElectronApps has quit [Read error: Connection reset by peer]
ElectronApps has joined #osdev
srjek|home has joined #osdev
srjek has quit [Ping timeout: 258 seconds]
Izem has quit [Ping timeout: 258 seconds]
Izem has joined #osdev
dh` has joined #osdev
srjek_ has joined #osdev
sm2n_ is now known as sm2n
srjek|home has quit [Ping timeout: 256 seconds]
srjek_ has quit [Ping timeout: 258 seconds]
shikhin has joined #osdev
GeDaMo has joined #osdev
froggey has quit [Ping timeout: 252 seconds]
YuutaW has quit [Ping timeout: 240 seconds]
froggey has joined #osdev
YuutaW has joined #osdev
Izem has quit [Ping timeout: 258 seconds]
flx-- has quit [Remote host closed the connection]
flx- has joined #osdev
Izem has joined #osdev
mahmutov has joined #osdev
Izem has quit [Quit: Going offline, see ya! (www.adiirc.com)]
lleo has joined #osdev
<klange>
Weather has me feeling completely unmotivated... bah...
<moon-child>
eh...I'm feeling demotivated despite extremely good weather!
<moon-child>
at least you have an excuse :)
mctpyt has quit [Ping timeout: 272 seconds]
lleo has quit [Ping timeout: 276 seconds]
elastic_dog has quit [Ping timeout: 256 seconds]
elastic_dog has joined #osdev
regreg has joined #osdev
iorem has joined #osdev
regreg has quit [Ping timeout: 276 seconds]
iorem has quit [Ping timeout: 258 seconds]
pretty_dumm_guy has joined #osdev
pretty_dumm_guy has quit [Client Quit]
pretty_dumm_guy has joined #osdev
sortie has joined #osdev
ElectronApps has quit [Remote host closed the connection]
<zid>
IRQs go to an offset interrupt vector in most setups
<zid>
PIC controls it unless you're using lapics or whatever
<zid>
because the low interrupts are reserved for exceptions
<geist>
nur: right, it's part of the PIC setup (two pics) to give an offset of of which vector to deliver
<geist>
since 0-0x1f are reserved for exceptions on x86, the first obvious place to deliver PIC interrupts are 0x20 - 0x2f
<nur>
ahhhh
paulbarker has joined #osdev
<zid>
you can overlap them if you want but it makes it pretty hard to tell them apart
<geist>
so some firmware before you must have configured it that way
<nur>
so in the interrupt table do I set up 0x20 for irq0 or 0x0?
<zid>
I think DOS actually did have them overlapped?
theruran has joined #osdev
SanchayanMaity has joined #osdev
jakesyl has joined #osdev
<geist>
nur: 0x20
<geist>
if you configure the PIC that way, but it's a nice default way to do it
<geist>
and yes classic DOS/BIOS configured it another way, but that was a mistake because someone at IBM didn't read the 8088 manual close enough
<geist>
and they dealt with it forever
<nur>
man
<geist>
honestly not sure why you are observing it already configured at 0x20, unless you're running a bootloader or you copy/pasted the PIC setup code
<geist>
since coming out of the BIOS it is probably conigured somewhere else
<nur>
also the interrupt only fires once, which is weird. I'm probably doing something wrong wrt loading the timer value.
<zid>
seabios uefi or something maybe?
<nur>
I copy pasted the PIC setup code.
<geist>
nur: correct, you have to EOI (end of interrupt) acknolwedge with the PIC
<geist>
ah yes okay, if you look at the setup code it probably configures the offset
<nur>
iret does the EOI right?
<geist>
it may be non obvious but basically there's a register in there somewhere where you provide the top 5 bits of the IRQ
<geist>
er IRQ Vector, hence why you have to configure it to a multiple of 8
<geist>
nur: honestly i dont remember the specific details enough
<geist>
i dont think so, no.
<nur>
well, a clue.
<nur>
thanks :)
<geist>
right
<geist>
fairly certain you have to EOI the PIC, but i've dealt with so many interrupt controllers they just blur together and PIC is particularly wonky (becausei t's old)
<nur>
thanks! this helps a lot
<sortie>
I have coffee and a crazy plan
<sortie>
It's time to migrate my https://sortix.org host to another host and proxy it into a VM running my OS. Already got a prototype and why not just make it official
<bslsk05>
sortix.org: The Sortix Operating System
<geist>
oh no sortie is nuts
<geist>
someone, quick sneak a downer in his cup!
<geist>
he's outtta control!
<sortie>
The obvious risks is that if my OS crashes, it can impact the availability of the OS
<sortie>
And who knows how well this scales
<sortie>
Look at my crazy recklessness!
<sortie>
I don't even have cookies on my domain!
srjek_ has joined #osdev
srjek_ is now known as srjek
<sham1>
No cookies? Blashemy
<kingoffrance>
no, he's sane. coffee and a crazy plan. crazy plan, or crazy plan then coffee, would be insane
regreg has joined #osdev
<kingoffrance>
he has maintained the priority/hierarchy
<kingoffrance>
coffee first
<nur>
HUZZAH MY TIMER WORKS
<nur>
thanks room
<zid>
channel
<nur>
po-tay-to, po-tah-to
<gog>
podate
<sortie>
Time to augment my coffee with snacks
<kingoffrance>
see, he knows how to avoid anti-pattern
<nur>
cheers sortie! I too should snack to celebrate except it's 3:21 am and snacks are a bad idea.
<sortie>
nur, that has never stopped me before
<nur>
I'm still pleased with myself that I made a great pasta last night but I am out of anchovies
XgF has joined #osdev
devcpu has joined #osdev
<nur>
time to move on to my next impossible task, pagetables
<j`ey>
nur: fun!
<sortie>
OK I'm out of snack, this crazy plan of mine calls for beer
<sortie>
Now I'm translating .htaccess into httpd.conf(5)
mctpyt has quit [Ping timeout: 252 seconds]
GeDaMo has quit [Quit: Leaving.]
pretty_dumm_guy has joined #osdev
pretty_dumm_guy has quit [Client Quit]
pretty_dumm_guy has joined #osdev
pretty_dumm_guy has quit [Client Quit]
pretty_dumm_guy has joined #osdev
pretty_dumm_guy has quit [Client Quit]
pretty_dumm_guy has joined #osdev
regreg has quit [Ping timeout: 240 seconds]
<geist>
nur: yay! did you have to EOI it?
<geist>
what i never remember precisely is whether or not it's edge or level, and when you have to EOI (or if you use the auto-EOI feature, etc)
<geist>
there's some setup details with the PIC that are a bit wonky. paradoxically lots of newer interrupt controllers tend to be simpler to operate