simpl_e has quit [Remote host closed the connection]
simpl_e has joined #osdev
dude12312414 has quit [Quit: THE RAM IS TOO DAMN HIGH]
clever has quit [Ping timeout: 256 seconds]
clever has joined #osdev
Burgundy has quit [Ping timeout: 248 seconds]
[_] has quit [Ping timeout: 252 seconds]
[_] has joined #osdev
craigo has joined #osdev
AFamousHistorian has joined #osdev
xvmt has quit [Ping timeout: 260 seconds]
Vercas has quit [Quit: Ping timeout (120 seconds)]
modscleo4 has joined #osdev
xvmt has joined #osdev
<heat>
zid`, AMD K7 Athlon – microarchitecture of the AMD Athlon classic and Athlon XP microprocessors. Was a very advanced design for its day. First generation was built with a separate L2-cache chip on a board inserted into a slot (A) and introduced extended MMX. The second generation returned to the traditional socket form factor with fully integrated L2-cache running at full speed. The third generation, branded as XP, introduced full support for SSE.
<zid`>
Thanks bro
<zid`>
You've gotten a meme stuck to the bottom of your shoe and tracked it into the channel btw
Vercas has joined #osdev
genpaku has quit [Read error: Connection reset by peer]
genpaku has joined #osdev
clever has quit [Ping timeout: 260 seconds]
clever has joined #osdev
gog has quit [Ping timeout: 252 seconds]
genpaku has quit [Ping timeout: 248 seconds]
genpaku has joined #osdev
dude12312414 has joined #osdev
slidercrank has joined #osdev
masoudd has joined #osdev
bradd has joined #osdev
AFamousHistorian has quit [Quit: Leaving]
heat has quit [Ping timeout: 248 seconds]
<Jari--_>
morning from Finland EU
* Jari--_
got some ideas on how to implement semantic A.I. and integrate it into the OS
<Jari--_>
practical solutions, algorithms, etc. googled for months
[_] has quit [Read error: Connection reset by peer]
Burgundy has joined #osdev
dude12312414 has quit [Quit: THE RAM IS TOO DAMN HIGH]
gxt has quit [Remote host closed the connection]
gxt has joined #osdev
gorgonical has quit [Remote host closed the connection]
fedorafan has quit [Ping timeout: 248 seconds]
fedorafan has joined #osdev
masoudd has quit [Quit: Leaving]
Vercas has quit [Quit: Ping timeout (120 seconds)]
xenos1984 has quit [Read error: Connection reset by peer]
Vercas has joined #osdev
xenos1984 has joined #osdev
Vercas has quit [Remote host closed the connection]
Vercas has joined #osdev
pg12 has quit [Ping timeout: 252 seconds]
pg12 has joined #osdev
<sham1>
Machine learning to do things like scheduling
<sham1>
"Adaptive scheduling"
<sham1>
Anyway, the choice of algorithm really would depend on what you're trying to do with the AI
<sham1>
Hell, you would most likely not even need "complicated" things like neural networks to do stuff, but again, it depends
<sham1>
I suppose the biggest problem would be to a) gather the data set necessary and b) to train the damn model. You obviously would have to avoid overfitting, so something like k-fold cross-validation for training whatever model you'd be doing would be what you'd go for
<bslsk05>
developer.arm.com: Documentation – Arm Developer
masoudd has joined #osdev
masoudd has quit [Max SendQ exceeded]
<dinkelhacker>
My understanding is that at L1 and L2 tables I either point to subsequent table with a table descriptor or I directly map the block of memory (block entry).
<dinkelhacker>
But what's the table entry then?
ThinkT510 has joined #osdev
masoudd has joined #osdev
fedorafan has quit [Ping timeout: 248 seconds]
fedorafan has joined #osdev
masoudd has quit [Ping timeout: 252 seconds]
Vercas has quit [Quit: Ping timeout (120 seconds)]
Vercas has joined #osdev
danilogondolfo has joined #osdev
fedorafan has quit [Ping timeout: 248 seconds]
fedorafan has joined #osdev
eschaton has quit [Quit: ZNC 1.8.x-git-34-0db5c235 - https://znc.in]
Vercas has quit [Remote host closed the connection]
Vercas has joined #osdev
eschaton has quit [Remote host closed the connection]
vinleod has joined #osdev
vdamewood has quit [Read error: Connection reset by peer]
eschaton has joined #osdev
vinleod is now known as vdamewood
vdamewood has quit [Remote host closed the connection]
vdamewood has joined #osdev
Vercas has quit [Quit: Ping timeout (120 seconds)]
Vercas has joined #osdev
fedorafan has quit [Ping timeout: 248 seconds]
Turn_Left has joined #osdev
fedorafan has joined #osdev
Left_Turn has quit [Ping timeout: 252 seconds]
gxt has quit [Remote host closed the connection]
gabi-250 has quit [Remote host closed the connection]
foudfou has quit [Remote host closed the connection]
gabi-250 has joined #osdev
foudfou has joined #osdev
gxt has joined #osdev
nanovad has quit [Ping timeout: 252 seconds]
nanovad has joined #osdev
terminalpusher has joined #osdev
gxt has quit [Ping timeout: 255 seconds]
gxt has joined #osdev
craigo has quit [Quit: Leaving]
craigo has joined #osdev
Vercas has quit [Ping timeout: 255 seconds]
Vercas has joined #osdev
bradd has quit [Ping timeout: 268 seconds]
foudfou has quit [Quit: Bye]
foudfou has joined #osdev
Burgundy has quit [Ping timeout: 260 seconds]
zid` has quit [Read error: Connection reset by peer]
foudfou has quit [Remote host closed the connection]
foudfou has joined #osdev
zid has joined #osdev
gog has joined #osdev
zid has quit [Remote host closed the connection]
[itchyjunk] has joined #osdev
Vercas has quit [Ping timeout: 255 seconds]
zid has joined #osdev
Vercas has joined #osdev
Vercas has quit [Ping timeout: 255 seconds]
Left_Turn has joined #osdev
Turn_Left has quit [Ping timeout: 256 seconds]
Vercas has joined #osdev
masoudd has joined #osdev
masoudd has quit [Remote host closed the connection]
masoudd has joined #osdev
masoudd has quit [Max SendQ exceeded]
masoudd has joined #osdev
masoudd has quit [Remote host closed the connection]
masoudd has joined #osdev
Vercas has quit [Ping timeout: 255 seconds]
vdamewood has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
Vercas has joined #osdev
masoudd has quit [Quit: Leaving]
heat has joined #osdev
smach has joined #osdev
heat has quit [Remote host closed the connection]
smach has quit [Remote host closed the connection]
bauen1_ is now known as bauen1
gxt has quit [Remote host closed the connection]
gxt has joined #osdev
clever has quit [Ping timeout: 248 seconds]
terminalpusher has quit [Remote host closed the connection]
fedorafan has quit [Ping timeout: 252 seconds]
clever has joined #osdev
fedorafan has joined #osdev
sortiecat has joined #osdev
Arthuria has joined #osdev
Arthuria has quit [Read error: Connection reset by peer]
Arthuria has joined #osdev
SGautam has joined #osdev
Burgundy has joined #osdev
sortiecat has quit [Read error: Connection timed out]
sortiecat has joined #osdev
Matt|home has joined #osdev
vdamewood has joined #osdev
fedorafan has quit [Ping timeout: 246 seconds]
dude12312414 has joined #osdev
fedorafan has joined #osdev
sortiecat has quit [Read error: Connection timed out]
sortiecat has joined #osdev
gdd has quit [Ping timeout: 265 seconds]
gdd has joined #osdev
sortiecat has quit [Read error: Connection timed out]
sortiecat has joined #osdev
Left_Turn has quit [Read error: Connection reset by peer]
Left_Turn has joined #osdev
joe9 has quit [Quit: leaving]
xenos1984 has quit [Ping timeout: 252 seconds]
sortiecat has quit [Quit: Leaving]
xenos1984 has joined #osdev
wootehfoot has joined #osdev
ZombieChicken has joined #osdev
Sos has joined #osdev
x8dcc has joined #osdev
SGautam has quit [Quit: Connection closed for inactivity]
xenos1984 has quit [Ping timeout: 256 seconds]
potash has joined #osdev
dude12312414 has quit [Quit: THE RAM IS TOO DAMN HIGH]
xenos1984 has joined #osdev
potash has quit [Read error: Connection reset by peer]
Vercas has quit [Quit: Ping timeout (120 seconds)]
joe9 has joined #osdev
craigo has quit [Quit: Leaving]
Vercas has joined #osdev
_xor has quit [Ping timeout: 260 seconds]
_xor has joined #osdev
_xor has quit [Read error: Connection reset by peer]
_xor has joined #osdev
x8dcc has quit [Read error: Connection reset by peer]
zid has quit [Remote host closed the connection]
zid has joined #osdev
zid has quit [Ping timeout: 248 seconds]
zid has joined #osdev
wootehfoot has quit [Read error: Connection reset by peer]
Vercas has quit [Remote host closed the connection]
Vercas has joined #osdev
gxt has quit [Remote host closed the connection]
gxt has joined #osdev
hmmmm has quit [Ping timeout: 252 seconds]
x8dcc has joined #osdev
<x8dcc>
hello, I am trying to implement the simple getchar function I mentioned yesterday, but I have a small issue
<x8dcc>
I use an array to store the user's input chars, and it gets updated in the keyboard IRQ handler. This array is checked by the actual getchar function to check if its empty, and wait until it has a value
<x8dcc>
the problem is that with -O2 the compiler optimizes this empty while loop, so it never exits. Is there any way I can specify the compiler to make that check volatile?
<x8dcc>
afaik making the "static char[]" volatile *should* fix it, but I don't know if there is a better way since all the other array operations (for example in the kb handler) would not get optimized
<clever>
x8dcc: without volatile, gcc assumes there are no other things (threads/irq) that could change a variable
<clever>
and if a var is seen to have some value, it wont bother checking it again, until the local code has change it
<x8dcc>
yeah, with -O0 it works fine (at least that part)
<clever>
it can help to read the generated asm, and see what its really doing
<x8dcc>
clever: so making that array volatile would be the only way to tell the compiler to check that? my loop is literally "while (getchar_arr[pos] == EOF);"
<clever>
yeah, making the array volatile is one option
<x8dcc>
I guess since it's a simple function I could write it in assembly, but it seems kinda sketchy
<clever>
you could also have seperate read and write pointers, rather then relying on a magic value in the array
<clever>
and then make only those pointers volatile
GeDaMo has quit [Quit: That's it, you people have stood in my way long enough! I'm going to clown college!]
<x8dcc>
oh, wait, I could declare a local pointer to that array in that function and make that volatile, that could work too, right?
<x8dcc>
not sure if its what you meant but that could work
<clever>
have a read_pos and a write_pos index into the array
<clever>
the writer increments write_pos after writing data
<clever>
the reader increments read_pos after reading
<clever>
if readpos == writepos, then there is no data in the buffer
<clever>
and make writepos volatile
<clever>
plus some logic to wrap when you hit the end of the array
<x8dcc>
I see what you mean
<x8dcc>
yeah, I already check that
<geist>
yah make the head/tail pointers volatile. you'l;l want to anyway
<geist>
later on there are better ways of locking/synchronizing this, but for now spinning on some volatile regs will do t
<geist>
the array should probably be volatile too
<x8dcc>
okay, I fixed this part, something else is still broken but it's progress
<geist>
yay
<x8dcc>
thank you for the suggestions :)
<clever>
printf all the vars on every iteration?
<x8dcc>
hm?
<clever>
to debug what is making it not work
<x8dcc>
I'm going to use gdb since someone here told me how to use it without patching it lol
<clever>
the cpu isnt supported by gdb, and the jtag interface isnt documented publicly
<x8dcc>
haha
<clever>
i would have to implement my own gdbserver stub from scratch
<x8dcc>
oh I see
<x8dcc>
a nice vacation project is all I see
<clever>
and even then, there is the problem of what if the gdb server crashes?
<clever>
simpler to just printf debug my way to answers
ZombieChicken has quit [Ping timeout: 255 seconds]
<x8dcc>
meta-debug the debugger
ZombieChicken has joined #osdev
<mrvn>
x8dcc: volatile isn't enough when you have multiple cores.
<mrvn>
You need the hardware approriate memory barriers around each access so you might as well use atomic and let the compiler handle that.
<geist>
mrvn: we know this, we're just trying to keep it simple for now
<geist>
this spinning on volatile thing is not the ultimate solution, but will work for now until proper blocking/etc is immplemented
<mrvn>
except it has race conditions and will drop keys randomly and isn't really simpler than atomic.
<mrvn>
you can spin on atomic too
<geist>
feel free to help them implement atomics
<mrvn>
thank good for builtins
<mrvn>
-o
<geist>
feel free to help them implement wrappers for the builtins, etc
<geist>
x8dcc: i never asked, what architecture are you working with here?
<mrvn>
also C or C++?
<mrvn>
and what standard version
<mrvn>
.oO(volatile being deprecated makes it rather more complex in newest standards)
<x8dcc>
okay, I fixed it completely
<x8dcc>
mrvn: for now I am only working with 1
<x8dcc>
geist: I want to make it 32 bit
<geist>
sure, but what architecture? x86?
<x8dcc>
yes
<x8dcc>
I am not sure if I will end up adding ring3 userspace or everything ring0
<geist>
yah that comes quite a ways down the road
<x8dcc>
I kinda like both ideas, I know ring3 is obviously better
<x8dcc>
mrvn: C, I am not using any C++ code
<mrvn>
urgs. you might want to rethink that. Unless you want an OS for some industrial PC boards 32bit just forces you to learn stuff you never need again and adds problems you rather wouldn't have.
demindiro has joined #osdev
<mrvn>
I assume you don't actually have a 32bit only cpu?
<x8dcc>
no I don't, but what do you mean? rethink using cpp?
<geist>
i think they're talking about rethinking x86-32
<geist>
since presumably you're using x86-64 now?
<demindiro>
x64 is better in pretty much every way
<mrvn>
x8dcc: rething going to 64bit long mode
<demindiro>
Larger address space, more registers etc
<x8dcc>
geist: my host machine is x86-64, yes
<demindiro>
RIP relative addressing especially
<geist>
mrvn: or you mean the opposite? *not* going to long mode?
<mrvn>
no, I mean he should take the leap and go long mode.
<mrvn>
The little time spend learning how to switch to long mode is well worth it. Easily saved later one because the arch is just better.
<geist>
but they already are aren't they?
<x8dcc>
well for now I want to keep making it 32 bit, and maybe I will switch in the future
<demindiro>
I would do it now
<geist>
oh! you're in 32bit x86
<geist>
i see. yeah you'll want to switch fairly soon, trouble is of course all the page table stuff, which to a newbie is a big pile of nonsense
<demindiro>
It's a tiny effort that'll save you headaches later
<x8dcc>
hmm, I will think about it
<geist>
but anyway, i'm happy you're making progress with IRQs and whatnot. what i'd personally do is flesh that out a bit, get handy with interrupts and generally speaking building up some infrastructure for kernel mode
<x8dcc>
now that I have getchar, I can focus on the #1 most important priority. The pc speaker piano.
<geist>
then basically start over with what you know, go directly to x86-64
<geist>
oh or the pc speaker piano. sure if you have a specific goal x86-32 will do that just fine
<x8dcc>
geist: yeah, is what I thought initially, start with this and once I know what I am doing, maybe try 64bit
<geist>
and honestly you dont even need interrupts for that, can just poll the keyboard
<mrvn>
x8dcc: with just single tones or mixing multiple key preses?
<mrvn>
also: 1 bit sound quality sucks.
<mrvn>
been there, done that. :)
<x8dcc>
heresy
<x8dcc>
it is perfect in every way
<x8dcc>
anyway, I guess for now single tones, not sure how hard it is to mix them
<mrvn>
ever done sound recording by polling the dataset port on the C64?
hmmmm has joined #osdev
<x8dcc>
the piano thing is just a dumb game, btw, it's obviously not my final goal haha
<geist>
well it *is* a timer on the PC, so its not quite as bad as having to manually flip the speaker back and forth (ie, apple 2)
<mrvn>
x8dcc: hard. you have to compute the wave form and then turn the speaker on/off to make the waveform. Single tone you just set a pitch and volume.
<geist>
at least with PC you're basically furiously reprogramming a square wave generator
<x8dcc>
mrvn: I don't know what the "dataset port on the C64" is
<x8dcc>
mrvn: isn't that what doom used? I think I read something like that in the osdev wiki or somewhere else
<mrvn>
x8dcc: it's where you connect the tape recorder to load/save data. It has a low and high pass filter on it so you can detect 2 tones.
<x8dcc>
damn, that sounds extremely easy and friendly
<mrvn>
So recroding from it all you get is 2 frequencies basically.
<mrvn>
1 bit quality too. it's beRAUSCHend.
<geist>
heh i wouldn't call that extremely easy and friendly
<geist>
more like, slightly more functional
<x8dcc>
do you know if the templeos piano app supports multiple key presses? I am guessing it does
<x8dcc>
that app (and templeos in general) would be my ideal perfect os, but you know, I am not him
<mrvn>
x8dcc: blasphemer. Thou shall have no other OSes than TempelOS.
<x8dcc>
amen
<x8dcc>
you should search the "adulteress" video of templeos, truly beautiful
dutch has quit [Quit: WeeChat 3.8]
<sham1>
TempleOS. Did Terry ever conclude that it indeed is the 3rd Temple™?
<kof123>
i always took at as somewhat tongue in cheek, no idea
* kof123
points up like alchemist
dutch has joined #osdev
smach has joined #osdev
demindiro has quit [Quit: Client closed]
[itchyjunk] has quit [Read error: Connection reset by peer]
Vercas has quit [Quit: Ping timeout (120 seconds)]
Vercas has joined #osdev
danilogondolfo has quit [Remote host closed the connection]
bauen1 has quit [Ping timeout: 246 seconds]
bauen1 has joined #osdev
slidercrank has quit [Ping timeout: 248 seconds]
gog has quit [Read error: Connection reset by peer]