| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10
Comments:
<0> dw zb_gdt: dw zb_gdt_end - zb_gdt_start - 1
<0> dd zb_gdt_start
<0> pretty sure I just need the addresses?
<1> .short zb_gdt_end - zb_gdt_start - 1
<0> but wont do that with the values that the variables hold?
<0> rather than their addresses?
<1> .int/.short/.byte always use numbers plainly
<1> recall, .byte 0 places value 0
<1> even though you need $0 in instruction
<0> well, ill try it
<0> lgdt [gdt_pointer]
<0> in nasm
<0> will just be :
<0> lgdt gdt_pointer in AT&T?
<0> also, Im not sure how : jmp 0x08:function would be in AT&T
<1> lgdtl
<0> lgdtl ?
<0> gotcha
<1> yeah
<0> what about the second part?
<0> the DD aprt?
<0> .int VAULE ?
<1> DD == .int
<0> yeah
<0> ill give it a shot
<0> still no idea how to do : jmp 0x08:blah
<0> ljmp 0x08:blah?
<1> ljmpl $0x8, $blah
<0> ah, I see
<0> thanks!
<0> Ill try it :D
<0> It worked, MWK :D
<0> bootloader is translated :D
<0> :D
<1> good
<2> hehhe jeez :)
<2> one dunno asm
<2> and is trying to code a hello world boot loader ..
<2> hmmm
<3> Oh noes.
<3> Yet another one!
<4> lol
<5> if a usb cable has black/red for power, and green/white for TX/RX, and another has blue/black for power, grn/wht for data, is it safe to ***ume green -> green, white -> white?
<6> *probably*, but if you could double check that'd be great
<5> geist: but it wont break anything permanently, correct?
<5> it just wont work
<5> I know the power is correct
<6> sure, if you wire it up wrong it could very easily fry the device and/or the host
<1> i once fried host controller by connecting it wrong
<6> exactly
<1> so it definately isn't safe
<6> i've cooked a firewire deivce (my old 5GB ipod) by plugging it in upside down
<5> mwk: that's power too tho, no?
<5> only thing im not 100% sure on is the TX/RX lines
<6> incrrect polarity on the power lines is probably more of a concern
<5> im 100% sure i have the power lines (GND/VCC) correct
<6> and it was *always* correct? all it took was one time to plug it in wrong to fry the PHY
<5> geist: yes
<5> the red line had +5 on the 5 pin end, and the red was marked VCC on the 4 pin header end
<5> i just couldnt gather anything useful off the TX/RX with my cheap mulitmeter
<6> you're ***uming the colors are correct
<6> therefore you dont 100% know that you have it wired correct
<6> personally i would avoid screwing with what you're doing unless you know what you're doing
<6> or have a multimeter that can check continuity
<7> "do I cut the red wire?!" <kersplode>
<5> geist: ah, i went on the red wire had +5Vdc on the original cable
<5> and the 4 pin header is marked VCC
<6> *shrug*. dunno what you want me to do
<5> geist: *shrug* :)
<6> blow it up if you want. I'd test it with a multimeter
<6> usb is not tolerant of swapped wires at all
<5> geist: the power's not the issue.. i'm just wondering if i mix the 2 data lines up, is it likely to break it?
<6> probably. you may have already fried it
<5> geist: i've not connected it yet, thats why i ask :)
<5> before i break it :)
<5> multimeter gives nothing useful on either data line
<6> you can check continuity
<6> actually, i have no idea what you're doing
<6> there's no other end of the cable?
<3> Bwahaha.
<3> Maybe it's a circular cable?
<5> geist: It's a 4pin to connect to a mobo header
<5> other end has the mini 5 pin thingy
Return to
#osdev
or
Go to some related
logs:
songbird sources.list debian sarge
gentoo Please Recompile with USE
proxifer
GPG Error apt-get debootstrap
tslib tarball
#centos
ubuntu HDIO_GETGEO failed: Inappropriate ioctl for device
(defun Dijkstra)
#debian
package javax.servlet does not exist gentoo
|
|