#tyndur · 2010-04-06

191 Nachrichten · Seite 1 von 1 · Original-CSV herunterladen

  1. eddybXanClic: started to revive my ehci driver
  2. eddybno irq on virtualbox :((
  3. XanClicVBox has a bug there
  4. eddybit has?
  5. XanClicTry the IRQ below
  6. eddyblike 10 instead of 11?
  7. XanClicExactly
  8. eddybin vmware it goes pretty well
  9. eddybi get an irq when a device connects...
  10. eddybbut the schedule won't start
  11. eddybalso, it reports frame list rollover, but i got periodic schedule disabled(maybe i've switched the bits by mistake???)
  12. eddybthe interrupt thing makes no difference :|
  13. XanClicWell, for me it did ;-)
  14. XanClicAnd for some others I know, too
  15. eddybwtf?
  16. eddyb3 pci devices report interrupt number 11 :O
  17. XanClicNever heard of IRQ sharing?
  18. eddybhow much memory space OHCI uses?
  19. XanClicHm, 4 kB, I think
  20. eddybs/memory/mmio\/io/
  21. eddyb0x1000
  22. eddybexactly the number of mmio space one of the other devices with irq 11 got
  23. eddybthe device with irq 10 got 0x20 of io, 0x40000 of mmio and another 0x4000 of mmio
  24. XanClicIt's a network device
  25. XanClicI already checked tha
  26. XanClict
  27. eddybbut i don't get any irq, even if i add "-1" :(
  28. eddyboh, and also "<eddyb> okey, this is really stupid. but the beggining of my memory region i use in ehci driver got "SQLite format 3" :|" << this is quite strange and i think it's related to pedigree
  29. eddybdon't tell me...
  30. eddybthere's only a handler/irq allowed in pedigree
  31. XanClicThat's what I'd call a "fail" *g*
  32. eddybwhich can be == fail
  33. eddybheh, in the same time :P
  34. eddybthe problem is...
  35. eddybfrom the handler registration and first request, there's just a couple of instructions :|
  36. eddybBINGO
  37. eddyb+1 means 12, which is mouse irq. the good thing is that i can move the mouse and make it complete transactions :P
  38. eddybdamn non-working irq...
  39. eddybit does set the connect status changed bit, and i can see new devices
  40. eddybXanClic: afaik, you haven't touched ehci yet... you had problems with ohci, then?
  41. eddybbtw, no unhandled irq showed up
  42. XanClicNo, I've also touched EHCI
  43. eddybaah
  44. eddybno irqs at all
  45. eddyb== nothing reached the ISR
  46. eddybso it's more internal, if there is a problem
  47. eddybargh, linux can ahdnle it
  48. eddyb*handle
  49. XanClicOf course
  50. XanClicLinux remaps the IRQs
  51. eddybxD
  52. eddybvia some PCI nifty config stuff, i suppose?
  53. XanClicVia APIC
  54. eddybah, ok
  55. eddybapic is kinda unfunctional in pedigree
  56. eddybhmm...
  57. eddybso it can be that without that remapping you say linux is doing, no interrupt from ehci will reach even the ISR ?
  58. XanClicYes, because VBox gives you the wrong IRQ number
  59. XanClicAnd it is 10 for sure, it's not just me who detected that *g*
  60. eddybbut as i said, no interrupt reach PIC driver
  61. eddyb*reaches
  62. XanClicPedigree's got a driver for VBox' network card?
  63. kwolfe1000
  64. eddybsorry, afaik, i've enabled no network card
  65. kwolfXanClic: Paloxena has the same driver once you apply Matt's latest patch
  66. eddyband i made PIC driver print every irq(except 0 and 8)
  67. XanClickwolf: And once I've implemented CDI, yes ;-)
  68. eddybXanClic: so, what now? i told you it doesn't even reach ISRs
  69. XanClicWell, I don't know.
  70. XanClicYou have several problems to which I just answer "works for me" ;-)
  71. kwolfXanClic: I was talking about one of the Paloxena versions that have CDI ;-)
  72. XanClickwolf: But those don't have USB ;-)
  73. kwolfUntil you finish USB for CDI. ;-)
  74. XanClicI guess, that's no repeat-until but a repeat-forever *g*
  75. XanClici.e., I doubt it'll be ever finished
  76. eddybgood
  77. eddybotherwise i'd have to throw my work into trash://
  78. kwolfWell, yes, wrong word. An OS is never finished. ;-)
  79. XanClicNo, I meant I think I continue with my CDI.storage attempts ;-)
  80. XanClic(Triple I, yeah)
  81. kwolf*sigh* Why that?
  82. XanClicI don't know how to implement USB efficient when using different address spaces
  83. XanClicI don't even know how to implement it inefficiently *g*
  84. kwolfWe probably need to have you around at the next hackathon to sort things out
  85. kwolfShouldn't be all that hard, though
  86. XanClicYou won't accomplish that *g*
  87. eddybXanClic: OOI, on which version of virtualbox irq 10 works for you?
  88. XanCliceddyb: 3.1.4, afair
  89. eddybthat's quite recent :(((
  90. kwolfXanClic: I meant the implementation. I'm afraid getting you there is too hard indeed. ;-)
  91. eddybdamn poor radio internet :((
  92. eddyb3.1.2 r56127 here
  93. XanClicI had the same problem in 3.1.2, too ;-)
  94. eddybXanClic: do you have any source code for reference?
  95. eddybi'm getting sick of vm bugs
  96. XanClichttp://gitorious.org/paloxena/kernel3/blobs/master/src/kernel/drivers/network-controller/ehci.c maybe
  97. XanClicAnd http://gitorious.org/paloxena/kernel3/blobs/master/src/kernel/drivers/network-controller/ehci.c#line140 in particular for VBox *g*
  98. eddyb"(NN) e1000: Fuehre Reset der Karte durch" << stuck at there :|
  99. eddybwhy is it in network controllers?
  100. XanClicBecause all my USB HCs are network controllers for the OS
  101. XanClicThey send packets, just as a network card does *g*
  102. Homixhm funny^^ ;)
  103. eddybpci_outw(pci->bus, pci->dev, pci->func, 0x04, 0x06); << what does this do?
  104. XanClicIt writes 0x06 into the PCI configuration space at offset 0x04
  105. XanClicA word
  106. eddybok, but what's the effect?
  107. XanClic=> Enabling bus master capability and MMIO
  108. eddybah, k
  109. eddybdelay() does delay in ms?
  110. XanClicNo, in µs, afair
  111. XanClicAnd heart_beat_count is the system timer which is incremented every ns
  112. eddybare those waits really necessary?
  113. XanClicWhy not?
  114. XanClicThose are done just once
  115. eddybno, i mean not having them can cause problems?
  116. XanClicWell, I don't know
  117. eddybif you'd see my code, you'd say C++ makes things go water shrink :P
  118. eddybexcept for the waits and the big C stuff, i see nothing different
  119. eddybhmm...
  120. eddybdo waits do wonders?
  121. eddybbut still no irq :((
  122. Jarvixhi
  123. XanClicmoin, Jarvix
  124. quokmoin :)
  125. XanClicmoin, quok
  126. kwolfMoin quok
  127. eddybgreat, manually waiting, i get XactErr set :(
  128. XanClicNice, I get that one, too ;-)
  129. eddyblol?
  130. eddybVirtualBox?
  131. XanClicYe
  132. XanClics
  133. XanClicThough I receive an interrupt
  134. eddybwhich i don't :/
  135. eddybhmm, maybe i can make pedigree boot from this usb stick...
  136. eddybit would really help :|
  137. eddyb(considered now we have on screen log - half of it, actually - :P)
  138. eddybbtw, what ping really does in ehci? it's like instead sending a real packet, it sends just something small to see if the device responds?
  139. XanClichttp://wiki.osdev.org/USB#PING_Transaction_Protocol
  140. eddybi have specfobia :P
  141. XanClicThat's no spec
  142. eddybokey, i've read it before
  143. eddybi just wanted to see if my understanding of it is accurate :P
  144. XanClicWell, it's not whether the device responds but whether it's able to accept (or send) data
  145. eddybbut can it be used as a ping facillity? as in test if the device can be reached
  146. XanClicNo
  147. XanClicWell, you could, if you were able to send raw USB packets, but you aren't
  148. eddybah, so it's just a protection mechanism :(
  149. XanClicProtection?
  150. XanClicIt's been introduced to remove useless traffic
  151. Jarvixhi
  152. eddybbrb, testing a bootable pedigree
  153. eddyb*usb stick with pedigree
  154. eddybwell
  155. eddybI can boot pedigree from usb stick
  156. eddybbut
  157. eddyball UHCIs and the EHCIs got IRQ 255 :((
  158. eddybXanClic: does that mean I need APIC driver to make it work?
  159. XanClicDon't know
  160. eddybpedigree got some unused LAPIC routines, but it looks like they're just for IPI :|
  161. XanClicYou'd need I/O APIC for PCI
  162. eddybgreat, IoApic.cc got only the license header and the #include "IoApic.h" :(
  163. eddybdid "<eddyb> great, IoApic.cc got only the license header and the #include "IoApic.h" :(" reached the channel?
  164. XanClicYes
  165. eddybor did anyone say anything while i left?
  166. XanClicNo
  167. eddybokey
  168. eddybi've just read http://markmail.org/message/hjmwydqx6bk2jm6e
  169. eddybmaybe it'd help playing with the BIOS?
  170. eddybheh
  171. eddybBIOS update on this crap really did wonders
  172. eddybit now assigns irqs properly
  173. eddybbut pedigree still hangs after some EHCI message :|
  174. eddybi mean freeze
  175. eddybi got a while(portStatus&PORT_RESET); in my code, can it freeze pedigree so not even a F12(used to get into debugger) will get thru?
  176. eddybdammit, i sound like a total n00b
  177. eddybsure it can. at that point interrupts are disabled by something in ata and i enable them only after XD
  178. eddybwhich means there's a problem at port reset, btw
  179. XanClicSorry to ask those questions, but you marked portStatus as volatile and the MMIO is uncachable?
  180. eddybask matt/james
  181. eddyb-EWORKSINEMULATORS
  182. eddybso i guess yes
  183. XanClicSo it's at least volatile
  184. eddybah, and FYI, empty ports always return 0xffffffff, so it sounds like some other error
  185. eddyblooking over my usb-hcd/main.cc file, i saw probeXhci and it made me laught :))
  186. taljethXanClic: How are you sure that it's volatile? Emulators usually reset that bit immediately, so it might just have the right value from the beginning. (Well, qemu usually does, no idea for the rest of them)
  187. XanClicHm, well
  188. XanClicRight
  189. eddybi added some more debugging, brb
  190. eddybmy second guess
  191. eddybthe second port (with the usb stick) got 0x1803