#tyndur · 2010-02-15

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

  1. kwolfMoin
  2. pcmattmanHi kwolf
  3. kwolfHi pcmattman
  4. pcmattmanPlease excuse the internal issues with Pedigree over the past 24 hours :)
  5. kwolfYou mean eddyb? I'm not that quick to leave a channel ;-)
  6. pcmattmanWell, he might come here and complain
  7. pcmattmanOn a different note, I am now implementing the mem.h stuff into Pedigree's CDI module
  8. kwolfWell, if he comes here, we can have ops
  9. kwolfI mean, I'm not going to ban him right away now, but if he continues here, I will do so eventually
  10. pcmattmanSounds good
  11. kwolfAre you going to implement the real thing for mem.h?
  12. pcmattmanWhat do you mean, "the real thing"?
  13. kwolfI started with a very simplistic thing for tyndur. Only allocate complete pages, no scatter/gather, always copy
  14. pcmattmanRight
  15. kwolfShould be compliant with the spec, but rather inefficient
  16. pcmattmanI'll probably avoid scatter/gather initially, but everything else should be implementable from the beginning
  17. pcmattmanRealistically though scatter/gather isn't too complicated, it's just easier to ignore it for now
  18. kwolfscatter/gather is an option that you may or may not implement in cdi_mem_alloc when physical memory is requested, but it needs not be contiguous
  19. kwolfBut in general I think it will get useful only when we start passing mem_areas from external sources
  20. pcmattmanThe best thing is that our PhysicalMemoryManager is actually designed in such a way that these calls can directly wrap native kernel calls
  21. kwolfYour PMM can directly handle requests of less than a page?
  22. pcmattmanOkay, most features ;)
  23. kwolfHeh, yes, then you end up with my implementation. ;-)
  24. kwolfThis one: http://list.tyndur.org/pipermail/tyndur-devel/2010-February/001667.html
  25. pcmattmanHeh, nice
  26. pcmattmanThese well-designed kernels are great, aren't they? :P
  27. kwolfSo shouldn't take you too long ;-)
  28. pcmattmanAlready doing a test compile to see if it builds
  29. pcmattmanHeh, failed :P
  30. pcmattman-1 != null, it seems
  31. kwolfBut it's almost the same ;-)
  32. kwolfAnyway, I would be suspicious of code that seems to work at the first attempt
  33. pcmattmanMaybe I should use e1000 or something to make certain the mem functions work
  34. pcmattman(in qemu)
  35. kwolfHm, last time I tried (Friday?) no CDI drivers did work in Pedigree
  36. kwolfNeither e1000 nor pcnet
  37. pcmattmanWas that before or after the mem.h stuff went into the CDI master?
  38. kwolfI reverted the submodule to the last commit before mem.h
  39. kwolfOtherwise it wouldn't even build
  40. pcmattmanHmm, e1000 is being executed, but doesn't even pick up a device
  41. pcmattmanAren't regressions just wonderful? :)
  42. kwolfThey are what makes OS dev interesting :-)
  43. pcmattmanOh right, I actually disabled the net stuff because I can't figure out how to get a cdi_net_driver in the CDI NIC wrapper
  44. kwolfHm, I guess you should fix that ;-)
  45. kwolfIs this what happened with the driver initialisation patches?
  46. pcmattmanI'd say so
  47. pcmattmanAh fantastic, I haven't even properly updated most of the code after those patches
  48. kwolfLooks like we're losing instead of gaining compliant OSes...
  49. kwolfAnd I don't think a complete implementation does even exist
  50. pcmattmanI'll work at it once I commit the mem.h stuff
  51. pcmattmanAt least Pedigree compiles and boots to bash now
  52. kwolfIf it compiles, boot up shouldn't be too difficult with disabled drivers ;-)
  53. pcmattmanOkay, pushed that code finally
  54. pcmattmanWorking through the backlog of things I needed to do last month but never got around to...
  55. kwolfYup, at some point you just need to do it. But everything CDI related should be pretty straightforward.
  56. pcmattmanIt is so far
  57. pcmattmanNow to get these NIC drivers working with the new device initialisation code somehow
  58. kwolf*lol*
  59. kwolfI like your code
  60. kwolf /// \todo Fundamentally wrong
  61. kwolfCould be mine ;-)
  62. pcmattmanWell, look at how I implemented it ;)
  63. pcmattmanIt'll be problematic if someone calls cdi_mem_free on the return value, unless cdi_mem_require_flags makes its argument invalid
  64. kwolfIt doesn't, so the code is fundamentally wrong in two ways ;-)
  65. pcmattmanMaybe we should update the documentation of cdi_mem_require_flags
  66. pcmattman"Can cause its argument to become invalid"
  67. kwolfNo, you should update your code ;-)
  68. kwolfDrivers will still need the old buffer
  69. kwolfBecause the old buffer is where the caller expects the read data in the end
  70. kwolfFor the function is unused anyway, but I hope to change the interfaces some time this week
  71. kwolf*For now
  72. pcmattmanTrue
  73. pcmattmanIt'll be implemented in due time
  74. kwolfAnd you always can stop me from doing it by posting your own patches to the interface, so that I'm busy with changing tyndur ;-)
  75. pcmattmanHahaha
  76. pcmattmanAlso, you used double quotes in mem.h rather than angle brackets, tsk tsk!
  77. pcmattman:P
  78. kwolfYou acked it :-P
  79. pcmattmanI missed that small detail ;)
  80. kwolfWill prepare a patch to change the remaining quotes. While at it, we can do it for the drivers, too.
  81. quokmoin
  82. kwolf__Moin quok
  83. XanClicMoin,
  84. XanClic+quok
  85. quokI had an interesting morning so far
  86. quokI have to take sleeping pills at night because I have restless leg syndrome
  87. quokand in the morning I take pills to keep my blood pressure in check.. it's slightly elevated because I'm a bit overweight (and don't really care to try to correct that situation)
  88. quokwell, this morning I grabbed the wrong pills.. took the sleeping pills instead of the blood pressure pills XD
  89. XanClicI guessed that *g*
  90. kwolf__And you're still awake? ;-)
  91. quokFor now :/
  92. quokCalled off work, my boss laughed at me and told me to get some rest
  93. XanClicxD
  94. quokinstead I'm going to try to code on quokos (and CDI)
  95. XanClicHm, I doubt if you enjoy reading that code tomorrow ;-)
  96. kwolf__Ok, I will make sure that any CDI patches you send today are given a thorough review ;-)
  97. quokMostly I plan on getting CDI stuff started in QuokOS :P
  98. kwolf__When I did it, a was acutally disappointed because it was so easy ;-)
  99. kwolf__-a +I
  100. kwolf__Getting the standard libc function copied into the kernel was most of the work
  101. kwolf__Ok, my implementation is far from complete, but ata works
  102. eddybmoin :)
  103. XanClicYay :D
  104. DickHuuhnSo und nu
  105. DickHuuhnEnglish or German :O
  106. XanClicBetter English
  107. DickHuuhnOkay
  108. DickHuuhnSo, who has won the 512 byte contest now?
  109. DickHuuhnAnd by the way quok: Creative-Commons-Zero is closer to Public Domain than ISC :)
  110. DickHuuhnOkay XanClic was now so kind to tell me that this discussion has already been made :P
  111. XanClicNice, eventually someone here who is capable of speaking good English ;-)
  112. kwolf__Hm, should quok take it personally? ;-)
  113. DickHuuhnI learned it with my language-buddies Westerwave and Oettinger so stfu
  114. XanClickwolf__: Meh ;-)
  115. XanClicI mean someone who is also in #niwohlos and can thus act as my babelfish
  116. quokAh, I knew I shouldn't have joined #lost :)
  117. XanClicBecause it's too fast to use Google? ;-)
  118. quokI'm trying to not use google :P
  119. quokbut barely following :)
  120. kwolf__As long as you're not forced to participate... But DickHuuhn did it right. ;-)
  121. DickHuuhnWhat did I do? D:
  122. quokDickHuuhn: nobody has won yet as one of my testing machines died. I'm still trying to find a replacement for it... one of the entries was tested on it but not the other, so I don't think it's fair at this point to declare a winner
  123. DickHuuhnAh, okay
  124. quokalthough I could just drop that test, but I'd really rather not :)
  125. kwolf__DickHuuhn: You asked him a question in German. I think this is exactly what he was afraid of. ;-)
  126. DickHuuhnOh, sorry, quok :D
  127. quokyes, I understood the german
  128. quokjust wasn't at all sure how to phrase my response :)
  129. kwolf__But answering in English was easier, right ;-)
  130. quokit was!
  131. DickHuuhnyay
  132. quokI just didn't want to answer in English in #lost :)