gog, I just thought about myself wearing that and vomited a little bit.
vdamewood has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
Not into chokers.
vdamewood has joined #osdev
sdfgsdfgs has joined #osdev
what about the skirt and the gloves?
[_] has joined #osdev
[itchyjunk] has quit [Ping timeout: 252 seconds]
dutch has quit [Ping timeout: 252 seconds]
dutch has joined #osdev
gog: more defined pleating, please; and those are arguably just arm covers and not gloves, gloves need at least a bit more intentional hand coverage
gog has quit [Ping timeout: 260 seconds]
oh no my opinions on skirts knocked out gog
gog has joined #osdev
Yay, gog's back.
gives gog a fishy in a skirt, 'gloves', and a collar.
me marries the fishy
[_] is now known as [itchyjunk]
divine has joined #osdev
srjek has quit [Ping timeout: 252 seconds]
sts-q has joined #osdev
JerryXiao has joined #osdev
nyah has quit [Ping timeout: 265 seconds]
_eryjus has joined #osdev
kanzure has joined #osdev
sts-q has quit [Ping timeout: 245 seconds]
sts-q has joined #osdev
nj0rd has joined #osdev
xenos1984 has joined #osdev
Oli has quit [Quit: leaving]
dude12312414 has quit [Quit: THE RAM IS TOO DAMN HIGH]
[itchyjunk] has quit [Read error: Connection reset by peer]
klys has joined #osdev
dormito10 has joined #osdev
dormito11 has joined #osdev
dormito has quit [Ping timeout: 252 seconds]
dormito10 has quit [Ping timeout: 265 seconds]
ElectronApps has joined #osdev
They're definitely arm wraps.
Not to be confused with ARM wraps.
prefers aarch64 wraps
wleslie has joined #osdev
I think I may be beginning to understand PCI. I've been comparing open source drivers and the osdev wiki and I think I've got something. I would love to hear if I'm missing something. Here goes:
so if you're implementing PCI, there's not much that is genuinely needed; but seems to be a whole stack of optional, useful interfaces it provides. you can get by simply enumerating the devices on each bus, querying their vendor and product or class and subclass, starting the relevant driver and mapping physical addresses and io ports described by
any BAR into the driver's address space and calling it done.
now it's a good idea to go through and compare the resources claimed by each BAR to ensure that there are no overlaps, especially if you have hotplug devices, but BIOS systems should already be set up without any resource conflicts
Yep, that's pretty much it
On PCs (which have a pretty advanced pre-boot firmware), all devices will have had IO and memory spaces allocated, so all you need to do is enumerate it and use the pre-existing regions
dormito11 is now known as dormito
superb. so I can go back and add support for power management or MSI when I need them, and get on with porting drivers for now.
I still need to set up mapping for devices the BIOS didn't set up for me - my ExpressCard XHCI card is unconfigured.
xenos1984 has quit [Read error: Connection reset by peer]
thanks, that's good to know. so if I have a driver for some hardware, it is worth asking the driver which BARs should be configured?
Iirc I've done two approaches
1. The PCI bus handler detects the BAR types (by checking the set bits), and determines the size (by doing a read/write/restore)
2. The device driver queries the bus handle for the BARs it actually needs
updated my testing procedure, instead of needing to manually power my test VM off, scp the new bootable ISO to the ESXi box, and power it back on, I just copy the new boot images to the TFTP root and punch "reload" into the serial console
valerius_ has joined #osdev
zaquest has quit [Remote host closed the connection]