#tyndur · 2009-11-11

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

  1. pcmattmanHello kwolf
  2. kwolfHi pcmattman
  3. pcmattmanI sent a couple of patches to the CDI list earlier this evening
  4. pcmattmanJust a couple things I ran into while I was debugging all the different NICs Pedigree supports, nothing major
  5. kwolfMaybe you can send an additional patch which adds some -W options to the Makefile? Your compiler seems to be more strict by default than mine
  6. pcmattmanI think it would be best if you choose your -W flags, I don't want to add a whole bunch and leave you with a bunch of warnings :)
  7. pcmattmanI'm merely looking at CDI from a portability perspective in that patch, where it might be harder to integrate into strict environments
  8. kwolfHm, don't know. I guess most people will use their own Makefiles anyway
  9. kwolfBeing strict in what we accept for CDI code actually helps with portability
  10. kwolfHowever, I'm not sure if I want to fix up ata etc., so maybe I'd really better avoid changing the flags
  11. pcmattmanYup, that's my main reasoning for not doing so
  12. kwolfHave you checked if the casts are really necessary or if we could rather change the type of some variables? I don't like these casts much...
  13. pcmattmanThe variables that are being casted are all void*'s
  14. kwolfOh, even the one casted to int?
  15. pcmattmanAh, that case
  16. pcmattmanI wasn't certain about whether cur_buffer needed to be uint32_t or if it was correct, so i went with the least-impact solution
  17. kwolfYou mean netcard->tx_cur_buffer? It's currently int, but I think we could safely make it an uint32_t (or unsigned int, if this is enough)
  18. pcmattmanIn that case, those casts to int are not required
  19. kwolfIf you send a second version, I'll take that, but if not, I also can live with the current version
  20. pcmattmanI'll put one together when I have a spare moment
  21. kwolfWith the e1000 EEPROM, you still haven't had success?
  22. pcmattmanUnfortunately no
  23. kwolfMaybe you really should have a look at the VBox source if it even supports the protocol you're trying to implement
  24. kwolfBy the way, how's your release looking so far? Is it getting stable?
  25. pcmattmanWe're looking good for Saturday
  26. kwolfNice. Are you going release a RC or should I wait until Saturday with breaking it? ;-)
  27. pcmattmanhttp://www.wikiforall.net/pedigree.iso
  28. pcmattmanThat's a pre-release image that you can break ;)
  29. kwolfFrom this week?
  30. pcmattmanLatest build
  31. kwolfWow, 128 MB? At home I would download on it for days... ;-)
  32. pcmattman:)
  33. kwolfWhat software do you include to get it that big?
  34. pcmattmanIt's basically every package that can be installed
  35. pcmattmanThe final images will be a little smaller, we just leave everything in while debugging
  36. kwolfIt's a lot anyway
  37. kwolfI think we would fill maybe 40 to 50 MB
  38. kwolfHeh, you can still cd into regular files
  39. pcmattmanAh. :(
  40. kwolfAlso, vim starts, but is far from usable :-(
  41. pcmattmanOkay
  42. pcmattman:)
  43. pcmattmanWell, Vim won't be on the final release image, and I've just fixed the chdir bug ;)
  44. kwolfAh, ok, removing software is always an option to fix bugs ;-)
  45. kwolfHeh, now I know how you're going to shrink the ISO size ;-)
  46. kwolfvim? Buggy, let's drop it. gcc? Buggy, let's drop it. Kernel? Buggy, let's drop it... *g*
  47. pcmattmanHahaha
  48. pcmattmanhttp://pedigree-project.org/r/boards/2/topics/1 is the selection of packages that will be in the final release
  49. kwolfAh, you're even packaging your own software like the kernel etc.?
  50. pcmattmanCorrect
  51. kwolfLooks like a nice list for developing software
  52. kwolfCan you build a Pedigree kernel on Pedigree?
  53. pcmattmanHeh... As of 6 or 7 months ago, no
  54. pcmattmanAnd we haven't tried since
  55. kwolfI had it work for tyndur in August - checking out, building, etc. - and then we switched to git. So you don't even get the code any more...
  56. pcmattmanWell, we use SCons for our build system, which definitely makes things more complicated
  57. kwolfHm, right
  58. pcmattmanI should probably also mention that 40 MB of source code doesn't fit easily into a disk image ;)
  59. kwolfpcmattman: Disk images can be large ;-)
  60. FreakyPenguinAch hier ist
  61. FreakyPenguin es doch schon angenehmer ;-)
  62. XanClicUh, I cannot understand you at all, FreakyPenguin ;-)
  63. XanClicAh, that's a language I do understand ;-)
  64. FreakyPenguinOffizielle Zweitsprache neben Isländisch ist hier noch immer Deutsch ;-)
  65. XanClicDamnit *g*
  66. XanClicMais qu'est-ce que c'est avec tous les francophones?
  67. taljethHm, ich fange ja nur ungern auch hier mit Kicks an...
  68. XanClicVoulez-vous les bannir?
  69. XanClicOoops
  70. XanClic*g*
  71. XanClicBut in #interlingua, there is nobody but me so I have to compensate that ;-)